micro-ebusd doesn't work eBUS Adapter Shield v5

[Fortune95]

So far, I have been running regular ebusd in LXC containers and have tried to switch to micro-ebusd. The adapter does not establish a connection to the Ebus. Or does micro-ebusd only work with HA? I am currently using ioBroker.

Log.txt

[john30]

that shouldn't make a difference, but I'll check

[john30]

did you setup an MQTT broker? or which way do you plan to get the data?

[Fortune95]

I currently receive the data via the Ebus adapter in iobroker.

https://github.com/rg-engineering/ioBroker.ebus

`"_This adapter reads

data from ebusd using html In this case ebusd must run and must be able to send data to e.g. explorer via http://ip:port/data (http://192.168.0.123:8889/data) Current version of ebusd incl. configuration files can be copied from https://github.com/john30/ebusd All fields with data, lastup and from global section are parsed. All others are ignored at the moment. There is a possibillity to poll data which are not polled by ebusd directly. Command 'read -f' is used to force reading over ebus."_`

[john30]

the issue was with the fix ip address on ethernet. should be solved with new version, please check.

for iobroker the easiest would also be to use MQTT with micro-ebusd, as the mentioned plugin seems to use a weird combination of different access to the data on ebusd, which are not comparable in micro-ebusd in the first place. but I'm not an expert for iobroker (yet) :) I'll try iobroker to see what it can do

[john30]

ok, so basically it is quite simple to get the data into iobroker:

1. add an MQTT client adapter instance
2. configure it to connect to your MQTT broker
3. configure the eBUS adapter to use some topic within the iobroker toppic (as configured in the MQTT settings there)
4. then the data from micro-ebusd simply appears as objects in iobroker under the corresponding topic path

since the data is in JSON, it seems some tiny layer needs to be added as the iobroker MQTT client does not have an option to configure the payload as being JSON (at least I didn't find that). So in order to e.g. get the outside temperature as number, right click on the object under the eBUS adapter objects in iobroker in the path broadcast/outsidetemp and pick "create alias". in the dialog, check "use convert function" and put this in the "read formula": JSON.parse(val).value then the real value appears in the alias section

alternatively, it should also work with using the "MQTT Broker/Client" adapter of iobroker and configure micro-ebusd to use that as the MQTT broker

[Fortune95]

Thank you very much for the quick solution. The adapter is now connected to the EBus. I will try your advice about MQTT.

[john30]

it is a lot easier with the "MQTT Broker/Client" (configured as a client in my trial) as it automatically subscribes to everything, so all the topics automatically appear anyway

[john30]

there is even a special adapter for automatically importing the discovery data sent by eBUS adapter to home assistant, but unfortunately it is not maintained any more and also seems not to work correctly. it finds some sensors but does not update any of the values. maybe I'll adopt the repo at some point :)

[Fortune95]

Could you give me a tip on how to read data via MQTT? I can only see the “broadcast” data. The Ebus adapter from iobroker queries all defined parameters every 5 minutes. It would also be interesting to know how to write. I use it to activate the “Speicherladung.” :-)

[Fortune95]

🙈🙈Have overseen this awesome "Messages" Tab/window!😊😊😊 Need only a tip for writing a parameter over mqtt.

[Fortune95]

Ok, I realized that the Tab "Messages" is only visible when HA is enabled under MQTT. Tried to write on a parameter in iobroker but it didn't work.

[Fortune95]

Finally I also find out to write. I had to create an additional mqtt instance in iobroker as "client" from that instance I was able to write. Only a few messages under the circuit "bai" were not decoded and missed over mqtt.

[john30]

the messages tab visibility only depends on whether micro-ebusd is running (not on the MQTT config), so it does not appear from the very start but a bit later. the missed bai messages should be solved with the new release from today

[Fortune95]

There is still one unknown message.

"ebusd: received unknown 1008b5110100 / 08e8021132040f0081"

Log.txt

[Fortune95]

Found some more unknown messages.

Log1.txt

[Fortune95]

Normal Ebusd info:

version: ebusd 25.1.25.1 device: /dev/ttyACM0, serial high speed, enhanced, firmware 1.1[5b17].1[5b17] signal: acquired symbol rate: 22 max symbol rate: 134 min arbitration micros: 2 max arbitration micros: 4 min symbol latency: 4 max symbol latency: 4 scan: finished reconnects: 0 masters: 3 messages: 717 conditional: 0 poll: 0 update: 16 address 03: master #11 address 08: slave #11, scanned "MF=Vaillant;ID=BAI00;SW=0518;HW=7401", loaded "v aillant/bai.0010006101.inc" ([Scan_id_product='']), "vaillant/08.bai.csv" address 10: master #2 address 15: slave #2, scanned "MF=Vaillant;ID=70000;SW=0614;HW=6903", loaded "va illant/15.700.csv" address 31: master #8, ebusd address 36: slave #8, ebusd

[john30]

the 1008b5110100 is generally unknown and should as well be when using ebusd. the same is true for the other ones. some of them are decoded once the message definition is loaded though (SetMode and Status01). so all as expected from my point of view, or what are you missing exactly?

[Fortune95]

Yes you are right, I compared both logs and same messages are unknown, so nothing is missing. This issue can be closed. When will the permanent token be available? I'm looking forward to switching to µebusd permanently. :-) Thank you very much for your support!

[john30]

permanent tokens are available now. closing this one as completed