search

davesmeghead / visonic

Visonic Custom Component for integration with Home Assistant
Apache License 2.0
92 stars 20 forks source link

alarm_sensor_bypass service call appears to have broken #55

Closed stridger closed 2 years ago

stridger commented 2 years ago

I am using the visonic.alarm_sensor_bypass HA service call in some of my scrips, which worked fine so far, but since recently it seems to have broken. I am not sure if that is due to a module or a HA update.

It logs "Attempt to bypass sensor but entity not defined", even though the entity clearly is defined. The callI use is as follows:

service: visonic.alarm_sensor_bypass
data:
  entity_id: binary_sensor.visonic_z02
  bypass: true

the entity does exist and bypassing works fine from the new frontend switch, but it would be good to be able to use the service call again.

Any clues?

Thank you so much for all your work on this, this integration is quite key for my alarm panel automations but also home automations more generally as it exposes all Powermax sensors to HA.

davesmeghead commented 2 years ago

I've spotted the problem, it's due to changes made in the HA Core, I've uploaded release 0.7.0.0, please give it a try

stridger commented 2 years ago

Wow, that's amazing, thank you so much. Yes bypassing works perfectly now. When testing though I noticed that this call still does not work (sorry to create more work):

service: visonic.alarm_panel_command
data:
  command: arm_home

However that is less of an issue, as I can use the standard alarm_control_panel.alarm_arm_home etc commands instead, which work fine. But I thought I would just mention it anyway.

Thank you for your ultra-quick help! Enjoy your coffee and your weekend :-)

davesmeghead commented 2 years ago

That's good, I've extended the solution to cover the other services, please update to release 0.7.0.1, and thanks for the coffee :)