However, if the elk restarts, your custom values are set to zero, and also CQC can't read changes made to custom values made by the elk via rules. Add to this the fact that there is no persistence in CQC and that you can't for example turn your sprinklers on every fourth day (only 4th day of the month. Means that for a 31 day month, you water on the 28th and then the 4th of the next month) from within the elk it's not a great solution. I for one am not interested in having CQC determine when I should water - don't trust the PC to keep running while I am away.Awesome rules from that link!
But that image is awesome. What app is that?
Thank you so much!
That screenshot's from my CQC setup. (www.charmedquark.com). You should give it a try, it has a 30 day trial. It has supported the ElkM1 for years, but the latest beta includes features to update custom values (the durations on the right on the screen shot).
Here is a link to the rest of my screenshots:
CQC BlueGlass Theme
So until CQC supports persistence and can read custom counters, and the Elk can support rules like "every fourth day" I think the Elk is a poor solution. I have 28 valves running and would not have used the Elk had I understood the limitations prior to implementation.
And hold onto your hat waiting for Elk. Their rate of updates is very slow and you never have any idea of what is going to be added until it arrives (or doesn't most likely)!