lukasgrebe / ha-addons Goto Github PK

Hallo Lukas,

thanks for your work.
Unfortunately it doesn't work with my system and I don't know why.

I have the ebusd Adapter v5. It is flashed with Version 2023-09-17.
The adapter is connected with my heating (Wolf CSZ 2 14/300) and the electrical circuit should work 20V DC is measurable.

I installed the HA Addon with the following config:
scanconfig: true loglevel_all: notice mqtttopic: ebusd mqttint: /etc/ebusd/mqtt-hassio.cfg mqttjson: true network_device: ens:192.168.178.21:9999 latency: 10 accesslevel: “*” configpath: https://cfg.ebusd.eu/

The bus appears in my MQTT integration with 2 devices "eBusd" and "ebusd bus device".
The MQTT Explorer shows data (only a few) but they didn't appear in MQTT.

You find my problem also here (in german) --> https://community.simon42.com/t/einrichtung-ebusd-adapter-und-integration/10008/20

Thanks

Jan

Hello,
HA turns the logos of the inactive containers into gray-scaled. Unfortunately, the current black&white logo does not makes any change. It is impossible to decide on the addons overview page that is it running or not. It requires an additional step to open the addon to check it's status.

I recommend to add a colorful background or colorize somehow the current black letters:

• icon.png
• logo.png

To conform with addon docs, an app armor config should be added https://developers.home-assistant.io/docs/add-ons/presentation

By default ebusd service comes with a config path and downloads config from the cfg.ebusd.eu or upd.ebusd.eu or ebusd.eu/config or such location.
However the download of this config is dependent on internet connectivity and may be affected by ssl issues.

DOCS.md:34:

Configuration CSV files:

Recommended to download and place in /configuration/ebusd-configuration or similar location and configure to ensure local availability.

Hi Lukas,
By upgrading the addon to version 23.2.3, the control entities (r,w type) of template/type tempv (EXP) are no longer recognized as controls by Home Assistant.
Sensors entities (r only) of same type (tempv/EXP) remains OK and r,w entities of other types are also OK.
Going back to version 23.1, control EXP type entities reappear.
File concerned: 15.700.csv
entities: z1DayTemp, z1QuickVetoTemp, Hc1MaxFlowTempDesired, Hc1MinFlowTempDesired...
Anyone else seeing this behavior?

Anyway, well done and thank you for this addon.

The log tab of the addon only shows a very small fraction of the ebusd log, i.e. I see only the latest part of it each time I click on the refresh button.
Is the full log saved in a particular file so I can check the full log ?

I have a couple ebus devices, none of which are supported by ebusd out of the box, but I was able to find a csv definition for at least one of them that would make ebusd be able to use it.
Is there a way to provide this addon with the path to such file to be loaded?

Hi, is this project still being maintained? I am happy to fork and take over but don't want to steal anyone's thunder if @LukasGrebe still wants to lead development.

I will fork in a couple of weeks if no response.

I have ordered and installed the following eBUS adapter 3 from john30:

At start-up I see the following in the add-on log:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
> ebusd --foreground --mqtthost=core-mosquitto --mqttport=1883 --mqttuser=addons --mqttpass=tienieK5eehauWi3Oow4Raech3aimeith0hu7aizoo5xaich8sietheimaLaivu7 --scanconfig --mqttjson --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqtttopic=ebusd --device=192.168.178.117:9999 --log=all:notice
2023-02-21 13:26:47.882 [main notice] ebusd 23.1.p20230106 started with auto scan on device 192.168.178.117:9999
2023-02-21 13:26:48.764 [bus notice] bus started with own address 31/36
2023-02-21 13:26:48.801 [bus notice] signal acquired
2023-02-21 13:26:49.223 [mqtt notice] connection established
2023-02-21 13:26:58.013 [bus notice] max. symbols per second: 122
2023-02-21 13:27:00.061 [bus notice] max. symbols per second: 149
2023-02-21 13:27:02.019 [bus error] signal lost
2023-02-21 13:27:02.295 [bus notice] signal acquired
2023-02-21 13:27:05.005 [bus notice] max. symbols per second: 264
2023-02-21 13:27:11.036 [bus notice] max. symbols per second: 318

In MQTT Explorer I have the following messages:

It appears that I am missing something to receive the data from the vaillant heat pump.
Why does the eBUS Adapter 3 WiFi can't retrieve and send data via MQTT?
Can you please have a look into this issue?

The integration seems to show only a 'skip' button, not an 'update' one ?

Hallo,
I installed the addons and get the parameters of my Pump displayed in HA and it works fine.
When I try to change a parameter through the following script:

alias: Test
sequence:

• service: mqtt.publish
  data:
  topic: ebusd/hwc/StorageTempDesiredStart/temp/set
  payload: 45
  mode: single

I get:
[mqtt error] received unmatchable topic ebusd/hwc/StorageTempDesiredStart/temp/set

it seems that the add-on (scan) identified or set up all parameters as sensors but some of them should be inputs

any idea ?

Thank you
Xavier

Hi
Will there be an Update available to 23.3 for the HA Addon
or is it already possible to update ?

thx Peter

Hello, is it possible to get eBus messages from two different network devices on ebusd add-on? I use HAOS and 23.2.3 ebusd add-on.
There are two network devices: 192.168.1.58:9999 and 192.168.1.78:9999 (eBus adapters v3 with esp8266)
Now I have to run virtual machine with HAOS and ebusd add-on special for second adapter.
Thanks

will this daemon work with an ebus device that communicates via wifi
https://ebus.github.io/adapter/wemosebus

Hey
I'm usually good at following steps without really understanding what i'm doing. But now it doesn't work !
I have ebus adapter shield from john.

