Hi,

Since yesterday I can experience very strange results using RPI + HT3 together with Junkers heater.

Temp of water is reported correctly only in case the tap water is beying heat. The other parameters like to insidetemperature (FW100) is OK and the Junksers mode is also OK.

The heater itself works normally.

In case the water is heat for central heating is not reported at all.

Can you please guide me where to look for the problem. Is it hardware (mean RPI and circuit boards) or Junkers itself.

Very strange.

I am attaching the picture. I did the translation to polish language of the grapg but th colous are not changed.

Thanks for suggestions. I am lost a bit.

Describe the enhancement

It would be nice if some pressure measures could be added to MQTT interface at least the water supply line. I have to refill it recurrently and you can use it to avoid errors. This value is also visible in EasyControl App I also use...

Expected behavior
Some new topics for the heater

Describe the bug
The old sysv-startup scripts should be replaced with 'systemd'-handling.
Any additional script-call inside that startup should be removed.

To Reproduce
After installation currently that 'sysv'-scripts are used.

Expected behavior
Starting the project (after booting) using systemd-handling.

Additional context
Any previously used scripts 'spi_clk_off.py / spi_clk_on.py' not used anymore.

Describe the bug
The configured port-number:8086 is already used by 'InfluxDB' at Homeassistant

To Reproduce
Steps to reproduce the behavior:
If the httpserver-daemon ~/HT3/sw/etc/html/httpd.py is running, the InfluxDB can't be connected.

Expected behavior
The httpserver-daemon should use an other unused port-number.

Screenshots

I've read that there should be inter_byte_timeout used instead. For me changing this have fixed the problem with starting the serial port. Please consider changing that.

BTW Many thanks for all your hard work, I have managed to make it work with Junkers ZWB 28-5C. For now I've just run the status viewer, but I plan to make a transceiver and control the boiler externally. I will try to port some of the logic to ESP8266/ESP32 to just have a small wireless interface with 1 microcontroller.

What is the main reason for using ATmega/ATtiny in the transceivers? Wouldn't it work just using the USB-serial bridge in place of those microcontrollers? Sorry if the explanation is already on mikrokontroller.net - I'm very bad at German, and Google Translate sometimes makes it even harder to understand :)

Hi @norberts1 ,

thechnically this is not directly connected to your software, however you seam to be the most knowledgeable guy in this field and maybe you can help me.
I am running the ems-esp module by BBQKees with the software from proddy. Using this I am able to decode the messages of my heating system (Junkers Cerastar +Boch CT100). However i havent figured out yet, how to change the mode or setpoint of the thermostat.

Do you know which message (hex codes) I would have to send to the thermostat to do this? Or could you maybe point me in the right direction to figure this out?

Best Regards

Describe the bug
There are some drop outs especially in the outside temperature readings.

Screenshots

Additional context
The readings from the solar system do not suffer from drop outs.

Describe the bug
A clear and concise description of what the bug is.
It seems that there is no support for LWT topics in MQTT binding

To Reproduce
Steps to reproduce the behavior:
see mqtt sent by hometop, seems LWT is completely missing

Expected behavior
LWT should be set to "Online" / "Offline"

Screenshots
n.a.

Additional context
n.a

Describe the bug
From:

sol_yield_last_hour
sol_yield_sum
sol_yield_last_day

Only sol_yield_last_hour gets populated, although the Junkers FW 120 displays the other values.

Additional context
The bus system consists of:
Junkers CERAPUR-ECO ZSB14-3
Junkers ISM1
Junkers FW120

Describe the bug
I setup an read-only filesystem and used HT3 to send MQTT messages. For this I had to put var/log and var/run to a tmpfs. During investigation why it is not running fine I found 2 logfiles still not created in the logs folder. cdata.log and cdb_rrdtool.log. solved this via symlinks but it should be moved to log folder also. (a rsyslog integration would be nice also ;-) )

To Reproduce
Steps to reproduce the behavior:

1. Go to folder HT3/sw
2. See logfiles

Expected behavior
All logfiles should be located in the log folder or provided in the central log via rsyslog https://gist.github.com/danielkraic/a1657f19bad9c158cbf9532e1ed1503b

Additional context
Avoids broken SD Cards, etc.

Hi @norberts1 ,

First of all, thanks for the big update and all the improvements!

I have a suggestion; at the moment it looks like everything stops working once the MQTT broker goes offline.
In my case, the broker is running on another server. In noticed that, when the broker goes offline, the application stops working, generates an error and doesn't reconnect to the broker.

I also noticed, and think, that there is a timing issue when connecting to the remote broker.
When I restarted the raspberry pi, the software wasn't able to connect to the broker.
Maybe because the network is not yet fully initialized? I've added a 10 second sleep (probably way to high) to the mqtt_init function in the mqtt_client_if.py file and this solved the issue.

Are there any plans to implement a reconnect to the broker in case of disconnection?
I think it would also be good if the software submits all topics again to the broker after successfully reconnecting.

Greetings,
Frederic

Local_date_time     | UTC        | T_soll | T_ist | T_speicher | C_betriebs_zeit  | C_brenner_ww | V_WW_einmalladung | V_WW_desinfekt | V_WW_erzeugung | V_WW_nachladung | V_WW_temp_OK | V_lade_pumpe | V_zirkula_pumpe | V_spare_1 | V_spare_2 | hexdump
2022.09.20 13:20:27 | 1663672827 | 48     | 48.5  | 48.5       | 783.416666666667 | 410          | 0                 | 0              | 0              | 0               | 1            | 0            | 0               | 0         | 0         | 27_0 :WW :90 00 1b 00 30 00 b0 00 23 00 10 00 90 00 2b 00 30 00 b0 00 33 00 3b 00 10 00 90 00
2022.09.20 13:20:30 | 1663672830 | 15     | 48.5  | 48.5       | 783.416666666667 | 410          | 0                 | 0              | 0              | 0               | 1            | 0            | 0               | 0         | 0         | 52_0 :WW :88 00 34 00 0f 01 e5 01 e5 a1 00 00 03 00 00 b7 9d 00 01 9a 00 3f 00

T_soll is populated with "Soll-Temperatur Warmwasser (Zeitprogramm gesteuert)" and with "Sollwert Warmwasser-Temperatur".
When rendering T_soll in a diagram it looks really ugly.
I don't know where the 48 is coming from either (I can only imagine that this is the value set at the heater, but that should be 51_2?).

TIA,
Heiko

Describe the bug
There are serial portname changes for OS:buster and RPi3 / RPI4.
That device-name is changed from: /dev/ttyAMAx to /dev/serialx.
The default project-configuration is currently using: /dev/ttyAMA0.
Details see:
https://raspberrypi.stackexchange.com/questions/45570/how-do-i-make-serial-work-on-the-raspberry-pi3-pizerow-pi4-or-later-models/45571#45571

To Reproduce
After installation of the default project-configuration no data are received from the heaterbus.

Expected behavior
Default project-configuration should use that newly defined device-name: /dev/serial0.

Screenshots
none

Describe the bug

After a network issue with my Router there was some reboots of the router and MQTT broker as I tried to find the issue. From then I got strange topics, it seems that the topic name is appended with every publish. I still restarted the HT3 rasperry and all other components without any change in behavior. It happens not for every topic as some are published as before.

Perhaps there are some ideas what could cause this...

To Reproduce
Do not know as it appears after network issues...

Expected behavior
Topics should not be appended with every publish

Screenshots

Additional context
Attached the MQTT log in DEBUG mode and the configuration.
mqtt_client.log
mqtt_client_cfg.xml.txt

Describe the enhancement
System-alerts should be available for external instances.

Expected behavior
Heatersystem-alerts should be send out to available interfaces or should call (callback) handlers doing this.
At least the current error-code should be send out.

Additional context
A mapping between error-code and describing text would be nice.

Hi,

I would like to integrate the Junkers just for reading the values from the heather. I do not want to modify anything remotely.

Do I need to build the solution with ht-transceiver or just combination of RPI 3 with HT3-Miniadapter is enough?

DO I have a correct understanding that ht-transceiver is needed for controlling the heater but HT3-Miniadapter is only for reading??

Thanks for answer.

Describe the bug
The current mqtt topic- and payload-output doesn't match to the HomeAssistant interface.

To Reproduce
current mqtt-output is like: topic: 'hometop/ht/ch_pump_heating' and payload: 'current value'
visible with call:
mosquitto_sub -d -t hometop/ht/# -h 'broker-IP adr.'

