Hi akbooer,
I have some plugins that are communicating using TCP and the status attribute keeps changing to 2 and back to -1 all the time. One plugin uses a direct socket call, one an http request and a third the luup.inet.wget. The communication is working just fine and I do not see the same behavior on a Vera. The Netatmo plugin shows the same behavior btw (Version 2018.02.27, but also prior versions). I cannot find anything in the logs that is changing the status attribute.
It is not impacting the functionality, but I am just wondering why this is happening. Also having the screen showing red all the time without a real issue present is a bit annoying.
Running openLuup v18.2.26 on a PI.
Cheers Rene
Yes, this has been happening for a while. VeraBridge does it too…
…I was about to revamp the device and job status anyway, as @amg0 has now told me how to get messages into the AtlUI message area.
I believe that this is fixed in the latest development commit v18.4.5b
Let me know!
Looking good so far. Thanks again.
Cheers Rene
Thanks to you for reminding me of the issue!
Edit: for the technically minded, this arose because of yet another of those bizarre Vera/MiOS design choices… although “status” appears in user_data as a normal device attribute, it is NOT, because you can’t retrieve it with luup.attr_get()
This actually led to the id=user_data request returning a different status from the id=status request! Further refactoring is underway, but this fix should be fine for the time being.
