Closed EdLeckert closed 11 months ago
Kudos, SonarCloud Quality Gate passed!
0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells
No Coverage information
0.0% Duplication
should I do a release for this? I am guessing it doesn't help for those who already upgraded though?
I doesn't help those who have already upgraded...they can disable it manually as I explained in Issue #249.
However, for those who have not upgraded, it will save them that trouble, so if it's not too much trouble to release it might be worth it. It's up to you. I've been running with it that way for a month or two and it didn't bother me, but some find it annoying. Two have noticed and reported it so far.
Also know that I'm working on a possible fix for #248. I doubt that many installations are anywhere near as large as this one, but I can't know for sure. My idea is to add an option to Config Flow and Options Flow to not create the Program entities, warning users of the number of entities that would be created. Should have something for you to look at in a day or two.
Disables
sensor.opensprinkler_current_time
by default. Addresses Issue #249.Was planning to remove this entity and replace with a service, but now that it's released I think this is the way to go. Can still add a service later.
We don't need a constant update of the current time, but I have found it to wander in the past unexpectedly, so it's nice to have a way to check periodically.