Closed nweave03 closed 3 years ago
firstof9
commented
3 years ago Code slot in question is code_slot_3. Which is currently sent Enable = Off the code is clearing, but getting repopulated.
Likely the sync automation firing too quickly?
@FutureTense
nweave03
commented
3 years ago also @firstof9 Should I create a separate issue about the allow_automation_execution not toggling on HA restart or docker restart after the zwave network completes starting?
firstof9
commented
3 years ago Ah shoot, I know why that's not working, should be network_ready not network_start 🤦
nweave03
commented
3 years ago Ah shoot, I know why that's not working, should be
network_readynotnetwork_start🤦
i'm not following. is there some option I need to add or boolean to toggle?
firstof9
commented
3 years ago Edit: network_complete
I've adjusted the Wiki https://github.com/FutureTense/lock-manager/wiki/Additional-Steps#zwave-package-file
nweave03
commented
3 years ago Edit:
network_completeI've adjusted the Wiki https://github.com/FutureTense/lock-manager/wiki/Additional-Steps#zwave-package-file
Ah, okay i've updated my file, then tried a docker restart and a ha restart
But unfortunately it doesn't appear to be working
nweave03
commented
3 years ago @firstof9 looking at what you changed, and the event page [https://www.home-assistant.io/docs/z-wave/events/], should it be network_ready? that appears to toggle it at the appropriate time after the initial spinning stops.
firstof9
commented
3 years ago No network ready isn't the right one, I see you have sleeping nodes, let me compile this with a full list. Well it's one of the proper states, I'll add them all to cover all bases.
firstof9
commented
3 years ago I've updated the wiki again.
nweave03
commented
3 years ago I've updated the wiki again.
got it, looks like it's working. Looks like it's triggering on all 3 of those events? (just wanting to double check my understanding)
firstof9
commented
3 years ago Correct, it's been a while since I used zwave but I'm pretty sure this covers all startup scenarios now.
nweave03
commented
3 years ago is there anything I can do to help on this?
FutureTense
commented
3 years ago @firstof9 is the sensor being updated?
firstof9
commented
3 years ago @nweave03 Try putting this sensor.py file into your custom_components/lock-manager/ overwriting the old one, and restart HA.
This should resolve the issue.
nweave03
commented
3 years ago @nweave03 Try putting this sensor.py file into your
custom_components/lock-manager/overwriting the old one, and restart HA. This should resolve the issue.
Okay there are some differences here. Mostly seems like the calls to zwave aren't happening anymore. I am still seeing that weird create/delete loop. And I captured a crash from notifications. I have also tried to disable all of the codes to get them to clear. The one thing that I can say is that zwave traffic tells me, and manual attempts to confirm also show that no actual code sets go out on disable.
nweave03
commented
3 years ago i was restarting HA and found a bunch of crashes
nweave03
commented
3 years ago okay, so I have tried to disable all the codes, see below
Then I check the logs and zwave logs, it appears to be stuck in the loop, but for all of them
nweave03
commented
3 years ago it also happens with the codes being enabled now. I had to shut off the allow_automation_execution triggers to get it to stop sending code set and clears constantly, which it did start to do after that HA restart.
firstof9
commented
3 years ago Did the PIN status ever go Connected?
The debug messages will always show up because the sensor's refreshing the data, these messages don't mean the code are being updated/cleared constantly. That only happens when the automation(s) fire.
nweave03
commented
3 years ago It always says Connected, even when PIN status is blank. The method I am using to confirm the codes are being updated and cleared constantly is to watch the zwave logs and see what commands are being sent out. I may not be able to see the exact codes being set, but I do see UserCodeCmd_Get, UserCodeCmd_Set, for all the various code numbers going out constantly
firstof9
commented
3 years ago That's very odd, once the slot_code_sensor is cleared or the PIN matches the sensor the automation isn't supposed to fire.
nweave03
commented
3 years ago That's very odd, once the
slot_code_sensoris cleared or the PIN matches the sensor the automation isn't supposed to fire.
is there some way I can add logs or something to help you two see why it thinks it needs to fire?
firstof9
commented
3 years ago I'll see what I can conjure up in the morning.
FutureTense
commented
3 years ago @nweave03, in the future, please use Github’a collapse feature to hide your logs and errors posts. They are making this issue very difficult to follow. Example:
<details>
<summary>Click to show log</summary>
## Logs
1
2
3
4
</details>@nweave03, in the future, please use Github’a collapse feature to hide your logs and errors posts. They are making this issue very difficult to follow. Example:
<details> <summary>Click to show log</summary> ## Logs 1 2 3 4 </details>Click to show log
will do from now on
firstof9
commented
3 years ago I've updated the sensor.py once more lowered it's refresh time to 1 second. Let's see if this helps at all.
nweave03
commented
3 years ago Okay I went ahead and re-ran it. It is still in the loop. I also wonder if there is an issue from unreliability here. On some of these older locks (like this one) I know from experience it can take up to 2 minutes to get a code set. Could this be affecting the turn around time? This is also a large z-wave network with over 115 nodes, would that have an effect here?
nweave03
commented
3 years ago I don't know if this helps, but I decided to do a complete regenerate of the locks as i've done before
lock-manager directory under packages.storage/core.entity_registryThen I restarted HA and did the following
now the logs think there are codes in all the available code slots, and don't respond when I change the code or toggle the enabled.
another odd thing, even when doing the above, it still remembers all of the previous state of the entities since before the removal. Is there a way to do a clean sweep and remove all previous state here?
firstof9
commented
3 years ago another odd thing, even when doing the above, it still remembers all of the previous state of the entities since before the removal. Is there a way to do a clean sweep and remove all previous state here?
This is part of the Home Assistant restore from database feature. You'd have to nuke your database to nuke the data.
now the logs think there are codes in all the available code slots, and don't respond when I change the code or toggle the enabled.
did allow_automations not toggle on?
nweave03
commented
3 years ago another odd thing, even when doing the above, it still remembers all of the previous state of the entities since before the removal. Is there a way to do a clean sweep and remove all previous state here?
This is part of the Home Assistant restore from database feature. You'd have to nuke your database to nuke the data.
now the logs think there are codes in all the available code slots, and don't respond when I change the code or toggle the enabled.
did
allow_automationsnot toggle on?
just realized since I was using the easy mode option on the wiki that nuked the allow_automations setup, re-adding and will post
nweave03
commented
3 years ago okay so oddly enough, its back to only messing with code_slot_3 again (confirmed from watching zwave logs). I briefly disabled code_slot_4, and it started doing the loop on code_slot_4 as well (again, confirmed from zwave logs). Then i re-enabled code_slot_4 and it stopped the loop on code_slot_4 and now is only looping on code_slot_3 again.
firstof9
commented
3 years ago Is code slot 3 enabled or disabled?
nweave03
commented
3 years ago Is code slot 3 enabled or disabled?
It is disabled. Despite the attempt to reset, it still looks exactly like the screenshot from before
firstof9
commented
3 years ago That's odd be cause the log is showing the code is blank so it should go "Disconnected", can you check the code_slot_3 sensor to see what it's showing in dev-tools->states?
nweave03
commented
3 years ago That's odd be cause the log is showing the code is blank so it should go "Disconnected", can you check the code_slot_3 sensor to see what it's showing in dev-tools->states?
it is unknown. Also, it may be relevant, but only 2 of the lock codes are actually present on the lock itself, despite the system thinking 4 are. they are lock_code_1 and lock_code_5 which are the two that the system thought were present before I did my attempted reset.
firstof9
commented
3 years ago It should defiantly not be showing unknown. The only valid values are the PIN or Unavailable.
Try renaming the door via Options to frontdoor2 this should orphan the old entities and you should then be able to remove them from the Configuration -> Entities screen or from the Entities link on the integration screen.
nweave03
commented
3 years ago It should defiantly not be showing
unknown. The only valid values are the PIN orUnavailable.Try renaming the door via
Optionsto frontdoor2 this should orphan the old entities and you should then be able to remove them from theConfiguration->Entitiesscreen or from theEntitieslink on the integration screen.
okay so I did try to create a new named entity. However, none of the old entities can be removed from the method you outlined. See screenshot. I have tried directly, rebooting HA, and rebooting the docker container. All attempts have the same error, and none of the entities are deleted.
From the restart after changing the name to frontdoor2 the following logs show that it still believes there are 5 codes set
Also all of the code slots are now unknown
firstof9
commented
3 years ago This tells me your sensor.py isn't updated. The status of Unknown has been removed for some time now.
If you are fimilar with linux see if you can get the sha256sum of your sensor.py from the lock-manager directory: sha256sum sensor.py it should be one of the following:
0ee5999d6dbcf2e1d44c8303119c1ce05c63d51fbdbb44ca9f7c4fdf6e4d40e9 for version 0.0.40
e0710892b8c8fe958dbb24e077aa02f72271d573f7250ef869358a3a490e826c for the test version I linked last
nweave03
commented
3 years ago This tells me your sensor.py isn't updated. The status of
Unknownhas been removed for some time now.If you are fimilar with linux see if you can get the sha256sum of your sensor.py from the lock-manager directory:
sha256sum sensor.pyit should be one of the following:
0ee5999d6dbcf2e1d44c8303119c1ce05c63d51fbdbb44ca9f7c4fdf6e4d40e9for version 0.0.40e0710892b8c8fe958dbb24e077aa02f72271d573f7250ef869358a3a490e826cfor the test version I linked last
you're right, the sha256 doesn't match
543c340cb63f650d8f32fcb4c48c7f0cdd4772b53a367f3fe5ff15585cd13eb3 sensor.pyBut i literally just copied it in 3 times and still get the same result. I also checked out the branch and checked it and do not see the same checksum you last gave. are you sure you've pushed?
firstof9
commented
3 years ago I sure did, can you double check sensor.py for any occurrence of Unknown, it shouldn't exist on any lines. Once you confirm this, the only other thing I can think of is a duplicated directory in custom_components or something messed up in the __pycache__ directory.
nweave03
commented
3 years ago I don't see Unknown in the sensor.py but I do see it in lock_manager_common.yaml in the random-code-fix branch
:~/repos/lock-manager/custom_components/lock-manager$ grep -R "Unknown" *
lock_manager_common.yaml: {{alarm_type_value}};{{alarm_type_value}}-Unknown Alarm Type Value;{{usercode_value}}can you copy your sensor.py into this text? I'd like to test the sha256sum from the raw text, since I don't seem to be able to find the correct checksums in the branch or from copying it from the web repo
firstof9
commented
3 years ago Likely something weird with github.
Here you go:
nweave03
commented
3 years ago i still get the same sha256sum as I have seen before and from the repo version
:~$ sha256sum sensor.py
543c340cb63f650d8f32fcb4c48c7f0cdd4772b53a367f3fe5ff15585cd13eb3 sensor.pyInteresting, there's zero way your sensor should be reporting Unknown for the code slot, that value is only updated from sensor.py. Something very strange occurring there.
nweave03
commented
3 years ago agreed, i'm also not sure why our sha256sums don't match on the same code
firstof9
commented
3 years ago only thing I can think of is that I ran the sha256sum via WSL it shouldn't matter but maybe it does on a NTFS volume 🤷♂️
nweave03
commented
3 years ago also, this is a small difference, but the value is unknown not Unknown. The grep doesn't find unknown either, but these code slots have never been set to anything. what is the default in home assistant?
firstof9
commented
3 years ago The default is Unavailable until a code populates the slot and then Unavailable when a slot's cleared.
nweave03
commented
3 years ago during home assistant startup it is Unavailable, then once completed it switches to Unknown I'm poking in the home-assistant_v2.db to see if I can even isolate where that is coming from there
nweave03
commented
3 years ago quick question. I've noticed that when I do enter a PIN in the PIN value, it will set that to the code slot upon successful command. This is even despite the fact that the log seems to indicate that for the be469 lock, the code itself isn't available. The default case for the PIN on each of these code slots is unknown. Would it happen to copy whatever value is there for the PIN into the code slot in this case, since the logs indicate that the system thinks there are 5 codes there, even though I cannot identify them?
Describe the bug Lock-Manager is deleting and recreating a lock code in a loop. Not sure why.
Environment (please complete the following information):
Click to show log
**Logs** ``` 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_255 value: 30 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_254 value: False 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_0 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_1 value: ********** 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: Ignoring code slot with * in value. 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] Work around code in use. 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] Utilizing BE469 work around code. 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_2 value: ********** 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: Ignoring code slot with * in value. 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] Work around code in use. 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] Utilizing BE469 work around code. 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_3 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_4 value: ********** 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: Ignoring code slot with * in value. 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] Work around code in use. 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] Utilizing BE469 work around code. 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_5 value: ********** 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: Ignoring code slot with * in value. 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] Work around code in use. 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] Utilizing BE469 work around code. 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_6 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_7 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_8 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_9 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_10 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_11 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_12 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_13 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_14 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_15 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_16 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_17 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_18 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_19 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_20 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_21 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_22 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_23 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_24 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_25 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_26 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_27 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_28 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_29 value: 2020-11-06 22:18:18 DEBUG (SyncWorker_5) [custom_components.lock-manager.sensor] DEBUG: code_slot_30 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_255 value: 30 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_254 value: False 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_0 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_1 value: ********** 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: Ignoring code slot with * in value. 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] Work around code in use. 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] Utilizing BE469 work around code. 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_2 value: ********** 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: Ignoring code slot with * in value. 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] Work around code in use. 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] Utilizing BE469 work around code. 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_3 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_4 value: ********** 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: Ignoring code slot with * in value. 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] Work around code in use. 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] Utilizing BE469 work around code. 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_5 value: ********** 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: Ignoring code slot with * in value. 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] Work around code in use. 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] Utilizing BE469 work around code. 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_6 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_7 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_8 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_9 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_10 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_11 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_12 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_13 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_14 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_15 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_16 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_17 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_18 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_19 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_20 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_21 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_22 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_23 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_24 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_25 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_26 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_27 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_28 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_29 value: 2020-11-06 22:18:48 DEBUG (SyncWorker_8) [custom_components.lock-manager.sensor] DEBUG: code_slot_30 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_255 value: 30 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_254 value: False 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_0 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_1 value: ********** 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: Ignoring code slot with * in value. 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] Work around code in use. 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] Utilizing BE469 work around code. 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_2 value: ********** 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: Ignoring code slot with * in value. 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] Work around code in use. 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] Utilizing BE469 work around code. 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_3 value: ********** 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: Ignoring code slot with * in value. 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] Work around code in use. 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] Utilizing BE469 work around code. 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_4 value: ********** 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: Ignoring code slot with * in value. 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] Work around code in use. 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] Utilizing BE469 work around code. 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_5 value: ********** 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: Ignoring code slot with * in value. 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] Work around code in use. 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] Utilizing BE469 work around code. 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_6 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_7 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_8 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_9 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_10 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_11 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_12 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_13 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_14 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_15 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_16 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_17 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_18 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_19 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_20 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_21 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_22 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_23 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_24 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_25 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_26 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_27 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_28 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_29 value: 2020-11-06 22:19:18 DEBUG (SyncWorker_50) [custom_components.lock-manager.sensor] DEBUG: code_slot_30 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_255 value: 30 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_254 value: False 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_0 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_1 value: ********** 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: Ignoring code slot with * in value. 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] Work around code in use. 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] Utilizing BE469 work around code. 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_2 value: ********** 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: Ignoring code slot with * in value. 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] Work around code in use. 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] Utilizing BE469 work around code. 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_3 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_4 value: ********** 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: Ignoring code slot with * in value. 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] Work around code in use. 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] Utilizing BE469 work around code. 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_5 value: ********** 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: Ignoring code slot with * in value. 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] Work around code in use. 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] Utilizing BE469 work around code. 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_6 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_7 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_8 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_9 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_10 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_11 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_12 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_13 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_14 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_15 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_16 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_17 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_18 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_19 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_20 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_21 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_22 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_23 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_24 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_25 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_26 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_27 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_28 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_29 value: 2020-11-06 22:19:48 DEBUG (SyncWorker_43) [custom_components.lock-manager.sensor] DEBUG: code_slot_30 value: ```Screenshots
Additional context see discussion on bug #55