Files
core/tests
Matthew Treinish 087bffeaae Add workaround to use notification state for zwave lock state (#17386)
* Add workaround to use notification state for zwave lock state

There are several zwave lock models out there which do not seem to
update the lock state on non-rf events (see #11934 #14632 #14534 for
examples) including kwikset smartkey zwave plus locks (which I own).
In these cases it seems that the notifications for non-rf events the
access_control value is updated but not the primary value for the
lock state, which is what is used to set the is_locked property. To
properly have the lock state accurate for all types of notifications
on these models we need to use the access_control field. This commit
adds a workaround for the 4 models reported to exhibit this behavior
so that home-assistant will reliably set the lock state for all
device notifications.

* Add YRD220 as per adrum to workaround list

* Inline constants
2018-11-06 11:00:48 +01:00
..
2018-10-29 11:28:04 +01:00
2018-11-05 13:21:03 +01:00
2016-01-30 14:08:32 -05:00
2018-08-20 16:34:18 +02:00
2016-10-23 23:48:01 -07:00
2018-10-11 19:24:25 +02:00
2018-10-24 12:10:05 +02:00
2018-10-24 12:10:05 +02:00
2018-10-24 12:10:05 +02:00
2018-02-22 23:22:27 -08:00