Build: 20240106
ebusd device string: ens:192.168.86.44:9999
WiFi station/client: Nest, 192.168.86.44, 52% (-74dBm)
WiFi access point: inactive
Chip ID: 54320485bd48, ESP32-C3, rev 4
Hostname: ebus-85bd48
Up time: 4259
Free heap: 118952
ebusd connected: no
eBUS signal: acquired

When i let the MQTT config blank in ebusd add on, i get this 👍

#> [09:29:34] ERROR: Got unexpected response from the API: Service not enabled

ebusd --foreground --mqtthost= --mqttport= --mqttuser= --mqttpass= --scanconfig --mqttjson --configpath=http://ebusd.eu/config/ --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqtttopic=ebusd --device=ens:192.168.86.44:9999 --log=all:notice
ebusd: invalid mqtthost

When i fill the MQTT field, i get this :

s6-rc: info: service s6rc-oneshot-runner: starting

s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started

ebusd --foreground --mqtthost=mqtt://192.168.86.145 --mqttport=1883 --mqttuser=mqtt_user --mqttpass=Zigbee2MQTT --scanconfig --mqttjson --configpath=http://ebusd.eu/config/ --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqtttopic=ebusd --device=ens:192.168.86.44:9999 --log=all:notice
2024-02-12 10:22:25.483 [main notice] replaced old configPath http://ebusd.eu/config/ with new one: http://cfg.ebusd.eu/
2024-02-12 10:22:25.484 [main notice] ebusd 23.2.p20230716 started with auto scan on device: 192.168.86.44:9999, enhanced
2024-02-12 10:22:25.859 [bus notice] device status: resetting
2024-02-12 10:22:25.860 [bus notice] bus started with own address 31/36
2024-02-12 10:22:25.920 [mqtt error] unable to connect, retrying: Lookup error.
2024-02-12 10:22:25.943 [bus notice] device status: reset, supports info
2024-02-12 10:22:26.064 [bus notice] signal acquired
2024-02-12 10:22:26.066 [bus notice] device status: extra info: firmware 1.1[4106].1[4106], jumpers 0x0f
2024-02-12 10:22:26.293 [bus notice] new master 10, master count 2
2024-02-12 10:22:30.080 [bus notice] new master 03, master count 3
2024-02-12 10:22:30.081 [update notice] received unknown MS cmd: 1008b5070108 / 026400
2024-02-12 10:22:30.356 [update notice] received unknown MS cmd: 1008b510090000006effff01ff00 / 0101
2024-02-12 10:22:30.634 [update notice] received unknown MS cmd: 1008b5110101 / 0932350080385a0000ff
2024-02-12 10:22:30.865 [update notice] received unknown BC cmd: 10feb516080000211012020124
2024-02-12 10:22:31.081 [update notice] received unknown BC cmd: 10feb508020900
2024-02-12 10:22:36.173 [bus notice] scan 08: ;Vaillant;BAI00;0202;9602
2024-02-12 10:22:36.174 [update notice] store 08 ident: done
2024-02-12 10:22:36.174 [update notice] sent scan-read scan.08 QQ=31: Vaillant;BAI00;0202;9602
2024-02-12 10:22:36.174 [bus notice] scan 08: ;Vaillant;BAI00;0202;9602
2024-02-12 10:22:36.457 [main notice] read common config file vaillant/scan.csv
2024-02-12 10:22:36.529 [main notice] read common config file vaillant/broadcast.csv
2024-02-12 10:22:36.599 [main notice] read common config file vaillant/general.csv
2024-02-12 10:22:36.670 [main notice] read scan config file vaillant/08.bai.csv for ID "bai00", SW0202, HW9602
2024-02-12 10:22:36.971 [update notice] sent scan-read scan.08 id QQ=31:
2024-02-12 10:22:37.242 [update notice] sent scan-read scan.08 id QQ=31:
2024-02-12 10:22:37.511 [update notice] sent scan-read scan.08 id QQ=31:
2024-02-12 10:22:37.818 [update notice] sent scan-read scan.08 id QQ=31: 21;17;34;0010014601;3100;005617;N0
2024-02-12 10:22:38.067 [main notice] found messages: 202 (2 conditional on 27 conditions, 0 poll, 10 update)
2024-02-12 10:22:38.360 [update notice] sent scan-read scan.08 id QQ=31: 21;17;34;0010014601;3100;005617;N0
2024-02-12 10:22:38.621 [update notice] sent scan-read scan.08 id QQ=31: 21;17;34;0010014601;3100;005617;N0
2024-02-12 10:22:38.911 [update notice] sent scan-read scan.08 id QQ=31: 21;17;34;0010014601;3100;005617;N0
2024-02-12 10:22:39.211 [update notice] sent scan-read scan.08 id QQ=31: 21;17;34;0010014601;3100;005617;N0
2024-02-12 10:22:39.211 [bus notice] scan 08: ;21;17;34;0010014601;3100;005617;N0
2024-02-12 10:22:39.212 [mqtt error] publish: The client is not currently connected.
2024-02-12 10:22:41.191 [update notice] received unknown MS cmd: 1008b5110100 / 08950114001f000080
2024-02-12 10:22:41.461 [bus notice] scan 15: ;Vaillant;SBX00;0325;4802
2024-02-12 10:22:41.461 [update notice] store 15 ident: done
2024-02-12 10:22:41.461 [update notice] sent scan-read scan.15 QQ=31: Vaillant;SBX00;0325;4802
2024-02-12 10:22:41.461 [bus notice] scan 15: ;Vaillant;SBX00;0325;4802
2024-02-12 10:22:41.716 [update notice] sent unknown MS cmd: 3115b5090124 / 09003231313733313030
2024-02-12 10:22:42.000 [update notice] sent scan-read scan.15 id QQ=31:
2024-02-12 10:22:42.263 [update notice] sent scan-read scan.15 id QQ=31:
2024-02-12 10:22:42.391 [update notice] received update-write bai SetMode QQ=10: auto;0.0;55.0;-;1;0;0;0;0;0
2024-02-12 10:22:42.611 [update notice] sent scan-read scan.15 id QQ=31: 21;17;31;0020128485;0082;006586;N3
2024-02-12 10:22:42.611 [bus notice] scan 15: ;21;17;31;0020128485;0082;006586;N3
2024-02-12 10:22:42.680 [main error] unable to load scan config 15: no file from vaillant with prefix 15 matches ID "sbx00", SW0325, HW4802
2024-02-12 10:22:42.680 [main error] scan config 15: ERR: element not found
2024-02-12 10:22:44.165 [update notice] received read bai Status01 QQ=10: 25.0;26.5;-;28.0;45.0;off
2024-02-12 10:22:44.681 [mqtt error] publish: The client is not currently connected.

What step did i miss ?
TY for your help !

I own an ESP32 based ebusd adapter. I connected it to the ebus line of my Genus One and Cube S Net. I managed to configure the connection to WiFi and configured the connection settings on Home Assistant eBUSd. I placed the Ariston.csv in the /config folder of the home assistant OS, but most of the messages include MS and BC commands. What am I doing wrong? Please help.

The newer ebusd adapters are enhanced or high speed mode by default.
Using it over wifi may be unstable and USB mode may be preferred.
Connection over USB requires ens: prefix or changing jumpers to work in regular mode.
Such prefix is not added for the device: configuration entry when selecting usb device.
The network_device: config entry is an alias for custom device string and it supports more than its name suggests.
As simple workaround the network_device: configuration entry can have the following value: "ens:/dev/ttyUSB0"

Took some time to realize that the network_device field can be "misused" to make things work properly, maybe it can help others.

DOCS.md:11:
2. Define either a USB or network device. Seperate configuration entries are available via the UI or can be configured manually using device: /dev/ttyAMA0 or network_device: enh:192.158.0.7:9999 or network_device: ens:/dev/ttyUSB0 (for enhanced or high speed configurations)

Is it possible to find out what configuration file is used in my implementation?
MQTT shows following data for my system:
scan.15 = { "MF": {"value": "Vaillant"}, "ID": {"value": "70000"}, "SW": {"value": "0614"}, "HW": {"value": "6903"}}

I'm missing some values (e.g. Water Pressure) and want to understand, why this is not available.

It is a new version from the eBusd online.
When do you update the add on?

Thanks.

Since a few days values are not updated or ar displayed as "unknown"

• I have updatet the firmware of the adapter to the newest Release
• I have rebooted the adapter (several times)
• I have stopped and restarted the Plugin (several times)
• I have restarted Home Assistant
• I have positioned the adapter close to the router

nothing helps - no idea what has been changed

