John30 seems to do a new release about every 6 months so might be a while.
You could try docker compose and use latest or developer version of ebusd. I’m using portainer and start stacks from there.
Thanks @timstanley1985, I switched to ebusd-edge…and the unmatchable topic error is not showing up…but instead I get an error if I write (change input number):
2022-02-16 20:50:37.839 [mqtt debug] received topic ebusd/hwc/StorageTempDesiredStop/set with data 57
2022-02-16 20:50:37.839 [mqtt info] received set topic for hwc StorageTempDesiredStop
2022-02-16 20:50:37.839 [mqtt error] write message hwc StorageTempDesiredStop not found
2022-02-16 20:50:41.989 [main debug] performing regular tasks
Any clues?
Thanks!
Hi. I have a problem… I use EBUSD EDGE and use mqttvar:
filter-name=status|temp|fuel|count|energy|power|runtime|hours|starts|mode|curve|^load$|^party$|cooling|heat|sensor|data|error|pressure|flame
then i have sensors by auto discovery. He found me what i need.
Then i create in climate thermostat but it is no working:
- platform: mqtt
name: Parter podłogówka
max_temp: 30
min_temp: 5
precision: 0.1
temp_step: 0.5
modes:
- auto
- heat
- cool
- "off"
mode_state_template: >-
{% set values = { 'auto':'auto', 'day':'heat', 'night':'cool', 'off':'off'} %}
{{ values[value] if value in values.keys() else 'off' }}
mode_state_topic: "ebusd/700/z2OpMode"
mode_command_topic: "convert/z2modeset"
temperature_low_state_topic: "ebusd/700/z2NightTemp"
temperature_high_state_topic: "ebusd/700/z2DayTemp"
temperature_low_command_topic: "ebusd/700/z2NightTemp/set"
temperature_high_command_topic: "ebusd/700/z2DayTemp/set"
current_temperature_topic: "ebusd/700/z2RoomTemp"
please help me… On old addon 0.87 this works with no problem.
Have you done anything to try and debug this yourself before asking questions? What do your logs say? Are all the sensors listed in the config working? Does the command topic work?
Thanks @timstanley1985 and @Mozzarella
Since @andrej33 and @pepeEL are also still having problems with writing I’d like to switch back to V0.87 until there’s a stable release which works for writing.
I’m going to try a selective restore from a backup as suggested here and see if I can get back to 0.87
1 Like
Possible rounding error on a writable sensor.
I’ve got this number sensor which is the only one with a red underline
The hover popup reads
Please enter a valid value: The two nearest valid values are 16.06 and 17.06
Developer->states shows it as
I’m not sure where it specifies this as an integer (step: 1) value (although it probably is) but the x.06 is a bit weird. This value has previously shown as a non-integer number (17.06… with extra trailing digits I can’t remember)
The ebusd-configuration is here at line 20
It’s not really a problem but I thought I’d mention it.
Thanks to all for the really good work on this addon
Well restoring the backup didn’t work 
It appeared to install 0.87 (according to HA) but a -V command lime parameter to ebusd shows 22.1 (the latest)
So the container is 0.87 but the executable is 22.1
Really stuck now with not being able to write…
Topic looks that work. When send by MQTT Explorer command ebusd/700/z2OpMode/get i recived:
{ “opmode”: {“value”: “auto”}}
In logs no show any errors…
I also think that 0,87 is more stable than version with auto discovery
To disable discovery remove any text from the the mqttint field and switch off mqttjson. This should return the addon back to 0.87 functionality.
If you really wanted to roll back you could also clone the add-on repo into your /addon folder and tweak the dockerfile of ebusd-edge to clone an older version of ebusd and build if you are adamant you need the older binary version.
That being said, if it was me I would persevere with auto-discovery and try and make it work for you (raising issues on the ebusd github if you spot bugs) rather than sit on an old version.
I would log this as an issue on the ebusd github. You could try tweaking the section at line 230 of mqtt-hassio.cfg and making a pull request if you find something that works.
OK - I’ll log it after I’ve had another go at getting 22.1 to work for me.
Re: the tweaking of mqtt-gassio.cfg I’ll have to research what this entails before I embark on another ‘project’
I decided to give the edge variant a try.
After the first attempt crashing my pi I got it installed (probably low memory - pi 3).
It does not work for me at all
Log
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
> ebusd --foreground --mqtthost=core-mosquitto --mqttport=1883 --mqttuser=addons --mqttpass=xxxxxxxxxx --readonly --scanconfig --mqttjson --mqttlog --latency=0 --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqtttopic=ebusd --device=/dev/ttyUSB0 --log=all:notice
2022-02-17 18:06:57.694 [main notice] ebusd 22.1.v22.1-32-gea60ef9 started read only with auto scan on device /dev/ttyUSB0
2022-02-17 18:06:58.980 [bus notice] bus started with own address 31/36
2022-02-17 18:06:58.988 [mqtt notice] connection established
2022-02-17 18:06:58.994 [bus notice] signal acquired
2022-02-17 18:07:01.695 [bus notice] new master 10, master count 1
2022-02-17 18:07:01.695 [update notice] received unknown BC cmd: 10feb5050427001f00
2022-02-17 18:07:02.129 [update notice] received unknown BC cmd: 10feb505034a0100
2022-02-17 18:07:03.966 [update notice] received unknown MS cmd: 1023b505072b001900000000 / 00
2022-02-17 18:07:04.205 [bus notice] new master 03, master count 2
2022-02-17 18:07:04.205 [update notice] received unknown MS cmd: 1008b511020300 / 0af901fe05b502032c0000
2022-02-17 18:07:04.365 [update notice] received unknown MS cmd: 1008b5110102 / 050000c800c8
2022-02-17 18:07:05.962 [update notice] received unknown MS cmd: 1008b509040ed10000 / 00
2022-02-17 18:07:06.474 [update notice] received unknown MS cmd: 1008b50903290100 / 050100d90100
2022-02-17 18:07:08.039 [update notice] received unknown BC cmd: 10feb516080000071917020422
2022-02-17 18:07:08.215 [update notice] received unknown BC cmd: 10feb51603018003
2022-02-17 18:07:08.727 [update notice] received update-read broadcast datetime QQ=10: 3.500;19:07:00;17.02.2022
2022-02-17 18:07:08.988 [main error] scan config 08: ERR: element not found
2022-02-17 18:07:09.206 [update notice] received unknown BC cmd: 10feb51603043005
2022-02-17 18:07:09.780 [update notice] received unknown MS cmd: 1008b50903290700 / 0507009d0100
2022-02-17 18:07:09.956 [update notice] received unknown MS cmd: 1050b5040101 / 09170400000081000100
2022-02-17 18:07:10.119 [update notice] received unknown MS cmd: 1050b504020d00 / 051900f00117
2022-02-17 18:07:10.307 [update notice] received unknown MS cmd: 1050b5040132 / 0a001a0603010130050100
2022-02-17 18:07:10.453 [update notice] received unknown MS cmd: 1050b5040131 / 020001
2022-02-17 18:07:10.989 [main error] scan config 15: ERR: element not found
2022-02-17 18:07:11.907 [update notice] received unknown BC cmd: 10feb5050427001f00
So I now have endless unknown xx cmd: and scan config errors.
No sensors are detected.
I know this an ebusd issue not the addon but the end result is I’m below square 1.
I’m out of my depth with this one so I’m going to think out which way I want to go.
Really pining for the executable in V0.87…
For the record which version of ebusd was in V0.87 - maybe I can squirt it into the container?
[edit]
I think it must be Quince (21.3)
Your config has read only set, is that why your write sensors weren’t working?
I would also try unsetting your latency, eBUSd should set this automatically
I want use Auto Discovery but for me now not working and i dont know why… also i dont have many know to resolved problem. I also send on github problem but with no answear
For those having issues try pushing rebuild on eBUSd Edge. John30 has just merged a commit which looks like it might resolve some issues
For information, I had the exact same problem.
After 2 days of research, I notice that HA is using a local DNS server running on my HA.
After modifying the DNS config of HA so that it uses the DNS server of my FIA box, the installation of the ebusd add-on goes correctly
Issue with unknown command I solved with --accesslevel=*
I have a question:
[mqtt debug] publish ebusd/global/updatecheck revision v22.1 available, broadcast.csv: different version available, memory.csv: different version available
What does different version available means? Where does it get info about different version?
I have copied CSV files to /config folder in HA… Does it check the “local” files to those on github?
Thanks!
Help on mqtt-hassio.cfg please.
I’m now using my own (in order to get all my sensors).
I’ve got my sensors covered in filter-name = and write access with filter-direction = r|u|^w
Is it possible to define an input_select for an ebus item which has a selection of string values?
Specifically ebusd/hwc/OperatingMode which is defined as hwcmodes which are on/off/auto
I see there is a section in the cfg file
type_switch-list =
binary_sensor,,measurement = onoff
sensor,, =
and I feel it should be possible to add it here but the documentation in the file has baffled me.
I’m guessing the line would be something like input_select,,measurement = hwcmodes but it will also need linking somehow to the ebus item…
Thanks