search

genielabs / HomeGenie

HomeGenie, the programmable automation intelligence
https://homegenie.it
GNU General Public License v3.0
388 stars 154 forks source link

security system broken with stable 35 #360

Closed tuicemen closed 5 years ago

tuicemen commented 5 years ago

With the current (35) release the security system requires being recompiled to work again. I had figured this was just my system but it appears others are seeing this as well. Also it again doesn't retain its Armed state if set to Armed Home or Away and a reboot occurs #331

genemars commented 5 years ago

@tuicemen I think this can be closed?

tuicemen commented 5 years ago

the issue is still present in v36

genemars commented 5 years ago

@tuicemen I've tested this in Linux and it is working. Did you try on a fresh install?

tuicemen commented 5 years ago

If the security is armed and a reboot occurs the security module reverts to disarmed. happens on all three Pis I run. I've not tested on a fresh install only on a updated HG, will do that today.

genemars commented 5 years ago

If the security is armed and a reboot occurs the security module reverts to disarmed

@tuicemen I think this has always been that way, but this can be a feature request opening a new issue.

tuicemen commented 5 years ago

Ok I noticed a HG service restart also reverts the security to disarmed. Writing a new image with HG now to test the recompile issue. However I suspect any new build will not display this issue with having to recompile the security module until a update is performed. should I install 35 then update to 36 for the test?

tuicemen commented 5 years ago

I created a new raspi Image installed 35 then update to 36 for a test the issue is still there. If you click arm the system never does until you recompile the security program. Thinking maybe it was pulling the issue from 35 when the issue first appeared I did another image and installed a fresh 34 version first. I tested the security program by clicking arm and it worked I then updated to 36 clicked Arm on the security program and it failed to arm. only after a recompile did it work.

genemars commented 5 years ago

ok I will check this out 🙂

tuicemen commented 5 years ago

found another issue with the security module and v36 if set to armed and it is triped and an alarm condition occurs you can't click disarm and get the security back to a disarmed state it stays in an alarm state. re-compiling will reset it to disarmed

tuicemen commented 5 years ago

Version 37 appears to have fixed the security re configure issue. Thanks. As well Thanks for adding the security system retaining its status on a service restart!