As a long-time enthusiast of home automation, I’ve always been on the lookout for seamless integrations and innovative solutions. Recently, I’ve been diving into the world of Eedomus, a French automation gateway that natively supports Z-Wave connections. Their well-documented API has opened up a whole new realm of possibilities for me, and I’m excited to share my journey and some tips along the way!
One of my current projects revolves around creating a custom sensor setup to track the last status of my back door lock. While it’s straightforward to monitor the current state, I wanted a way to display the previous status, such as who last unlocked the door. This led me to explore template sensors in Home Assistant. Here’s a quick snippet of what I came up with:
sensor:
- platform: template
sensors:
template_back_door_unlock_status:
value_template: >
{% if is_state(‘sensor.back_door_alarm_level’, ‘2’) and is_state(‘sensor.back_door_alarm_type’, ‘19’) %}
User1
{% elif is_state(‘sensor.back_door_alarm_level’, ‘3’) and is_state(‘sensor.back_door_alarm_type’, ‘19’) %}
Guest 1
{% elif is_state(‘sensor.back_door_alarm_level’, ‘4’) and is_state(‘sensor.back_door_alarm_type’, ‘19’) %}
Guest 2
{% elif is_state(‘sensor.back_door_alarm_level’, ‘5’) and is_state(‘sensor.back_door_alarm_type’, ‘19’) %}
Guest 3
{% endif %}
friendly_name: ‘Last Unlocked by’
This setup allows me to track the last user who interacted with the lock, adding a layer of security and convenience. However, I’m still experimenting with how to persist this data even after the lock state changes. If anyone has tips or alternative approaches, I’d love to hear them!
On another note, I’ve been impressed by the Eedomus API’s flexibility. While I’m not a developer, I’ve managed to set up a test environment to explore its capabilities further. If anyone is interested in collaborating or needs help with testing, feel free to reach out—I’d be happy to assist!
One challenge I’ve encountered is ensuring that my automation rules don’t interfere with each other, especially when dealing with battery-powered devices like my shades. I’ve found that using a combination of delays and state checks helps prevent unintended behavior. For example, I programmed my shades to open at sunrise but added a 5-second delay to account for any initial communication lags.
If you’re also working on similar projects or have questions about Eedomus integration, custom sensors, or automation rules, I’d love to connect and share insights. Let’s keep the community spirit alive and continue to innovate together!
Cheers,
[Your Name]