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
It is possible for some tools to provide events that are not unique across the event title. For example a guest books multiple stays within the sensor window and the tools provides the guest name which is then used as the event name. As such, the lock updating can get caught trying to update the same slot between the multiple events.
There are two possible methods to make this work:
Add unique information to the event names (start DD/MM ?) easy, but somewhat ugly
Store information in the sensor as to which slot was used. This does have added complexity related to an HA restart as any slots already assigned would have to be properly detected and stored
The text was updated successfully, but these errors were encountered:
It is possible for some tools to provide events that are not unique across the event title. For example a guest books multiple stays within the sensor window and the tools provides the guest name which is then used as the event name. As such, the lock updating can get caught trying to update the same slot between the multiple events.
There are two possible methods to make this work:
The text was updated successfully, but these errors were encountered: