Swapped Current State

[Minimiller]

Hi MnrGreg. Now that Homekit is working I've tested it a bit and noticed that when I manually Stay-Arm at the panel it returns a CurrentState of 1 (i.e. Away_Arm state) on both the Pi terminal and on Homekit. Whereas, when I set the alarm on Homekit it is correct (i.e. the TargetState is a 0). IIf I close Homekit and start it again with the alarm in any state the alarm icon will always shows an "Away" state. Is this normal? I'm not much past the 'nooby' stage so unfortunately I'm can't make too much sense of the code. Thanks.

[micdamb]

Hi Minimiller, What does it mean "'initialising' the Homebridge by Stay-Arming the MG5050"? I think I have the same problems as you were when Homekit not working. Can You Help Me? The problem is inside the file Config.json? Now I'm using Homebridge for Bticino Myhome Control. { "accessory": "Homebridge-Paradox", "name": "Alarm System", "mqttusername": "", "mqttpassword": "", "mqttserver": "mqtt://localhost", "controltopic": "Paradox/C/P1", "statetopic": "Paradox/Events", "stayevent": "Event:Non-reportable event;SubEvent:Arm in stay mode", "armevent": "Event:Partition status;SubEvent:Arm partition", "disarmevent": "Event:Partition status;SubEvent:Disarm partition", "triggeredevent": "" } Have you got an example? Thanks a lot.