The Log-File of the adapter has no error messages
The Log-File of the AddOn shows several errors:
[code]
2023-12-13 17:45:46.042 [update notice] received read bai DateTime QQ=10: valid;17:45:47;13.12.2023;7.562
2023-12-13 17:45:46.349 [update notice] received poll-read bai Status02 QQ=10: auto;60;75.0;70;65.0
2023-12-13 17:45:46.705 [update notice] received update-read broadcast vdatetime QQ=10: 17:45:46;13.12.2023
2023-12-13 17:45:47.017 [update notice] received update-read broadcast outsidetemp QQ=10: 7.750
2023-12-13 17:45:47.173 [update notice] received unknown MS cmd: 1008b5100305ff01 / 0101
2023-12-13 17:45:47.426 [update notice] received update-write bai StatusCirPump QQ=10: on
2023-12-13 17:45:47.630 [update notice] received unknown MS cmd: 1008b5120204ff / 0101
2023-12-13 17:45:47.934 [update notice] received unknown MS cmd: 1008b513020508 / 00
2023-12-13 17:45:48.042 [update notice] received unknown BC cmd: 10feb510020601
2023-12-13 17:45:49.116 [bus error] poll 700 Hc1RoomTempSwitchOn failed: ERR: SYN received
2023-12-13 17:45:49.471 [bus error] device status: eBUS comm error: overrun
2023-12-13 17:45:55.277 [bus error] poll 700 Hc1Status failed: ERR: read timeout
2023-12-13 17:45:56.022 [update notice] received poll-read bai Status01 QQ=10: 54.5;48.5;7.750;42.0;57.5;on
2023-12-13 17:45:56.284 [update notice] received update-write bai SetMode QQ=10: auto;53.0;-;-;0;0;0;0;0;0
2023-12-13 17:46:01.152 [bus error] poll 700 Hc1SummerTempLimit failed: ERR: SYN received
2023-12-13 17:46:01.606 [bus error] device status: eBUS comm error: overrun
2023-12-13 17:46:05.705 [update notice] received poll-read bai Status01 QQ=10: 54.5;48.5;7.750;42.0;57.5;on
2023-12-13 17:46:05.913 [update notice] received update-write bai SetMode QQ=10: auto;53.0;-;-;0;0;0;0;0;0
2023-12-13 17:46:07.092 [bus error] poll 700 Hc2ActualFlowTempDesired failed: ERR: SYN received
2023-12-13 17:46:07.493 [bus error] device status: eBUS comm error: overrun
2023-12-13 17:46:13.123 [bus error] poll 700 Hc2AutoOffMode failed: ERR: SYN received
2023-12-13 17:46:15.945 [update notice] received poll-read bai Status01 QQ=10: 54.5;48.5;7.750;42.0;57.5;on
2023-12-13 17:46:16.047 [update notice] received update-write bai SetMode QQ=10: auto;53.0;-;-;0;0;0;0;0;0
2023-12-13 17:46:16.303 [update notice] received poll-read bai Status02 QQ=10: auto;60;75.0;70;65.0
2023-12-13 17:46:19.126 [bus error] poll 700 Hc2ExcessTemp failed: ERR: SYN received
2023-12-13 17:46:25.110 [bus error] poll 700 Hc2FlowTemp failed: ERR: SYN received
2023-12-13 17:46:25.157 [bus notice] arbitration won in invalid state ready
2023-12-13 17:46:25.921 [update notice] received poll-read bai Status01 QQ=10: 54.5;48.5;7.750;42.0;57.5;on
2023-12-13 17:46:26.234 [update notice] received update-write bai SetMode QQ=10: auto;53.0;-;-;0;0;0;0;0;0
2023-12-13 17:46:31.122 [bus error] poll 700 Hc2HeatCurve failed: ERR: read timeout
2023-12-13 17:46:36.073 [update notice] received update-write bai SetMode QQ=10: auto;53.0;-;-;0;0;0;0;0;0
2023-12-13 17:46:37.146 [bus error] poll 700 Hc2HeatCurveAdaption failed: ERR: SYN received
2023-12-13 17:46:43.128 [bus error] poll 700 Hc2MaxFlowTempDesired failed: ERR: SYN received
2023-12-13 17:46:46.003 [update notice] received poll-read bai Status01 QQ=10: 54.5;48.5;7.750;42.0;57.5;on
2023-12-13 17:46:46.211 [update notice] received update-write bai SetMode QQ=10: auto;53.0;-;-;0;0;0;0;0;0
2023-12-13 17:46:46.467 [update notice] received read bai DateTime QQ=10: valid;17:46:47;13.12.2023;7.750
2023-12-13 17:46:46.763 [update notice] received poll-read bai Status02 QQ=10: auto;60;75.0;70;65.0
2023-12-13 17:46:46.970 [update notice] received update-read broadcast vdatetime QQ=10: 17:46:46;13.12.2023
2023-12-13 17:46:47.280 [update notice] received unknown MS cmd: 1008b5110100 / 086e031426040f0081
2023-12-13 17:46:47.437 [update notice] received update-read broadcast outsidetemp QQ=10: 7.562
2023-12-13 17:46:49.787 [update notice] sent poll-read 700 Hc2MinFlowTempDesired QQ=31: 15
2023-12-13 17:46:55.721 [update notice] sent poll-read 700 Hc2PumpStatus QQ=31: 0
2023-12-13 17:46:56.030 [update notice] received poll-read bai Status01 QQ=10: 54.5;48.5;7.750;42.0;57.5;on
2023-12-13 17:47:01.159 [bus error] poll 700 Hc2RoomTempSwitchOn failed: ERR: SYN received
2023-12-13 17:47:06.384 [update notice] received update-write bai SetMode QQ=10: auto;53.0;-;-;0;0;0;0;0;0
2023-12-13 17:47:07.420 [bus error] poll 700 Hc2Status failed: ERR: read timeout
2023-12-13 17:47:13.800 [update notice] sent poll-read 700 Hc2SummerTempLimit QQ=31: 21
2023-12-13 17:47:13.845 [bus notice] arbitration won in invalid state ready
2023-12-13 17:47:16.260 [update notice] received poll-read bai Status01 QQ=10: 54.5;48.5;7.750;42.0;57.5;on
2023-12-13 17:47:16.767 [update notice] received poll-read bai Status02 QQ=10: auto;60;75.0;70;65.0
2023-12-13 17:47:19.123 [bus error] poll 700 Hc3ActualFlowTempDesired failed: ERR: SYN received
2023-12-13 17:47:19.478 [bus error] device status: eBUS comm error: overrun
2023-12-13 17:47:25.110 [bus error] poll 700 Hc3AutoOffMode failed: ERR: wrong symbol received
2023-12-13 17:47:26.296 [update notice] received poll-read bai Status01 QQ=10: 54.5;48.5;7.562;42.0;57.5;on
2023-12-13 17:47:26.605 [update notice] received update-write bai SetMode QQ=10: auto;53.0;-;-;0;0;0;0;0;0
2023-12-13 17:47:31.105 [bus error] poll 700 Hc3ExcessTemp failed: ERR: SYN received
2023-12-13 17:47:31.470 [bus error] device status: eBUS comm error: overrun
2023-12-13 17:47:36.391 [update notice] received poll-read bai Status01 QQ=10: 54.5;48.5;7.750;42.0;57.5;on
2023-12-13 17:47:36.680 [update notice] received update-write bai SetMode QQ=10: auto;53.0;-;-;0;0;0;0;0;0
2023-12-13 17:47:37.572 [bus error] poll 700 Hc3FlowTemp failed: ERR: read timeout
2023-12-13 17:47:43.247 [bus error] poll 700 Hc3HeatCurve failed: ERR: SYN received
2023-12-13 17:47:43.297 [bus notice] arbitration won in invalid state ready
2023-12-13 17:47:43.772 [bus notice] arbitration won in invalid state ready
2023-12-13 17:47:46.485 [update notice] received poll-read bai Status01 QQ=10: 54.5;48.5;7.750;42.0;57.5;on
2023-12-13 17:47:46.984 [update notice] received read bai DateTime QQ=10: valid;17:47:47;13.12.2023;7.750
2023-12-13 17:47:47.538 [update notice] received update-read broadcast vdatetime QQ=10: 17:47:47;13.12.2023
2023-12-13 17:47:47.753 [update notice] received unknown MS cmd: 1008b5110100 / 086e031426040f0081
2023-12-13 17:47:49.739 [update notice] sent poll-read 700 Hc3HeatCurveAdaption QQ=31: 0.0
2023-12-13 17:47:55.115 [bus error] poll 700 Hc3MaxFlowTempDesired failed: ERR: wrong symbol received
2023-12-13 17:47:56.497 [update notice] received poll-read bai Status01 QQ=10: 54.5;48.5;7.750;42.0;57.5;on
2023-12-13 17:47:56.764 [update notice] received update-write bai SetMode QQ=10: auto;53.0;-;-;0;0;0;0;0;0
2023-12-13 17:48:01.111 [bus error] poll 700 Hc3MinFlowTempDesired failed: ERR: SYN received
2023-12-13 17:48:06.586 [update notice] received poll-read bai Status01 QQ=10: 55.0;48.5;7.750;42.0;57.5;on
2023-12-13 17:48:06.891 [update notice] received update-write bai SetMode QQ=10: auto;53.0;-;-;0;0;0;0;0;0
2023-12-13 17:48:07.152 [bus error] poll 700 Hc3PumpStatus failed: ERR: SYN received
2023-12-13 17:48:13.143 [bus error] poll 700 Hc3RoomTempSwitchOn failed: ERR: SYN received
2023-12-13 17:48:17.042 [update notice] received update-write bai SetMode QQ=10: auto;53.0;-;-;0;0;0;0;0;0
2023-12-13 17:48:17.289 [update notice] received poll-read bai Status02 QQ=10: auto;60;75.0;70;65.0
2023-12-13 17:48:19.129 [bus error] poll 700 Hc3Status failed: ERR: wrong symbol received
2023-12-13 17:48:25.122 [bus error] poll 700 Hc3SummerTempLimit failed: ERR: SYN received
2023-12-13 17:48:26.815 [update notice] received poll-read bai Status01 QQ=10: 55.0;48.5;7.750;42.0;57.5;on
2023-12-13 17:48:27.062 [update notice] received update-write bai SetMode QQ=10: auto;53.0;-;-;0;0;0;0;0;0
2023-12-13 17:48:31.232 [bus error] poll 700 HcStorageTempBottom failed: ERR: read timeout
2023-12-13 17:48:37.001 [update notice] received poll-read bai Status01 QQ=10: 55.0;48.5;7.750;42.0;57.5;on
2023-12-13 17:48:37.150 [update notice] received update-write bai SetMode QQ=10: auto;53.0;-;-;0;0;0;0;0;0
2023-12-13 17:48:37.157 [bus error] poll 700 HcStorageTempTop failed: ERR: SYN received
2023-12-13 17:48:37.158 [bus notice] arbitration won in invalid state ready
2023-12-13 17:48:37.262 [bus notice] arbitration won in invalid state ready
2023-12-13 17:48:43.137 [bus error] poll 700 HolidayTemp failed: ERR: SYN received
2023-12-13 17:48:46.992 [update notice] received poll-read bai Status01 QQ=10: 55.0;48.5;7.750;42.0;57.5;on
2023-12-13 17:48:47.247 [update notice] received update-write bai SetMode QQ=10: auto;53.0;-;-;0;0;0;0;0;0
2023-12-13 17:48:47.806 [update notice] received poll-read bai Status02 QQ=10: auto;60;75.0;70;65.0
2023-12-13 17:48:48.013 [update notice] received update-read broadcast vdatetime QQ=10: 17:48:47;13.12.2023
2023-12-13 17:48:48.369 [update notice] received unknown MS cmd: 1008b5110100 / 0870031426040f0081
2023-12-13 17:48:48.517 [update notice] received update-read broadcast outsidetemp QQ=10: 7.750
2023-12-13 17:48:49.134 [bus error] poll 700 HwcFlowTemp failed: ERR: SYN received
2023-12-13 17:48:55.118 [bus error] poll 700 HwcMaxFlowTempDesired failed: ERR: SYN received
2023-12-13 17:48:55.485 [bus error] device status: eBUS comm error: overrun
2023-12-13 17:48:57.071 [update notice] received poll-read bai Status01 QQ=10: 55.0;48.5;7.750;42.0;57.5;on
2023-12-13 17:48:57.326 [update notice] received update-write bai SetMode QQ=10: auto;53.0;-;-;0;0;0;0;0;0
[/code]

