e-mcgee
commented
7 years ago Hi, the first issue you mention is related to the initial state problem. I have solved this for the PGM zones recently and need to fix for the alarm. It is easy to solve by simply setting the alarm to the correct state, i.e. disarm to match the actual state. Almost like syncing it initially. thereafter it is fine. Once I update the code it should work correctly from startup but for now the initial state is not correct.
The fact that your console states do not match the actual states means that the plugin is not getting the states from the alarm. There could be several reasons for it so you will need to troubleshoot.
An obvious issue could be that the alarm is busy with another application logged in such as iParadox. Unfortunately the alarm only allows a single login at a time. Thus if iParadox is connected nothing else can connect, and similarly if the plugin is logged in nothing else can connect. You should be able to spot this on the console as it will state that it cannot connect. To solve you need to make sure nothing else is connected at startup. It also means that iParadox will not work once the plugin is connected unfortunately. I have also not tested with your alarm type, so it can be that your alarm does not work. To confirm if it should work I suggest scanning through the various forums to see if other people had issues with your version alarm.
On the PGMs you must know that you need a reed switch (magnetic switch) that indicates whether the door is open or closed connected to the built in zone on the PGM. The plugin uses that to determine of the door is open or not. I am still battling with getting the Home app status correctly updated at the moment. I hope to solve that soon but it is a bit of trial and error at the moment. However, the plugin gets the correct status so you should be able to see that correctly once the you get the plugin to talk to your alarm.
Another pointer is that, once you have the plugin talk to your alarm the zone numbering should be confirmed as well. It could be that you are not matching the zone numbers correctly.
Last thing, note that the plugin does not support multiple partitions yet as I do not yet know how to get the second partition state read. I hope to get some input on that soon which will enable the plugin to read both partition status, but until that is resolved it only supports one.
booboisie
Hi – thanks for your work on this plug in. I’m just getting started with the plug in and homebridge running on Rasbian against a Paradox EVO192 (v4.52) with IP150 (v1.39.02) and have run into some issues getting it up and running correctly.
The Paradox system as 15 zones (garage doors, motion sensor and contact sensors) across two “areas”. On startup of homebridge in the console, the alarm status shows as “Alarmstatus:Disarmed”, however on the Home app, it continues to show as “Arming…”.
The status of zones show as “off” in the console and the home app regardless of state – even after triggering the PGM from iParadox the plugin does not correctly report the status of the garage door, nor enable it to be controlled from the home app.
I’ve included an excerpt from my config.json file below for reference. Would appreciate any pointers on where I'm going wrong to help get this up and running.
Thanks and Regards, Chris
{ "bridge": { "name": "Homebridge", "username": "CC:22:3D:E3:CE:30", "port": 51826, "pin": "031-45-154", "manufacturer": "@nfarina", "model": "Homebridge", "serialNumber": "0.4.20" },
"accessories": [ { "name": "Alarm", "config": { "type": "Alarm" } },