Since almost all door sensors are either on/off, yes binary sensors only.
I hope someone can help me with this
I set up everything as per installation instructions
when I paste the lovelace code, I get the cards but i get " entity not available: sensor.connected :" and " entity not available: binary_sensor.active" errors.
What am I doing wrong?
Hey yāall! I converted our garage hallway lock to a child lock and am getting the error below. I have removed and readded the integration multiple times. Even with the error, code sync is working but obviously Iām unable to restart HA services with the failed validation.
Thoughts?
I believe there was an indention issue in the generated yaml, Iāve just pushed a new release that should resolve that.
Deleted the child lock.
Updated key master in HACS to 0.72
Tried setting up the child lock with the same parameters and receive this error. Note that it does not generate any files or entities.
What version of HA?
Configuration ā Info hit the Copy icon on System health and paste it in your reply.
System Health
version: core-2021.10.1
installation_type: Home Assistant OS
dev: false
hassio: true
docker: true
user: root
virtualenv: false
python_version: 3.9.7
os_name: Linux
os_version: 5.10.62
arch: x86_64
timezone: America/Chicago
GitHub API: ok
Github API Calls Remaining: 4495
Installed Version: 1.15.2
Stage: running
Available Repositories: 881
Installed Repositories: 40
logged_in: true
subscription_expiration: November 6, 2021, 7:00 PM
relayer_connected: true
remote_enabled: false
remote_connected: false
alexa_enabled: true
google_enabled: false
remote_server: us-east-1-1.ui.nabu.casa
can_reach_cert_server: ok
can_reach_cloud_auth: ok
can_reach_cloud: ok
host_os: Home Assistant OS 6.4
update_channel: stable
supervisor_version: supervisor-2021.10.0
docker_version: 20.10.7
disk_total: 916.2 GB
disk_used: 389.0 GB
healthy: true
supported: true
board: generic-x86-64
supervisor_api: ok
version_api: ok
installed_addons: Samba share (9.5.1), Z-Wave JS to MQTT (0.26.0), Node-RED (10.0.1), Mosquitto broker (6.0.1), Home Assistant Google Drive Backup (0.105.2), Network UPS Tools (0.8.0), AirSonos (3.1.1), Grafana (7.2.0), InfluxDB (4.2.1), deCONZ (6.10.0), Portainer (2.0.0), Duck DNS (1.14.0), WireGuard (0.5.1), Dnsmasq (1.4.4), SSH & Web Terminal (9.0.1), Visual Studio Code (3.6.2), Vaultwarden (Bitwarden) (0.13.0), Frigate NVR (2.0), MariaDB (2.4.0), Nginx Proxy Manager (0.11.0), ESPHome (2021.9.3)
error: failed to load: unknown
dashboards: 5
resources: 26
views: 22
mode: storage
And you restarted Home Assistant?
Yes. I also just upgraded to 2021.10.2 and tried installing the child lock with the same error.
Maybe remove both the child and parent configs, restart and try readding both?
give it a shot
Alrightā¦so I removed all key master configs, reinstalled key master 0.72, and restarted HA.
Installed parent lock no problem, installed child lock, and get the same error.
I downgraded to key master 0.71 and was able to get both child and parent to install successfully but still getting the original error.
Soā¦I looks like 0.72 may have fixed one problem but then caused another.
Let me know if there is anything else I can test.
Please raise a bug on github.
1 Like
Done.
I did find a workaround downgrading to 0.63 setting up both parent and child locks then upgrading to 0.72
Iāve been thinking about this a lot ever since you mentioned it. Iām working on a beta with that removed. I hope to have it published after I give it a test run with the bbq.
Also ran into the issue although I was upgrading from the old non HACS integration to keymaster. How do you go about the process you mentioned? Did you just remove the integration from HACS? How do you then go about installing the older version?
The first thing I did was deleted both of my key master locks from Integrations. Obviously youāll want to take a screenshot of your names, codes and other settings.
I restarted HA for good measure.
Then go into HACS, find Keymaster, hit the three dots, and select reinstall. Youāll have the ability to select an older version. I installed 0.0.63.
After this I think I restarted HA again at this point then went through the process of reinstalling my parent and child keymaster locks which was successful. After that I was able to go back into HACS and upgrade Keymaster to the latest version which is now 0.0.74 and I have had no problems on this version.
The root problem seems to be with 0.0.7x versions generating correct config files.
New to keymaster, everything seems to be setup fine.
But IĀ“m not able to add pins to keyslots, the ui is stuck on āaddingā state.
Have set the plugin to debug but i donĀ“t see anything beneficial
2021-10-17 17:56:00 DEBUG (MainThread) [custom_components.keymaster] Add Code service: <ServiceCall keymaster.add_code (c:12b1c2cdabbfb8d1357675d38746e8aa): entity_id=lock.z_wave_module_for_id_lock_150_and_101, code_slot=11, usercode=123456>
2021-10-17 17:56:00 DEBUG (MainThread) [custom_components.keymaster.services] Attempting to call set_usercode...
Then it just refreshes the code slots into eternity, but no more messages about the problem that i can see.
Also tried manually adding a key with via the services page, but itĀ“s the same results.
Any suggestion on where to start debugging?
Newest plugin
Id-lock 150
Zwave JS
Grepped the logs and exclude the following line
- DEBUG: Code slot
- Finished fetching keymaster data
This gives us
2021-10-17 16:19:10 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'click' when rendering '{{ value_json.click }}'
2021-10-17 16:19:20 DEBUG (MainThread) [custom_components.keymaster] Add Code service: <ServiceCall keymaster.add_code (c:08435ab856e150dac4cf3dcfda4da4d3): entity_id=lock.z_wave_module_for_id_lock_150_and_101, code_slot=11, usercode=77882233>
2021-10-17 16:19:20 DEBUG (MainThread) [custom_components.keymaster.services] Attempting to call set_usercode...
2021-10-17 16:20:10 WARNING (Recorder) [homeassistant.components.sensor.recorder] sensor.stue_motion_unknown_0x01 has unknown unit None
2021-10-17 16:20:10 WARNING (Recorder) [homeassistant.components.sensor.recorder] sensor.eye_unknown_0x01 has unknown unit None
2021-10-17 16:21:17 DEBUG (MainThread) [custom_components.keymaster] Add Code service: <ServiceCall keymaster.add_code (c:25288f4cedab2b9c0e2e1603a227f294): entity_id=lock.z_wave_module_for_id_lock_150_and_101, code_slot=10, usercode=112233>
2021-10-17 16:21:17 DEBUG (MainThread) [custom_components.keymaster.services] Attempting to call set_usercode...
2021-10-17 17:53:34 DEBUG (MainThread) [custom_components.keymaster] Add Code service: <ServiceCall keymaster.add_code (c:a424f459f0b42c901341ceadecefba4c): entity_id=lock.z_wave_module_for_id_lock_150_and_101, code_slot=10, usercode=112233>
2021-10-17 17:53:34 DEBUG (MainThread) [custom_components.keymaster.services] Attempting to call set_usercode...
2021-10-17 17:56:00 DEBUG (MainThread) [custom_components.keymaster] Add Code service: <ServiceCall keymaster.add_code (c:12b1c2cdabbfb8d1357675d38746e8aa): entity_id=lock.z_wave_module_for_id_lock_150_and_101, code_slot=11, usercode=112233>
2021-10-17 17:56:00 DEBUG (MainThread) [custom_components.keymaster.services] Attempting to call set_usercode...
In each of the code slots try clicking on āAdvanced Optionsā and then āReset code slotā. That seems to have worked for me.
Iāve installed the integration and it is working well. Iād like to hide all the automations from the UI though since I donāt think they are meant to be edited. It also clutters it up and makes it harder to manage my other automations. Is there a way to do this?