-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Setting alarm state to Night crashes Homebridge #85
Comments
That is strange. There should not be a Night option available for the arm accessory. Which version of Homebridge & homebridge-verisure are you currently running? |
I am running Homebridge version 0.4.53 (through Hoobs version 3.1.27). And version 1.11.0 of homebridge-verisure. Also, the night alarm state does not show up in Apple's Home app, only in Eve's app. Maybe there is no way of hiding it in the Eve app? |
Oh, you used EVE to set it to Night? We could check before trying to set the state to make sure we don’t crash 👍🏼 |
Great! |
Off topic. But any chance of changing the name of home to night? So instead of home, away and off it says night, away and off. My physical button from Verisure shows a moon and a sun where the moon represent the current "home" mode. Having it named night would in this instance make more sense. |
I concur. The current naming is a bit of a brain bender. |
I can see how the current naming makes sense in the way Verisure labels the states with numbered panel. But I mostly use the “Trygghetspanel” with the moon and sun. In this scenario the naming doesn’t make sense. Maybe change it to home, on and off or night, on and off? I guess the question is should the naming follow Verisure logic or a more generic naming scheme. PS. Verisure just announced Arlo video doorbell |
I am running Homebridge through HOOBS in a docker container on a Synology.
When using the homebridge-verisure plugin for homebridge, in the iOS Eve app there are four alarm states: Stay, Away, Night and Disarm. If selecting the Night state, homebridge crashes with the following output in the terminal:
Would it possible to have the Night alarm state actually activating the Stay state so we can avoid this crash if accidentally clicking "Night"?
/Oskar
The text was updated successfully, but these errors were encountered: