-
Notifications
You must be signed in to change notification settings - Fork 87
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
MQTT Topics #61
Comments
Hi, I'm not sure I fully understood your comment. In paradox/states/partitions/PARTITION_NAME/current you will have information about the current state. This is intended for homekit but can be used for other means. |
Hi there, Am using with homekit and works great - let me try and explain; Below messages from ARM/DISARM and STAY - SLEEP is same as STAY; Arm Panel paradox/states/partitions/Outside/arm - "True" Disarm Panel paradox/states/partitions/Outside/arm - "False" Arm Stay Panel paradox/states/partitions/Outside/arm - "True" Disarm from Stay Panel As you can see the paradox/states/partitions/Outside/arm is always present regardless of the mode, this makes it difficult to follow the state through the messages. If there was a message like paradox/states/partitions/Outside/full_arm the states would be separate, hope im explaining ok. Maybe a simpler view is not to get the paradox/states/partitions/Outside/arm True messages when in SLEEP or STAY, just the false as it would indicate the partition is disarmed. So given the above if I filter only on; paradox/states/partitions/Outside/stay_arm - "True/False" I can get accurate state of SLEEP/STAY and DISARM for both of these - ARM is not possible as im excluding paradox/states/partitions/Outside/arm - "True" Kind regards, Emil |
Just to add; paradox/states/partitions/Outside/current_hass Sometimes it is correct for STAY and SLEEP i.e. "armed_night", but most of the time for all armed states it is just "armed_away" E |
There is a custom mapping for each platform. The mapping is limited to the states that exist in the target platform (homekit or hass). See the configuration variables MQTT_PARTITION_HOMEBRIDGE_STATES and MQTT_PARTITION_HOMEASSISTANT_STATES as these states can be customized. |
Thank you so much - there is still a bug somewhere as the status for ARM/STAY/SLEEP stays on armed_away most of the times - this was also the case in Tertuis's MQTTIP150 script - I could never get this to work reliable - not sure if other people are using all 3 armed states. |
i am using all the arm states on a daily basis and have not encountered any issues. |
Ok so just bought a new panel as messing with a active alarm not a good idea :-) Issue still the same for hass - states not correct for STAY and SLEEP. Anybody that can assist me to validate this - Iondarie confirmed all states is working for him/her. Only Warnings I get; 019-04-01 16:30:20,779 - WARNING - PAI.paradox.paradox - Missing element ID in system/ Kind regards, Emil |
You can adjust the state map in the configuration file. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
System
MG5050 USB307 and IP150
Describe the bug
Stay and Sleep Arm also receives regular Arm.
Hi there - is it possible to have a separate state for Arm, behavior right now is when you Sleep/Stay Arm you also receive a Arm message which theoretically is correct. This makes it harder to maintain state across STAY/ARM/SLEEP/DISARM - easy for ARM/DISARM or STAY/SLEEP/DISARM but struggling with the combination.
Kind regards, Emi
The text was updated successfully, but these errors were encountered: