Odd. It doesn’t generate any error for me, not on save and not at runtime. @dennypage’s explanation sounded reasonable to me, and it has fixed he issue. I’ve never seen an error since I made that change.
It must be something subtle because it’s not a 100% failure, just most of the time without this change.
It might be a timing thing because I don’t have as many devices as many of you do. Denny was finally able to reproduce it, though. I believe it started upon the 2.2.9 release with its concurrent Z-Wave radio update. No new devices here.
I’m willing to try any debugging to see if something else is going on. All I can say is that, upon making that simple change, the app started working again.
I detailed all the configuration stuff above to try to help Tony and Denny figure out what the issue was.
