I have such a great integration with Loxone to be shared, but lack of that data would be just a shame 😞
I have already found that if I manually change value within ioBroker panel (for instance: remaining filter, from 92% to 90%) then the value gets published to MQTT instantly. But they don't get published upon MQTT-client adapter restart, despite setting publish - enabled ("changes only" is not checked). And as those values change very rarely, I would need to wait long tome to get them published for the first time....
Any idea on workaround such as forcing initial publish of all mqtt-client configured values?
@ap2017 this error message is "ok".. one device has a timeout .. and the herdsman send this message...
Hi arteck 🙂
If an error message is "ok", wouldn't it make sense to catch the error, change it to a "warn" and not "error" message and limit to one single log line?
If you agree, then I will open a Github issue to consider for future updates.
They say good for many objects such has 10000 for performance reasons
I would assume this statement in the documentation was just made for the ease of use of ioBroker in general: Without like Redis, typically ioBroker's performance is good if you have way less than 10000+ objects. You are having a different use case (limited disc r/w per period). Not sure how the performance (like CPU and memory usage) of Redis is on a Raspberry, but I guess pretty low.
instead of the mqtt-in node - you can use the "iobroker in" node.
So if you have open your node red - drag an "iobroker in" node into the flow area. Configure this node by opening this node - and select your datapoint of your temperature sensor - as you can see in my screen-shot.
Then wire for the first time a debug node to the "iobroker in" node and have the debug window open in node-red.
Everytime your temperature will change generates a new message, which you can see in the debug window.
With this message - containing the temperature you can do what you want. Create your json string, you can use to put it in an other data object, write to a file, a database, put in an http-request and even use the simple api.
That's exactly the point. The config is determined by manufacturer and product and that's also what is displayed in the admin screen. But the name of the channel is taken from the valueId label.
So: the device is not in the openzwave database but it still reports the name.
Fix: report it to openzwave