firstof9
commented
7 months ago Means your slots are not available, fix the code slots in ZwaveJS UI.
Closed Vartkat closed 7 months ago
firstof9
commented
7 months ago Means your slots are not available, fix the code slots in ZwaveJS UI.
Vartkat
commented
7 months ago Hi,
Thanks for the quick answer. That did the trick for one but not for the other even if... I restarted Home Assistant I rebooted the Cabin1 Raspberry I reloaded the integration I restarted Home Assistant (after Cabin1 reboot) I reconfigured the integration (opened the dialog and validate).
Even if the slots were marked as Available in ZWaveJS UI I updated all 30 slots to Available and got 'Value updated' popup for each one.
Vartkat
commented
7 months ago I deleted the integration (just for this lock), restarted Home Assistant, re-added the integration with the exact same parameters... Stil no luck...Restarted HA... Nope. Gone to ZwaveJS UI to verify states, all slots marked as available, then just in case I asked for a refresh code values... Bingo ! Thanks for your help.
Describe the bug Entities
Environment (please complete the following information):
Logs
If Keymaster debug enabled :
home-assistant_keymaster_2023-11-23T14-20-38.765Z.log
Which seems to me is exactly my problem but doesn't give me any clue on how solve it. More, as I have several locks it doesn't say which lock it's about.
Screenshots
Additional context We're dealing with three cabins, Cabin1 Cabin2 and Cabin3. One Raspberry on each cabin (because one Zwave stick per cabin because of distance and walls issues). Cabin2 is the one running Home Assistant for everyone. Cabin1 and Cabin3 are just running Debian12 Docker and ZwaveJS-UI (and portainer). Cabin1 and Cabin3 have the axact same config. Integration for Cabin1 and Cabin3 added succesfully using ws:// URL. Zwave working fine, I can lock and unlock, it reports all status, all Zwave entities are here and oK.
Cabin 1 is the only one having issues with Keymaster.
I tried removing Cabin1 keymaster integration which leaves a bunch of entities. I manually deleted all Cabin1 keymaster entities which were unavailable while the corresponding integration (keymaster) was deleted. Rebooted each time I changed something. Once I found Home Assistant cleaned from the integration and its entities I begun the process of re-adding it, using the same name for the lock (maybe that's the error - but ot shouldn't be), exact same parameters for the Keymaster dialog as I had screenshot the form. Nothing changes, Cabin1 entities are still unavailable just after Keymaster integration addition.