ioBroker
It is rather simple to get the data from micro-ebusd into ioBroker.
Configuration
The following steps are needed for setup:
- ensure an MQTT client or server is configured in ioBroker. my recommendation is to use the “MQTT Broker/Client”, as it seems more capable than the “MQTT client” adapter and is automatically listening to all MQTT topics in client mode.
- get the URL of the MQTT broker and configure the eBUS adapter to use it (in the “Config” tab in the “MQTT” section) while appending some topic suffix (behind the broker URL) for the eBUS adapter, e.g. when the ioBroker IP is 192.168.0.5, then you could use “mqtt://192.168.0.5/stick” for an eBUS adapter stick
- reboot the eBUS adapter in order to publish to the broker
Then the data from micro-ebusd simply appears as objects in ioBroker under the configured topic path of the MQTT instance, e.g. below mqtt.0:
Extracting JSON
Since the data transferred is in JSON, some tiny layer is required in order to get the numeric value of each field of a message out of it.
This can be achieved by right clicking in the ioBroker object list on the message object of interest and picking “create alias”.
It opens a dialog where “use convert function” needs to be checked and the following needs to be entered in the “read formula” cell:
JSON.parse(val).value
(side note: “value” might have to be replaced with the actual field name of the message you’re interested in, in case it is not named “value”.)
After that, the field appears with the numeric value in the alias section of ioBroker.
Writing values
Writing values is a bit more tricky, since the value(s) need to be converted to JSON again.
Basically the JSON value shown in the object list is needed with the desired changes.
Then it needs to be sent to the topic of the object list with “/set” appended.
Of course micro-ebusd would issue the requested change as a message to the eBUS only if that message is also writable.