Because after adding the virtual device in HE, you add a new device node in NR and deployment triggered a cache rebuild
Yes, you will probably see a javascript error in the NR log file. The best I can do, is catch this error and print a formatted error message. I would require some effort to support new attribute
No everything is fine, but you need to restart flow to rebuild the global cache. Or use this flow to rebuild cache without restart
When a new device is added or updated the global cache must be refreshed. Adding a new device node will trigger it, so it's why nobody see this. But if you update an attribute of existing device its more problematic
I feel like a snail when I answer a question, trying to translate what I want to said, write, delete, write, fix, then finally not sure about what I'm writing, then testing, rewrite and finally click on reply ... but I re-read myself and I don't even understand what I have written, so edit my message and do the same steps again...
Anyways not surprising that everyone had time to reply before me
Thanks for the update, can't wait to "play with it"
But seriously, is there a way to "store" a variable in NR in such a way that it's value appears on the flow like say a temp sensor? Right now I pipe the data into a virtual device and display that, seems crude.
No, I just lifted someone's graphic -- using it as an example. Personally, I don't care for it. But, everyone should use the tool that works best for them.
I actually really like RM, and use it for various non-complex things if I'm in a hurry. It is really a very nice solution that works very well.
I do most in node-red, though, as I prefer to drag/drop, copy/paste, connect the dots, not worry about resource usage or speed, and can dump into JS in a pinch if needed. Works well for the way my brain thinks.