Update Yale Smart Alarm Client


sor.netatmo
2021-07-29 18:26:11 INFO (SyncWorker_40) [backoff] Backing off _authorize(...) for 13.7s (requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://mob.yalehomesystem.co.uk/yapi/yapi/o/token/)
2021-07-29 18:26:18 WARNING (MainThread) [homeassistant.components.alarm_control_panel] Updating yale_smart_alarm alarm_control_panel took longer than the scheduled update interval 0:00:30
2021-07-29 18:26:25 ERROR (SyncWorker_40) [backoff] Giving up _authorize(...) after 8 tries (requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://mob.yalehomesystem.co.uk/yapi/yapi/o/token/)
2021-07-29 18:26:25 INFO (SyncWorker_40) [backoff] Backing off get_authenticated(...) for 0.0s (requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://mob.yalehomesystem.co.uk/yapi/yapi/o/token/)
2021-07-29 18:26:25 INFO (SyncWorker_40) [backoff] Backing off _authorize(...) for 0.4s (requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://mob.yalehomesystem.co.uk/yapi/yapi/o/token/)
2021-07-29 18:26:26 INFO (SyncWorker_40) [backoff] Backing off _authorize(...) for 0.5s (requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://mob.yalehomesystem.co.uk/yapi/yapi/o/token/)
2021-07-29 18:26:26 INFO (SyncWorker_40) [backoff] Backing off _authorize(...) for 1.7s (requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://mob.yalehomesystem.co.uk/yapi/yapi/o/token/)
2021-07-29 18:26:28 INFO (SyncWorker_40) [backoff] Backing off _authorize(...) for 2.2s (requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://mob.yalehomesystem.co.uk/yapi/yapi/o/token/)
2021-07-29 18:26:31 INFO (SyncWorker_40) [backoff] Backing off _authorize(...) for 14.2s (requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://mob.yalehomesystem.co.uk/yapi/yapi/o/token/)


Hey,
I logged the issue on github and was told the new version that can be integrated into HA will be on the next upgrade.

Does the new integration improve the response times at all? I think the current integration I’m using for door contacts only polls the api every 60 seconds.

Does anyone know if this new version will allow you to trigger the panic button?

After updating to Home Assistant 2021.8.1 the integration failed to load.
Was in my config.yaml, but release notes say that the integration should still load and can then just remove config.yaml entry.

That didn’t work. So removed the config entry and integration and installed via the integrations panel and still not working.
Error in log:

Error setting up entry *email_address* for yale_smart_alarm
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 293, in async_setup
    result = await component.async_setup_entry(hass, self)  # type: ignore
  File "/usr/src/homeassistant/homeassistant/components/yale_smart_alarm/__init__.py", line 19, in async_setup_entry
    if not await hass.async_add_executor_job(coordinator.get_updates):
  File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 52, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/yale_smart_alarm/coordinator.py", line 119, in get_updates
    cycle = self.yale.get_cycle()
AttributeError: 'YaleSmartAlarmClient' object has no attribute 'get_cycle'

Any suggestions?

Thanks.

Same experience here but on 2021.8.2

Rolling back to 2021.7.x build fixes it.

Hi
I recommend raising a github ticket otherwise this won’t get sorted :slight_smile:

2021.8.2 is working fine for me.

Came here to look if anyone else has same problem. I raised a github issue:

I just upgraded as well and I am having the same issue

Error setting up entry *email_address* for yale_smart_alarm
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 293, in async_setup
    result = await component.async_setup_entry(hass, self)  # type: ignore
  File "/usr/src/homeassistant/homeassistant/components/yale_smart_alarm/__init__.py", line 19, in async_setup_entry
    if not await hass.async_add_executor_job(coordinator.get_updates):
  File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 52, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/yale_smart_alarm/coordinator.py", line 119, in get_updates
    cycle = self.yale.get_cycle()
AttributeError: 'YaleSmartAlarmClient' object has no attribute 'get_cycle'

You guys who happen now to have this issue that is says it can’t find get_cycle you don’t happen to have another custom component targeting the same upstream package (YaleSmartAlarmClient)?
You might need to adjust the manifest.json file within to use the same package version (0.3.4) or simply remove it all.

Bit of a update guys. I did indeed have a custom Yale component that was using a older version of the Yale api. Updating my custom component to 0.34 in the manifest fixed the issue

Thansk @gjohansson and @ha_irish, I have the custom_component Yale_Binary_Sensor and that needed updating to reflect the HA version change in the manifest.json.
There was also update to the binary_sensor.py file.

1 Like

Thanks for sharing the info on the yale binary sensor for door/window contacts. First time hearing about it!

@gjohansson
Thank you for working on this component, could you please confirm if you’ll be adding the panic button as a trigger?

That is the intention but as the list is quite long for what needs to be added e.g. locks, contacts etc. and every PR takes some time waiting for someone from core team to review it, it will take some time before it’s in.
But we will get there eventually

1 Like

Hi Guys,
is anyone else having a problem with the Yale smart integration stating it can’t connect?

I had some issues this morning and it seemed like a Yale outage as I couldn’t even get on via the Yale app, I did restart HA and then it started working after the Yale app was back up.

1 Like

oh okay
strange thing I was was able to log into the app and could use it fine. I restarted and everything was fine for about 30mins. I disables it this morning and I’ll recheck now.

thank you for responding