Expected behavior
mqtt output should match to required HomeAssistant default topic-name 'homeassistant' and payload using json-formated streams.

I'm having problems running hometop_HT3 on my new raspberry pi 5.
First issue:
when checking the status of the services I noticed following error with ht_collgate.service:

● ht_collgate.service - LSB: initscript for daemon: 'ht_collgate' connecting
     Loaded: loaded (/etc/init.d/ht_collgate; generated)
     Active: active (running) since Sun 2024-01-07 19:57:55 CET; 11min ago
       Docs: man:systemd-sysv-generator(8)
    Process: 925 ExecStart=/etc/init.d/ht_collgate start (code=exited, status=0/SUCCESS)
      Tasks: 7 (limit: 9262)
        CPU: 196ms
     CGroup: /system.slice/ht_collgate.service
             └─939 /usr/bin/python3 /home/tommi/HT3/sw/ht_collgate.py

Jan 07 19:57:55 rpi5 systemd[1]: Starting ht_collgate.service - LSB: initscript for daemon: 'ht_collgate' conne>
Jan 07 19:57:55 rpi5 ht_collgate[929]: Traceback (most recent call last):
Jan 07 19:57:55 rpi5 ht_collgate[929]:   File "/home/tommi/HT3/sw//etc/sysconfig/spi_clk_off.py", line 38, in <>
Jan 07 19:57:55 rpi5 ht_collgate[929]:     setup_gpio()
Jan 07 19:57:55 rpi5 ht_collgate[929]:   File "/home/tommi/HT3/sw//etc/sysconfig/spi_clk_off.py", line 36, in s>
Jan 07 19:57:55 rpi5 ht_collgate[929]:     GPIO.setup (11, GPIO.IN)
Jan 07 19:57:55 rpi5 ht_collgate[929]: RuntimeError: Cannot determine SOC peripheral base address
Jan 07 19:57:55 rpi5 systemd[1]: Started ht_collgate.service - LSB: initscript for daemon: 'ht_collgate' connec>

It seems that something about the GPIO's changed with the pi5 and the python3-rpi.gpio package doesn't support it(yet?). After some googling I was able to resolve this problem by uninstalling python3-rpi.gpio and installing rpi-lgpio which is a drop in replacement.

sudo apt remove python3-rpi.gpio
sudo pip3 install --break-system-packages rpi-lgpio

The error is now gone, but I'm still not receiving any data in Home Assistant.
I checked everything else i can think of, but I'm unable to pinpoint the problem.
So far i checked:

