akloeckner

@MartinHjelmare, you refered me here. I'd appreciate your advice. Is there any activity to be expected on that issue? How should we proceed in this matter (if at all)? We...

Ok. So, I take this as a "wait and see", which I will do, but I won't actively follow up on this idea unless someone else picks it up... I'll...

Before letting go of it, I went through some other issues here to link them up. * One go at my suggestion could also be to run a small "remote...

I now checked that. Thanks for the hint. The two sensors show the following (without sabotage triggered): ``` { "interface": "ip", "rssi": -25, "friendly_name": "Flur Sensor PRESENCE_DETECTION_STATE", "id": "000C170999****", "device_class":...

I just thad a similar problem, which might help pinpointing the bug: Today, I noted that the LOW_BAT attribute was also not showing in HomeAssistant. I found that startling, because...

Thanks for the hint! I have now updated and unfortunately this issue is not solved.

I tried lowercase just to be sure. You're right in that I probably made this mistake and could therefore not "access this attribute". I can access the lowercase attribute (as...

TL;DR: The `SABOTAGE` attribute lives on channel `0`. No `_hm_event_callback` function is called for `channel=0`. This might be caused by them being assigned to `self._eventcallbacks`; instead of `self._hmchannels[channel]._eventcallbacks` as is...

I updated to HA 0.95.4 today. A new sensor appeared for the battery status. I cannot check currently, whether it works. The sabotage attribute is still not working at least...

Sounds like a neat enhancement. Are you thinking, just a fullscreen `DEVICE_TRACKER` tile with fixed `zoom` setting (=should be easy with popups right now)? Or an actual embedded map (=...