Correct method for bypassing zones

[reflexsa]

Firstly, thanks for this integration. Has been a blessing! I wanted to ask something regarding bypassing zones. The way I have been bypassing my zones (as needed) through home assistant was using the following in my configuration.yaml:

#Alarm bypass zones
mqtt:
  switch:
    - name: "Guest bedroom bypass"
      command_topic: "paradox/control/zones/Guest_bedroom"
      state_topic: "paradox/states/zones/Guest_bedroom/bypassed"
      state_on: "True"
      state_off: "False"
      payload_on: "bypass"
      payload_off: "clear_bypass"

This seems to work before and after arming which is convenient, but I noticed the 'attached image' in Babyware, I'm not sure if it is actually a problem or if it is caused by how I am bypassing.

After doing a bit of reading here I assume the preferred way is using bypassed in HOMEASSISTANT_PUBLISH_ZONE_PROPERTIES, however I am not sure how to see or access these properties. After adding bypassed to in the configuration I only see entities for the 'open' and 'tamper', but not 'bypassed'

[yozik04]

What panel you are talking about? We support EVO and MG which are different on the protocol.

[reflexsa]

Sorry, it is MG5050

[yozik04]

Unfortunatelly cannot comment on that :) That part was not developed by me and I do not own that hardware.

[reflexsa]

No problem. My current method works ok but does look a bit cumbersome

[yozik04]

The level of support of MG branch is "as is". If unit tests pass I consider it is still working 😅.

[DeFiEcoSys]

Hey @reflexsa

You can go to Addons -> Paradox -> Configuration and scroll down to "HOMEASSISTANT_PUBLISH_ZONE_PROPERTIES" and select "bypassed" which will then make a button for each of your zones in HA that allows you to enable/disable them being bypassed.

It's the same outcome as what you have above, except you don't have to write the switch(es) yourself

[reflexsa]

Hey @reflexsa

You can go to Addons -> Paradox -> Configuration and scroll down to "HOMEASSISTANT_PUBLISH_ZONE_PROPERTIES" and select "bypassed" which will then make a button for each of your zones in HA that allows you to enable/disable them being bypassed.

It's the same outcome as what you have above, except you don't have to write the switch(es) yourself

Hey,

Unfortunately I did try adding "bypassed" there but do not seem to get a separate entity to use for bypassing. Perhaps I am looking at the wrong thing. Does a new entity appear after adding this? For the "tamper" option it did, but not when I added "bypassed"

[DeFiEcoSys]

I assume you've restarted the addon, and then Settings -> MQTT -> Devices -> [Click on your panel]

This then has extra Zone with "Bypassed" on the end.

That worked for me (and another friend).

[reflexsa]

I assume you've restarted the addon, and then Settings -> MQTT -> Devices -> [Click on your panel]

This then has extra Zone with "Bypassed" on the end.

That worked for me (and another friend).

Aha, I see them there! How would I add these to a dashboard without adding the whole lot? They don't seem to show up as entitities. I assume I can probably just manually copy the entity ID? Via the MQTT method you mentioned if I click on one of the items for details it shows this:

[DeFiEcoSys]

Correct, try and add in the name of the entity by ID (so like switch.zone_master_bedroom_bypassed)

[reflexsa]

Thanks so much! Somehow would have probably never found that.

[DeFiEcoSys]

No problem 👍

[reflexsa]

Something interesting, after viewing all the bypasses as you suggested, they now do appear in the entity list as well as when adding a card by entity.

[DeFiEcoSys]

Maybe just some caching issue where they weren't initially loaded.

The other handy one (same method) is to get the "was_in_alarm" which will be set to true (or "on") when that zone was what activated the alarm (handy for automations)