all services are running without errors (ht_collgate, ht_proxy, ht_2hass, ...

mqtt says state : online:

mosquitto_sub -h 127.0.0.1 -v -t "homeassistant/#"
homeassistant/sensor/heatersystem/status/config {"state_topic": "homeassistant/sensor/heatersystem/state", "value_template": "{{ value_json.status }}", "name": "status", "uniq_id": "status", "unit_of_measurement": ""}
homeassistant/sensor/heatersystem/state {"status": "Online"}

serial port should still be /dev/ttyAMA0 on the pi5
cat /dev/ttyAMA0
returns data, so i'm guessing this part also works. I can provide a datadump if you want

Any ideas what to check next?

Hi,

I have build a device, connect it to heater and RPI but I have an issue with /dev/serial0 access.

I have done all the changes in Stretch configuration files which are mentioned in the threat for RPI 3b to make the Serial0 available only for serial connection.

But still I am getting below error.

29.05.2018 23:15:12 INFO: Starting 'Ccollgate.run()
29.05.2018 23:15:12 CRITICAL: cht_if_worker();Error;couldn't open requested device:/dev/serial0
29.05.2018 23:15:12 CRITICAL: ccollgate().run();Error;could not start 'ht-interface' with file:'./etc/config/HT3_db_cfg.xml'
29.05.2018 23:15:12 CRITICAL: ccollgate().run();Error; terminated

@norberts1 , can you help and suggest what else should be changed in configuration?

Hello,

I'm trying to use home assistant to change the desired room temperature and also turn heating on/off (heizen/sparen?)
However i cannot seem to figure out the topic and payload i have to use.
In the manual i can find following command:
mosquitto_pub -d -h <host IP-Adr.> -t set/hometop/ht/hc1_Tdesired -m "21.5,heizen"
But running it on the command line doesn't seem to work (I changed <host IP-Adr.> to my mqtt brokers ip).
Running: mosquitto_sub -v -h rpi3.local -p 1883 -t 'rpi3/hometop/ht/hc1_Tdesired' gives correct results so the mqtt broker is working.

I noticed that rpi3 is added to the topic when using homeassistant. I tried adding rpi3 to the topic on various places, but nothing seems to work.

So maybe there is a bug in the ht_2hassio.py-daemon? Or maybe I am doing something wrong. Also maybe the answer be found in the docs, but my German is not very good, so i might have missed something.

Hi,
I have a Bosch gas heater with weather compensation FW100 (i think it uses Heatronic 3). Can this be used with that ? If so what kind of hardware would i need ? I could probably use an ESP8266 to connect to the heather if it's possible.

/donnib

Hallo @norberts1 Danke fúr die fantastike EMS2 infos.
I have an SM200 solar module and have been helping @proddy to get the data from the EMS2 telegrams into MQTT.
My SM200 sent this x026A telegram in test mode.
B0 00 FF 00 02 6A 03 03 03 03 01 03 03 03 03 03 01 03
I agree with you that byte 10 represents Solar Pump but also believe that byte 4 is the cylinder selector valve VS2. Also the values 01/03/04 are test/off/on.
This is further documented here:
https://emsesp.github.io/docs/#/SM100
I hope this helps.
mfG

I am using a pitiny adapter with an ttl USB converter.
I am using an udev-rule so that the USB device always shows up as /dev/heatronic3 symlink.

If i disconnect the USB port and reconnect it, ht_proxy just freezes and i must restart ht_proxy and ht_collgate.

Would be nice, if ht_proxy could try to reconnect every second or so...

Describe the bug
The decoding for different Solar System-Konfigurations (SolarOptions) should be implemented.

To Reproduce
Systems with EMS2 Solarmodul MS200 can have many different configurations and telegrams.
See logfiles on URL: https://www.mikrocontroller.net/topic/324673?page=single#7454290

Expected behavior
Decoding for different solar options is done and send to external interfaces.

Documentation

Describe the bug
The daemon Ccollgate.py terminates with error-message:
ccollgate().run();Error;could not start 'mqtt-interface' with file:'./etc/config/HT3_db_cfg.xml'
after a fresh installation on debian12.

The reason is not any error in the configuration-file but an error during paho-mqtt installation using pip3.

To Reproduce
Details see:
https://www.mikrocontroller.net/topic/324673?page=single#7535485

Expected behavior
Error-message in Ccollgate.py line:987 should handle faulty mqtt installation.
Installation-script must be modified for secure paho-mqtt installation.

Screenshots
None

Additional context
Error-message occurred during installation using script: ht_project_setup.sh
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv

Currently is required for debian12 to install that paho-mytt part by hand with:
sudo apt install python3-paho-mqtt

Hi,

recently some exceptions occur in ht_rpxy

Apr 04 19:58:07 fhempi ht_proxy.py[2112]: Exception happened during processing of request from ('127.0.0.1', 43732) Apr 04 19:58:07 fhempi ht_proxy.py[2112]: ---------------------------------------- Apr 04 19:58:07 fhempi ht_proxy.py[2112]: ---------------------------------------- Apr 04 19:58:07 fhempi ht_proxy.py[2112]: Exception happened during processing of request from ('127.0.0.1', 43734) Apr 04 19:58:07 fhempi ht_proxy.py[2112]: ---------------------------------------- Apr 04 19:58:07 fhempi ht_proxy.py[2112]: ---------------------------------------- Apr 04 19:58:07 fhempi ht_proxy.py[2112]: Exception happened during processing of request from ('127.0.0.1', 54694) Apr 04 19:58:07 fhempi ht_proxy.py[2112]: ---------------------------------------- Apr 04 19:58:07 fhempi ht_proxy.py[2112]: ---------------------------------------- Apr 04 19:58:07 fhempi ht_proxy.py[2112]: Exception happened during processing of request from ('127.0.0.1', 54696) Apr 04 19:58:07 fhempi ht_proxy.py[2112]: ---------------------------------------- Apr 04 19:58:07 fhempi ht_proxy.py[2112]: ---------------------------------------- Apr 04 19:58:07 fhempi ht_proxy.py[2112]: Exception happened during processing of request from ('127.0.0.1', 55762) Apr 04 19:58:07 fhempi ht_proxy.py[2112]: ---------------------------------------- Apr 04 19:58:07 fhempi ht_proxy.py[2112]: ---------------------------------------- Apr 04 19:58:07 fhempi ht_proxy.py[2112]: Exception happened during processing of request from ('127.0.0.1', 37414) Apr 04 19:58:07 fhempi ht_proxy.py[2112]: ---------------------------------------- Apr 04 19:58:07 fhempi ht_proxy.py[2112]: ---------------------------------------- Apr 04 19:58:07 fhempi ht_proxy.py[2112]: Exception happened during processing of request from ('127.0.0.1', 37416) Apr 04 19:58:07 fhempi ht_proxy.py[2112]: ----------------------------------------

which leads to the following error:
Apr 04 20:18:07 fhempi ht_proxy.py[2112]: ---------------------------------------- File "lib/ht_proxy_if.py", line 409, in add_client Apr 04 20:18:07 fhempi ht_proxy.py[2112]: txThread.start() Apr 04 20:18:07 fhempi ht_proxy.py[2112]: File "/usr/lib/python3.4/threading.py", line 850, in start Apr 04 20:18:07 fhempi ht_proxy.py[2112]: _start_new_thread(self._bootstrap, ()) Apr 04 20:18:07 fhempi ht_proxy.py[2112]: RuntimeError: can't start new thread Apr 04 20:18:07 fhempi ht_proxy.py[2112]: Traceback (most recent call last): Apr 04 20:18:07 fhempi ht_proxy.py[2112]: File "/usr/lib/python3.4/socketserver.py", line 613, in process_request_thread Apr 04 20:18:07 fhempi ht_proxy.py[2112]: self.finish_request(request, client_address) Apr 04 20:18:07 fhempi ht_proxy.py[2112]: File "/usr/lib/python3.4/socketserver.py", line 344, in finish_request Apr 04 20:18:07 fhempi ht_proxy.py[2112]: self.RequestHandlerClass(request, client_address, self) Apr 04 20:18:07 fhempi ht_proxy.py[2112]: File "/usr/lib/python3.4/socketserver.py", line 669, in __init__ Apr 04 20:18:07 fhempi ht_proxy.py[2112]: self.handle() Apr 04 20:18:07 fhempi ht_proxy.py[2112]: File "lib/ht_proxy_if.py", line 445, in handle Apr 04 20:18:07 fhempi ht_proxy.py[2112]: _ClientHandler.add_client(self._myownID, self.request) Apr 04 20:18:07 fhempi ht_proxy.py[2112]: File "lib/ht_proxy_if.py", line 409, in add_client Apr 04 20:18:07 fhempi ht_proxy.py[2112]: txThread.start() Apr 04 20:18:07 fhempi ht_proxy.py[2112]: File "/usr/lib/python3.4/threading.py", line 850, in start Apr 04 20:18:07 fhempi ht_proxy.py[2112]: _start_new_thread(self._bootstrap, ())

maybe we should close the thread on an exception or use a threadpool? Is there any possibility to get more infomation about the exception?

Describe the bug
There are new, not yet decoded deviceID's seen on the heatersystem-bus.
That ID:0x41 was seen at first. Perhaps there are other not yet decoded ID's.

To Reproduce
With powermoduls Bosch/Junkers: IPM1 or IPM2 new deviceID's are used on the bus.
This depends on the internal powermodul-configuration, selectable with 1 or 2 switches and there use in the heater-system.

Expected behavior
That newly found deviceID's should be decoded.

Screenshots
Configuration-switches in the powermodul (IPM2):

Describe the bug
On raspberry the creation of SQLite DB needs some time and in my architecture all data is send to MQTT/Influx DB to store and visualize everything. To reduce Ressource consumption it would be nice if it will be ask for in the setup script. I disabled and deleted rrd files by hand actually.

To Reproduce
run ht_project_setup.sh

Expected behavior
As implemented for MQTT it would be also nice of there is a question for SQLite,...

Screenshots

Additional context
Installation/Update