Hi everyone, I’ve been diving into setting up some automations in my smart home setup and I wanted to share my experiences and ask for some advice.
I recently set up an automation to monitor the runtime of my genset using Modbus TCP. Initially, I used a simple template to trigger notifications when the runtime exceeded a certain threshold. However, I quickly realized that comparing string values wasn’t working as intended—notifications were triggered way too early!
After some research, I switched to using integer comparisons, which worked perfectly in the developer template page. I went back and updated all my existing automations to use this new template. To be thorough, I even created additional reminders with slightly lower thresholds.
Here’s where things got interesting. Last night, the genset runtime hit 48 hours, and I received the notification for the 4750-hour service reminder. However, the 4740-hour reminder didn’t trigger. When I checked the automation logs, I noticed something odd—the automation was still showing the original template, even though the GUI and .yaml files reflected the updated version.
My theory is that the system might not have fully reloaded after the changes. I’ve heard that sometimes a full restart is necessary for changes to take effect, but I’m not entirely sure. Should I perform a .yaml restart or a full system reboot?
I’d love to hear if anyone else has encountered similar issues or has insights into why the automation might be behaving this way. Have you had experiences where changes weren’t reflected until a restart? Any advice would be greatly appreciated!
Looking forward to hearing from the community and learning from your experiences.