Hope anyone can help....
Thanks
Volker

remove the ebusd_edge folder. It's an artifact of early development where we did not rely on the ebusd docker container and instead compiling ebusd was required.

I have a problems with loading configuration files after week of work, from container use with MQTT work ok

Hello Lukas: Thank you very much for this addon!!!
Could you please not filter it to work only on serial devices?

I mean you have:
config.yaml
schema:
device: "device(subsystem=tty)"
port: "port?"
latency: "int(0,10000)?"

I want to connect it by ip address to the ebus device.

Best regards

make it possible to see unknown messages and allow for a method to make sense of them

Hi. Your addon is very very good. But works only with adapter by USB. Is any chance to you write also second add-on to communicate by WIFI or LAN with adapter ? Please.... I use HASSOS system and i donw want use other device like raspberry to install daemon ebusd....

Hi,

i am trying to get a full log out of the Addon. It is truncated but i want to see all. So my config-File looks like this:

scanconfig: true
mqtttopic: ebusd
mqttint: /etc/ebusd/mqtt-hassio.cfg
mqttjson: true
network_device: ens:192.168.7.130:9999
loglevel_all: debug
accesslevel: "*"
commandline_options: "--logfile=/homeassistant/ebusd.log"

to get a file that i can see within HA. But it would not show up in my "File Editor" Addon. What is wrong?

Sebastian

It would be great if this Plugin would be updated to the current version 23.3 of ebusd.
Thanks a lot

According to the official documentation or here, there is a security classification.
Since the add-on uses base images of HA, then there is a possibility to certificate the add-on with CodeNotary.

Since, for our users base it is only a nice to have, we should handle it cautiously.

<=6 gives green classification instead of the current 5-'yellow':

could you add an option to allow use of enh: and ens: prefix for a serial device as well?
I guess it would be best to extract that prefix to an own setting and prepend it to the device string in the run.sh script

Hi all,

I just wonder how can I start a telnet session to ebusd container. I have configured port 8888 on ebusd network configuration menu page.

Thank you in advance.

Hey all,

I'm currently trying to use the ebus-HA-addon and in general It does what it should
I can see almost every information in HA and some values are also ready to edit.

