Status of "No Response" indication

[keness521]

Problem description

Hello! I apologize if I've missed easily available information, I've read though, and I think the latest information about having a device show as "No Response" when Z2M declares it as such is possible, with v1.11.0-beta.2. Is this correct? Are there any other things with v1.11.0-beta.2 that might be a concern coming from v1.10?

I'm lucky enough to have a very stable network (knock on wood) and so I almost never see "No Response" for any devices, Z2M or otherwise. But I also just noticed that when I unplugged one device for a couple days to work on it, it never went to "No Response" in HomeKit. It did in Z2M right away, but I could control it on and off perfectly fine in HomeKit, even though it was actually unplugged.

I worry that I could have a device malfunctioning and not know about it if it were something that I couldn't just see with my eyes.

I think from what I understand, replicating Z2M's "No Response" into HomeKit is a more complicated than it might seem...?

Thanks very much for all the work on Homebridge-Z2M!

Suggested solution

No response

Alternative solutions

No response

Additional context / information

No response

[stale]

It appears that this issue did not have an update in quite some time. Please check if you can provide any additional information to help resolve this issue. If there isn't any activity in the next two weeks, this issue will be closed automatically. Thank you for your contributions!