Hi!
I have not seen that so far, but on another rest sensor that this happens from time to time.
I solved that with a automation that reload the rest-sensor if the sensor state become unavailable.
So in your case should be something like this:
Trigger:
platform: state
entity_id: sensor.hallway_front_door_lock_last_event
to: unavailable
reload rest:
service: rest.reload
data: {}
Call service to update rest sensor:
service: homeassistant.update_entity
data: {}
entity_id: sensor.hallway_front_door_lock_last_event
Give it a try an see if it helps to avoid getting that state.
Awesome. Happy to share how I got the template lock setup with the sensors to add battery levels (and alert). I then exposed that to Homekit to so I can control it via the Apple Home app etc (and add as an actual lock to Home Assistant dashboards and not a switch).
Thanks for this! So I added an extra with to the template (meaning if the sensors go unavailable / blank) the lock status is still “true”, then it doesnt unlock itself. I tested it by adding the extra bits to the template and then cut off internet access via my router.
Saw the state change in HA logs, and the locked stayed locked (phew!). Template below
value_template: “{{ is_state(‘sensor.hallway_front_door_lock_last_event’, ‘remoteLock’) or is_state(‘sensor.hallway_front_door_lock_last_event’, ‘manualLock’) or is_state(‘sensor.hallway_front_door_lock_last_event’, ‘’) or is_state(‘sensor.hallway_front_door_lock_last_event’, ‘Unknown’)}}”
Unfortunately not. The lock is actually bluetooth enabled, but no integration yet, otherwise you could have HA connect directly via bluetooth and communicate offline only.
There are plenty of other locks with integrations out there. Depends on what you are looking for. Good luck!
Can HA be programmed so that when i unlock one door, the other 3 doors will unlock too ?
my house has 2 doors and the guesthouse has 1 that i want to have unlocked at the same time the front door unlocks. It would be a pain in the ass if i forget the phone when i go to the guesthouse and finds out thats its locked.
Sure. If you have all locks integrated in HA, I am sure a simple automation to unlock all locked doors, if one of the three doors is unlocked, would be simple enough.
So it seems like, from what I can see, nothing needs to change.
Under the last breaking change for 2023.6 you can see the below for “Command Line”
The Command Line integration changes its YAML configuration format from an old-style platform configuration to a more modern integration-style configuration format.
For example, if you have a binary sensor configured previously as:
Example configuration.yaml entry
binary_sensor:
platform: command_line
command: “cat /proc/sys/net/ipv4/ip_forward”
YAML
That same binary sensor is now configured under the command_line integration configuration as:
YAML
Note: While this is currently not yet a breaking change, it did raise questions during our beta testing period. Hence we have added this as a breaking change to provide more context.
It seems for now based on your solution nothing changes as it is already correctly formatted.
However, still not 100% sure if the “Repair” note:
Command Line YAML configuration has moved
This stops working in version 2023.8.0. Please address before upgrading.
Configuring Command Line switch using YAML has moved.
Consult the documentation to move your YAML configuration to integration key and restart Home Assistant to fix this issue.
Thanks. Seems like I don’t get them anymore. Perhaps the API calls were failing for some other reason.
FYI - För some reason after the December HA updates the original command switch creation in a switch.yaml stopped working. Moving command switch to config.yaml works fine (friendly_name: has been deprecated, you need to use name:")
