add message broker support about ebusd

[andig]

Could you add something simple like e.g. an integrated web server or plain web sockets, too? Using something like node-red its dead simple to add MQTT support but it needs some basic "getting the data out" capabilities.

E.g. https://github.com/volkszaehler/vzlogger uses integrated microhttpd for that purpose.

[john30]

a web server is already integrated, but still treated as experimental (see http commandline options). When enabled, the messages and fields are available as JSON using the /data/ url suffix.
could you point me to the documentation part of node-red for the data lookup feature you are referring to?

[andig]

a web server is already integrated, but still treated as experimental

Great, I'll take a look,.

update it seems the daemon's http server is only accepting connections on localhost. Any chance to make binding to 0.0.0.0 configurable?

could you point me to the documentation part of node-red for the data lookup feature you are referring to?

I would generally refer you to http://nodered.org/. using node-reg you can easily "wire" any IOT application to anything else. It speaks http, websockets, mqtt and you name it out of the box. My idea was that- rather than implementing any specific logging technology- keep ebusd simple by implementing the most stupid of push mechanisms possible (e.g. web sockets) and leave everything else to the user side, e.g. by deploying node-red to convert "simple" to "custom" logging.

[john30]

no, a HTTP connection is accepted from any port, not only localhost, so I guess you have some firewall issue or something else.
for node-red please check if it supports subsription to MQTT topics. If so, then node-red will be supported automatically once the MQTT support is finished.

[andig]

no, a HTTP connection is accepted from any port, not only localhost, so I guess you have some firewall issue or something else.

Right. Used port was blocked by client machine.

for node-red please check if it supports subsription to MQTT topics

Should definitely be possible. My personal preference would have been simple web socket as it doesn't require setting up an MQTT broker but in the end it will also serve the purpose.
Looking forward to the next version to replace logfile parsing with MQTT/node-red!

[john30]

if you're only interested in pickung up the data from ebusd, then try the HTTP port and the URL http://<ebusdhost>:<ebusdhttpport>/data/

Personally, I use this with fhem and a JSONREADINGS device like this:

define jsonebus JSONREADINGS http://127.0.0.1:8080/data/ 60
attr jsonebus delay 60

[john30]

solved with da58804 and already documented in the wiki