You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 6, 2023. It is now read-only.
A change to the names of types (that was not clarified in the documentation) will break this integration in the 2021.7 release. I will submit the correction shortly.
The issue is that the documentation states to use TRIGGER_BASE_SCHEMA which can be imported from device_automation, however I think it was supposed to be DEVICE_TRIGGER_BASE_SCHEMA. The scaffold created this and some modern components use this, however the docs alone just reference TRIGGER_BASE_SCHEMA. This no longer exists and this the integration breaks on load (and will break other automations.) The fix is minor just add DEVICE_ before and everything is fine.
The text was updated successfully, but these errors were encountered:
xannor
added a commit
to xannor/reolink_dev
that referenced
this issue
Jul 14, 2021
A change to the names of types (that was not clarified in the documentation) will break this integration in the 2021.7 release. I will submit the correction shortly.
The issue is that the documentation states to use TRIGGER_BASE_SCHEMA which can be imported from device_automation, however I think it was supposed to be DEVICE_TRIGGER_BASE_SCHEMA. The scaffold created this and some modern components use this, however the docs alone just reference TRIGGER_BASE_SCHEMA. This no longer exists and this the integration breaks on load (and will break other automations.) The fix is minor just add DEVICE_ before and everything is fine.
The text was updated successfully, but these errors were encountered: