MQTT not processed in the background

[Radstake]

When the homekit app is active, changes are working when MQTT is configured. Both on and off work.
When the homekit app is not active, the status changes are not processed. When you open the homekit app, it loads with the previous state, not the updated one.

For now I fall back to statusurl, but would love this the work propperly

[Supereg]

Could you maybe provide some details about your configuration?

This sounds like intended behavior. The Home App will only subscribe to event notifications if it is open. When it closes, after a while, it will unsubscribe from any notifications (so the device could for example also go to sleep and save battery).
When the Home App reopens it will make a READ request (and also subscribe to future event notifications). And that's where your initial configuration would be important, as typically it would call the statusUrl to retrieve the latest state. But there are plugin configurations possible where you can omit the statusUrl and then the last known value (should) be returned.

[Radstake]

Hi, Thank you for your reaction. I'm currently refactoring my domotica setup and not using this at the moment. When I can give more feedback, I'll let you know. Thanks. Op vr 4 dec. 2020 om 12:57 schreef Andi <notifications@github.com>:

…

Could you maybe provide some details about your configuration? This sounds like intended behavior. The Home App will only subscribe to event notifications if it is open. When it closes, after a while, it will unsubscribe from any notifications (so the device could for example also go to sleep and save battery). When the Home App reopens it will make a READ request (and also subscribe to future event notifications). And that's where your initial configuration would be important, as typically it would call the statusUrl to retrieve the latest state. But there are plugin configurations possible where you can omit the statusUrl and then the last known value (should) be returned. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#68 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHWTML3HSWYSJNJIUNRWUDSTDFDBANCNFSM4RT3Z2FQ> .

[Supereg]

Just had a look at the code, and yes, indeed toggle switches (this without statusUrl) didn't properly return values coming from MQTT or notification server on read requests.

Fixed v0.5.32

[Radstake]

Check, thanks for fixing. Op vr 4 dec. 2020 om 14:09 schreef Andi <notifications@github.com>:

…

Just had a look at the code, and yes, indeed toggle switches (this without statusUrl) didn't properly return values coming from MQTT or notification server on read requests. Fixed v0.5.32 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#68 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHWTMMGVCJ7JG2ZNLMYWS3STDNSFANCNFSM4RT3Z2FQ> .