Topic is not updated with device status "Not Home" after TRACKER_TIMEOUT reach out

[begemotik]

Describe the bug
I configured the gateway as Home Assistant addon. I see the successful messages of iphone being online. The problem is that when device is not actually connected the status is still "home". I expect the reason is that after timeout (TRACKER_TIMEOUT ) happen no new messages posted to the topic and last one contains "rssi" property.

Configuration

{
    "adapter": "",
    "bindkeys": {},
    "blacklist": [],
    "ble": 1,
    "ble_scan_time": 10,
    "ble_time_between_scans": 20,
    "discovery": "1",
    "discovery_device_name": "TheengsGateway",
    "discovery_filter": "[IBEACON]",
    "discovery_topic": "homeassistant",
    "enable_tls": 0,
    "enable_websocket": 0,
    "general_presence": 1,
    "hass_discovery": "1",
    "host": "core-mosquitto",
    "identities": {
        "redacted": "redacted"
    },
    "log_level": "INFO",
    "lwt_topic": "home/TheengsGateway/LWT",
    "pass": "redacted",
    "port": 1883,
    "presence": 1,
    "presence_topic": "home/presence/TheengsGateway",
    "publish_advdata": 0,
    "publish_all": 1,
    "publish_topic": "home/TheengsGateway/BTtoMQTT",
    "scanning_mode": "active",
    "subscribe_topic": "home/+/BTtoMQTT/undecoded",
    "time_format": "0",
    "time_sync": [],
    "tls_insecure": 1,
    "tracker_timeout": 60,
    "user": "addons",
    "whitelist": [
        "redacted"
    ]
}

Expected behavior
I expect that after timeout configured if device is offline it should be marked as "not_home".

Screenshots
The last message was posted 30 minutes ago, and home assistant state is still "home".

[kickouille]

Hello @begemotik ,

I'm encountering the same with a different tracking device.
Indeed, after the timeout, a new JSON is supposed to be published for this device, without RSSI parameter.

I didn't have a chance to perform debugging for the moment but I believe it is worth it.

Regards,

Kickouille

[DaN66O]

This problem still exists.

[DigiH]

This problem still exists.

Which problem exactly, with which version of Theengs Gateway and with which settings?

The device-tracker Home Assistant discovery messengers would also be helpful.

Is it for all of you with having only one single device in the white-list?

[DigiH]

@begemotik @kickouille @DaN66O

Can any of you build from the development branch and report back?

#310

[kickouille]

@DigiH , dev branch built, installed, up and running. Waiting for the wife to move the car to test. :)
Apart from that, I confirm the issue is still there. Last MQTT message received still contains the RSSI values which does not release the "at home" status. As, as I undestand, tracking decision is based on this.

[DigiH]

@kickouille

• Can you post the last message you are receiving, which apparently still includes the RSSI property?
• Can you also confirm that you are using the white-list functionality with only a single MAC address defined, presumably for your BM2?
• Can you also confirm that this issues doesn't happen when you do not use a white-list at all, or with more than one device added to the white-list with the additional device being a non-tracker device like a thermometer or similar?
• Can you also confirm that you are only running a single Theengs Gateway instance with the latest development build, and no additional instances or instances of OpenMQTTGateway as well?

[kickouille]

@DigiH ,

Yes, I whitelisted the MAC address of my two HolyIOT devices.
I will have to test without whitelisting.
Yes, I'm only running a single gateway in latest dev.

I will have to to deeper tests and provide yu with the outputs because I noticed the following:
When devices are deleted from HA and the gateway is restarted, the beacon is properly identified as an HolyIOT one.
However, I noticed that when the issue happens, the device in HA is changing of type. It becomes a generic iBeacon.
So there may be an issue with the decoder not being able to identify the device.
HolyIOT sending seems consistent, but I'm wondering if maybe some data is missed when it is far away.

Regards,

Yanik

[kickouille]

Ok, in my case, I found what is happening, not sure it is linked to @begemotik initla issue opening.

I opened a PR: theengs/decoder#676

The way to identify the device type was partly based on a value which varies with time, the battery level.

@DigiH please tell me if that suits you.

[DigiH]

Cheers @kickouille - already merged.