But there are some values which will not be displayed in HA.
The addon uses the correct csv file (https://github.com/john30/ebusd-configuration/blob/master/ebusd-2.1.x/de/vaillant/15.430.csv)
And I'm currently disabled all filter (the only filter which is in my mqtt-hassio.cfg is "filter-seen=5")

For example I can see the control "HwcLegioStartDay" but not "HwcLegioStartTime".
I can see "HolidayRoomTemp" but not "HolidayStartPeriod" and "HolidayEndPeriod"

What did I wrong?

Instead of "foreground" and "Read Only", "Read Only" is shown twice. This could be an error in the UI Translatio

n

We currently have a boolean that allows the user to choose if eBUSd runs in the foreground or not. If the user switches this boolean off run.sh throws the following warning:

if bashio::config.false "foreground" || bashio::config.is_empty "foreground"; then
    bashio::config.suggest.true "foreground" "ebusd add-on will stop if ebusd is not running in the foreground."
fi

If the add-on will not run properly with foreground switched off then I propose that we remove this option and have foreground switched on by default and not user configurable.

I will raise a pull request once my other changes have been reviewed.

I am trying to update ebusd addon it fails with following error

Can't install ghcr.io/lukasgrebe/ha-addon-ebusd-armv7:23.2.1: 500 Server Error for http+docker://localhost/v1.42/images/create?tag=23.2.1&fromImage=ghcr.io%2Flukasgrebe%2Fha-addon-ebusd-armv7&platform=linux%2Farm%2Fv7: Internal Server Error ("manifest unknown")

How can I fix it pls?

Please improve your wiki with the following really useful staff:

HTTP and TCP client Access

To use HTTP and TCP clients enter port numbers into the add-on network settings and activate them in the config.

After TCP clients activation you can connect from any system with installed ebusd clients.

The following example will force a reading of all messages from loaded csv config files

ebusctl -s 192.168.178.17 f -l "*" -a|awk '{print $2}' | xargs -L1 -t ebusctl -s 192.168.178.17 r

and can be included via crontab for regular message updates.

Hello Lukas, This is not a real question. I have already solved it for myself and maybe it will help others. I had the problem that no mqtt parameters were transferred from HA. My solution was to transfer parameters in the config:

loglevel_all: notice
mqtttopic: ebusd
mqttint: /etc/ebusd/mqtt-hassio.cfg
mqttjson: true
mqtthost: 192.168.xx.xx
mqttport: 1883
mqttuser: user
mqttpass: password
network_device: ens:192.168.xx.xx:9999
latency: 10
accesslevel: “*”
configpath: https://cfg.ebusd.eu/

By the way, thanks for your work

In the Home-Assistant add-on 'shop' the repo has incorrect name. Let's rename it correctly!

It's best practice to have precompiled binaries for HA Add-ons. maybe there's another add-on from wich we can copy the pipeline

Settings have gotten more complex over time and are now confusing.

It may be preferable to offer just a few settings such as USB device dropdown and then refer to the ebusd documentation and offer a field for custom command line options.

I am running a WiFi ebus adapter connected to my Vaillant heat pump and ebusd addon on my HA. Everything works fine except the values I am interested in are being refreshed very slowly. Some values seem to take even hours to refresh (although this could be a bug in "Last updated" attribute?).

That said what is the best way to make sure I have the current up-to-date value displayed on my dashboard? I don't need all the values refreshed so often so decreasing polling interval does not seem to be a good option. I have tried creating an automation that is run every minute and is calling "MQTT: publish" service with empty payload and topic like "ebusd/b7v/Hc1FlowTemp/get" but this does not seem to have any effect on the values displayed on dashboard.

We Merged #19 before updating the docs. This remains an open TODO

Add-on may appear stuck in starting state.
Watchdog is advised to be turned off in this case.

It looks like the healthcheck is introduced for port 8888 hardcoded with a http curl call.
Altough if HTTP service is enabled it starts on 8889, and by default it has a TCP service n 8888.

Related:
Originally posted by @mousetwentytwo in #60 (comment)

Healthcheck code:

Not sure for the cause, may be unrelated to HTTP.

After some update Home Assistant addon no working correct with check watchdog. Still no show RUN status and can not stop addon , only has button for Uninstall. But addon works.... Is any chance to fix it ? I use addon 23.2.2

Hello,
Since mqtt is an esential component of ebusd, I would recommend to add the HA's /ssl folder as a same /ssl folder mountpoint in this addon.
(mqtt-addon also uses this folder to get the ca/server/key certificates.) It would be appreciated if the cert files can be identical.
Thank's in advance,

Hi,
i am using

Home Assistant
Core
2024.1.2
Supervisor
2023.12.0
Operating System
11.3
Frontend
20240104.0

but the add-on ist not installing. I already tried to restart everything. My supervisor.Log shows:

24-01-07 12:32:48 INFO (MainThread) [supervisor.resolution.checks.base] Run check for no_current_backup/system
24-01-07 12:32:48 INFO (MainThread) [supervisor.resolution.checks.base] Run check for pwned/addon
24-01-07 12:32:48 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/core
24-01-07 12:32:48 INFO (MainThread) [supervisor.resolution.checks.base] Run check for trust/supervisor
24-01-07 12:32:48 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_server
24-01-07 12:32:48 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/system
24-01-07 12:32:48 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system
24-01-07 12:32:48 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_server
24-01-07 12:32:48 INFO (MainThread) [supervisor.resolution.checks.base] Run check for docker_config/system
24-01-07 12:32:48 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/system
24-01-07 12:32:48 INFO (MainThread) [supervisor.resolution.check] System checks complete
24-01-07 12:32:48 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
24-01-07 12:32:48 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
24-01-07 12:32:48 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
24-01-07 12:32:48 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
24-01-07 12:34:54 INFO (MainThread) [supervisor.host.info] Updating local host information
24-01-07 12:34:55 INFO (MainThread) [supervisor.host.services] Updating service information
24-01-07 12:34:55 INFO (MainThread) [supervisor.host.network] Updating local network information
24-01-07 12:34:55 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
24-01-07 12:34:55 INFO (MainThread) [supervisor.host.manager] Host information reload completed
24-01-07 12:34:59 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
24-01-07 12:36:47 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'mqttuser'
24-01-07 12:36:47 INFO (MainThread) [supervisor.auth] Successful login for 'mqttuser'
24-01-07 13:04:59 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
24-01-07 13:32:48 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state running
24-01-07 13:32:48 INFO (MainThread) [supervisor.resolution.checks.base] Run check for no_current_backup/system
24-01-07 13:32:48 INFO (MainThread) [supervisor.resolution.checks.base] Run check for pwned/addon
24-01-07 13:32:49 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/core
24-01-07 13:32:49 INFO (MainThread) [supervisor.resolution.checks.base] Run check for trust/supervisor
24-01-07 13:32:49 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_server
24-01-07 13:32:49 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/system
24-01-07 13:32:49 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system
24-01-07 13:32:49 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_server
24-01-07 13:32:49 INFO (MainThread) [supervisor.resolution.checks.base] Run check for docker_config/system
24-01-07 13:32:49 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/system
24-01-07 13:32:49 INFO (MainThread) [supervisor.resolution.check] System checks complete
24-01-07 13:32:49 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
24-01-07 13:32:49 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
24-01-07 13:32:49 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
24-01-07 13:32:49 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
24-01-07 13:34:46 INFO (MainThread) [supervisor.backups.manager] Found 5 backup files
24-01-07 13:34:47 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
24-01-07 13:35:00 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
24-01-07 14:05:00 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
24-01-07 14:08:52 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'mqttuser'
24-01-07 14:08:52 INFO (MainThread) [supervisor.auth] Successful login for 'mqttuser'
24-01-07 14:32:49 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state running
24-01-07 14:32:49 INFO (MainThread) [supervisor.resolution.checks.base] Run check for no_current_backup/system
24-01-07 14:32:49 INFO (MainThread) [supervisor.resolution.checks.base] Run check for pwned/addon
24-01-07 14:32:50 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/core
24-01-07 14:32:50 INFO (MainThread) [supervisor.resolution.checks.base] Run check for trust/supervisor
24-01-07 14:32:50 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_server
24-01-07 14:32:50 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/system
24-01-07 14:32:50 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system
24-01-07 14:32:50 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_server
24-01-07 14:32:50 INFO (MainThread) [supervisor.resolution.checks.base] Run check for docker_config/system
24-01-07 14:32:50 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/system
24-01-07 14:32:50 INFO (MainThread) [supervisor.resolution.check] System checks complete
24-01-07 14:32:50 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
24-01-07 14:32:50 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
24-01-07 14:32:50 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
24-01-07 14:32:50 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
24-01-07 14:34:57 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/esphome/home-assistant-addon repository
24-01-07 14:34:57 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/LukasGrebe/ha-addons/ repository
24-01-07 14:34:57 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repository
24-01-07 14:34:57 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/GollumDom/addon-repository repository
24-01-07 14:34:57 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/addons repository
24-01-07 14:34:59 INFO (MainThread) [supervisor.store] Loading add-ons from store: 75 all - 0 new - 0 remove
24-01-07 14:34:59 INFO (MainThread) [supervisor.store] Loading add-ons from store: 75 all - 0 new - 0 remove
24-01-07 14:35:00 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
24-01-07 14:35:52 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/lukasgrebe/ha-addon-ebusd-aarch64 with version 23.2.3
24-01-07 14:35:57 INFO (SyncWorker_1) [supervisor.docker.manager] Stopping addon_2ad9b828_ebusd application
24-01-07 14:36:01 INFO (SyncWorker_1) [supervisor.docker.manager] Cleaning addon_2ad9b828_ebusd application
24-01-07 14:40:03 INFO (SyncWorker_4) [supervisor.docker.manager] Restarting homeassistant
24-01-07 14:40:21 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
24-01-07 14:40:26 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
24-01-07 14:40:27 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
24-01-07 14:40:32 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to NOT_RUNNING
24-01-07 14:40:32 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
24-01-07 14:40:32 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/esphome/home-assistant-addon repository
24-01-07 14:40:32 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/LukasGrebe/ha-addons/ repository
24-01-07 14:40:32 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repository
24-01-07 14:40:32 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/GollumDom/addon-repository repository
24-01-07 14:40:32 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/addons repository
24-01-07 14:40:34 INFO (MainThread) [supervisor.store] Loading add-ons from store: 75 all - 0 new - 0 remove
24-01-07 14:40:34 INFO (MainThread) [supervisor.store] Loading add-ons from store: 75 all - 0 new - 0 remove
24-01-07 14:40:38 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'homeassistant'
24-01-07 14:40:38 INFO (MainThread) [supervisor.auth] Home Assistant not running, checking cache
24-01-07 14:41:08 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to RUNNING
24-01-07 14:41:08 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
24-01-07 14:41:35 INFO (MainThread) [supervisor.host.info] Updating local host information
24-01-07 14:41:36 INFO (MainThread) [supervisor.host.services] Updating service information
24-01-07 14:41:36 INFO (MainThread) [supervisor.host.network] Updating local network information
24-01-07 14:41:36 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
24-01-07 14:41:36 INFO (MainThread) [supervisor.host.manager] Host information reload completed
24-01-07 14:46:27 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/lukasgrebe/ha-addon-ebusd-aarch64 with version 23.2.3
24-01-07 14:46:32 INFO (SyncWorker_3) [supervisor.docker.manager] Stopping addon_2ad9b828_ebusd application
24-01-07 14:46:36 INFO (SyncWorker_3) [supervisor.docker.manager] Cleaning addon_2ad9b828_ebusd application
24-01-07 14:49:03 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'mqttuser'
24-01-07 14:49:04 INFO (MainThread) [supervisor.auth] Successful login for 'mqttuser'

What is wrong? It seems that he is trying (14:46:27) but is stopping immediately (14:46:32)

Sebastian

I'am missing a quick setup guide on how to continue after the addon is installed.
So basically:

1. install addon
2. install hardware and connect
3. configure addon (what has to be configured what is optional?
4. Configure ebus configuration in ha?

I did the above with a Vaillant VRC-720 but absolutely no luck.

I have the ebus Adapter 3.

Installed the ebusd supervisor addon with
accesslevel: "*"
readonly: false

When I send to topic:
ebusd/bai/FlowTempDesired/set
67

I get back from the logs:
2022-12-14 20:11:11.894 [mqtt error] write message bai FlowTempDesired not found

Reading the same value works fine:
ebusd/bai/FlowTempDesired/get

returns
2022-12-16 13:56:15.689 [update notice] sent poll-read bai FlowTempDesired QQ=31: 60.00
2022-12-16 13:56:15.689 [mqtt notice] read bai FlowTempDesired:
2022-12-16 13:56:17.261 [update notice] sent poll-read bai PrEnergyCountHc3 QQ=31: 0

Looking at the MQTT ebusd bai device and the MQTT configuration information, all of the entities are sensors and none come up as inputs, e.g.

ebusd bai FlowTempDesired temp (sensor.ebusd_bai_flowtempdesired_temp)
MQTT discovery data:
Topic: homeassistant/sensor/ebusd_bai_FlowTempDesired_temp/config
Payload
unique_id: ebusd_bai_FlowTempDesired_temp
name: ebusd bai FlowTempDesired temp
device:
identifiers: ebusd_bai
manufacturer: ebusd.eu
name: ebusd bai
via_device: ebusd
sw_version: '22.4'
suggested_area: Heating
value_template: '{{value_json["temp"].value}}'
state_topic: ebusd/bai/FlowTempDesired
unit_of_measurement: °C
state_class: measurement
device_class: temperature
platform: mqtt

I wonder if the supervisor addon doesn't allow write functionality or if a further configuration setting needs to be made?
I haven't loaded a custom csv config file for my boiler. Do I need to edit mqtt-hassio.cfg and if so how?
Thanks

Hi there,

how do i run ebus-commands like "ebusctl find" or "grab result"?

Sebastian

Hello!
Trying to install ebusd-integration to HA - get error
Log:
21-10-08 17:12:40 INFO (SyncWorker_3) [supervisor.docker.addon] Starting build for 2ad9b828/armv7-addon-ebusd:0.81
21-10-08 17:13:28 ERROR (SyncWorker_3) [supervisor.docker.addon] Can't build 2ad9b828/armv7-addon-ebusd:0.81: The command '/bin/ash -o pipefail -c apk add --no-cache build-base argp-standalone git mosquitto-dev cmake' returned a non-zero code: 5
21-10-08 17:13:28 ERROR (SyncWorker_3) [supervisor.docker.addon] Build log:
Step 1/21 : ARG BUILD_FROM
Step 2/21 : FROM $BUILD_FROM as builder
---> a6b4abf955c9
Step 3/21 : ENV LANG C.UTF-8
---> Using cache
---> 4e367cb8ece4
Step 4/21 : RUN apk add --no-cache build-base argp-standalone git mosquitto-dev cmake
---> Running in 0a2e973a7db9
fetch https://dl-cdn.alpinelinux.org/alpine/v3.14/main/armv7/APKINDEX.tar.gz
1995604880:error:0D0D90AD:asn1 encoding routines:ASN1_TIME_adj:error getting time:crypto/asn1/a_time.c:330:
1995604880:error:0D0D90AD:asn1 encoding routines:ASN1_TIME_adj:error getting time:crypto/asn1/a_time.c:330:
1995604880:error:0D0D90AD:asn1 encoding routines:ASN1_TIME_adj:error getting time:crypto/asn1/a_time.c:330:
1995604880:error:0D0D90AD:asn1 encoding routines:ASN1_TIME_adj:error getting time:crypto/asn1/a_time.c:330:
1995604880:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1914:

WARNING: Ignoring https://dl-cdn.alpinelinux.org/alpine/v3.14/main: Permission denied

fetch https://dl-cdn.alpinelinux.org/alpine/v3.14/community/armv7/APKINDEX.tar.gz
1995604880:error:0D0D90AD:asn1 encoding routines:ASN1_TIME_adj:error getting time:crypto/asn1/a_time.c:330:
1995604880:error:0D0D90AD:asn1 encoding routines:ASN1_TIME_adj:error getting time:crypto/asn1/a_time.c:330:
1995604880:error:0D0D90AD:asn1 encoding routines:ASN1_TIME_adj:error getting time:crypto/asn1/a_time.c:330:
1995604880:error:0D0D90AD:asn1 encoding routines:ASN1_TIME_adj:error getting time:crypto/asn1/a_time.c:330:
1995604880:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1914:

WARNING: Ignoring https://dl-cdn.alpinelinux.org/alpine/v3.14/community: Permission denied

ERROR: unable to select packages:

argp-standalone (no such package):
required by: world[argp-standalone]
build-base (no such package):
required by: world[build-base]
cmake (no such package):
required by: world[cmake]
git (no such package):
required by: world[git]
mosquitto-dev (no such package):
required by: world[mosquitto-dev]
Removing intermediate container 0a2e973a7db9

Error at installation - The command '/bin/ash -o pipefail -c apk add --no-cache build-base argp-standalone git mosquitto-dev cmake' returned a non-zero code: 5

Forgot - Rpi 3B+, HA core-2021.9.7, HA supervisor-2021.09.6
Can you help?)))