Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Offline Door Sensor displays "Open" status in HA #20

Closed
cdrobey opened this issue Mar 17, 2022 · 7 comments
Closed

Offline Door Sensor displays "Open" status in HA #20

cdrobey opened this issue Mar 17, 2022 · 7 comments

Comments

@cdrobey
Copy link

cdrobey commented Mar 17, 2022

My door sensor went off-line and displays the sensor is open instead of unavailable. The HA logbook displays open and starts automation.

@XaF
Copy link
Owner

XaF commented Mar 17, 2022

Do you have logs from the automation to see what we receive as information?

I believe that an offline sensor is just reporting as open (i.e. Unsafe) from the panel, which does not allow us to differentiate between the two, which would thus be expected behavior here

@cdrobey
Copy link
Author

cdrobey commented Mar 18, 2022

Would you direct me to the logs files. I was unable to find any issues in home-assistant.log as well as docker stdout details.

@cdrobey cdrobey closed this as completed Mar 21, 2022
@nwf
Copy link

nwf commented Jan 8, 2023

Sorry to necro a bug report, but is it really the case that the panel doesn't differentiate between "failed" and "unsafe" states for integration? That's incredibly rude of it. :'(

@XaF
Copy link
Owner

XaF commented Jan 8, 2023

The panel does have a distinction for those states, but through the 3rd party integration we receive the same message in both cases: "open".
There is no way to know if that "open" means that the sensor has been activated (e.g. Door open, motion detected) or if the sensor is unsafe (e.g. Tempered with, non-responsive).

@nwf
Copy link

nwf commented Jan 8, 2023

Thanks. That's... more reason to replace this inherited system with something else. That said, thanks for all your hard work on qolsysgw; it was pretty smooth to get going (modulo finding my way around HA and friends) and it looks like it Just Works (TM) as best as the data stream it's given allows it.

@XaF
Copy link
Owner

XaF commented Jan 8, 2023

So I played a bit with my sensors and tampered them, and seem to see some kind of pattern when a sensor is tampered with, where the message seem to be repeated. This is not instant, nor does it seem to be something that can work 100% of the time, but we might be able to get something working.
I do not know if this is the same kind of information we would receive from an offline sensor, and it seems like if AppDaemon is restarted, when we pull the summary from the panel, we lose that information. I'll still try to see what kind of data we can get and if it makes sense to build that into qolsysgw even if it's partial information.

@XaF
Copy link
Owner

XaF commented Jan 16, 2023

I put more details in #73 and merged #74 to add the support. I might also merge #75 to bubble up the tampered list to the partitions. These will thus be part of the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants