There is a popular FHEM Module for Stiebel Eltron / Tecalor heat pumps LWZ and THZ. I tried to translate it into a custom component for Home Assistant.
It uses the serial interface either on the front of the device (USB-B) or on the mainboard, the same socket that their technicians use for reading the data. It’s not using modbus and no ISG is required.
It’s still in early development. The reading of all basic data should be possible and depending on device and firmware also the setting of some values.
Feel free to try it out and provide your opinion. It’s not yet available on HACS but as soon as I’m satisfied with the development, it will be added.
Super interested to try this out. I have a Stiebel Eltron LWZ 303i and I have managed to get the FHEM integration working. I then exchange data between FHEM and Home Assistant using MQTT. I would like to get rid of FHEM altogether as I barely understand the system and I see it as another potential point of failure.
I added your configuration files to the customer component folder and restarted Home Assistant, but obviously doing something wrong as I getting this error message
Okay, it should be fixed now. I struggle a bit with unit testing on my remote device, therefore debuggging is tedious and error prone.
Please go ahead and try again.
I get all the readings and parameters for my LWZ504. There is still some cleanup needed to avoid some duplicates and meaningless values.
And I need to do some functionality checking on the settings, if all values are accepted correctly.
On Firmware 206 a whole block needs to be written at once instead of a single parameter. This is not implemented yet.
As I mentioned previously, I have a LWZ303 and I am running version 2.06.I suppose this error is due to the functionality that you have not implemented as of yet. Correct?
hmm, the sensor values should appear in any case, it’s just the writing of settings that will fail wiht your firmware. Can you share the content of the logfile just after setup failed?
And are you by any chance trying to run fhem and homeassistant on the same machine? If yes please stop fhem and try again, because the fhem module for the thz will block the communication channel and prevent any other process from talking to the heat pump.
Thank you so much for picking up the integration again!
Sadly I get the same error. But I have indeed FHEM running - FHEM and HA both connect to the heat pump over ser2net. Is ser2net also blocked by FHEM? I will try again in the next days (it‘s already pretty late here).
btw I run a THZ 5.5 eco with „sFirmware version: 07.02“ according to FHEM readings. FHEMs readings are fine though.
The log says:
Traceback (most recent call last):
File "/config/custom_components/thz/config_flow.py", line 161, in async_step_detect_blocks
await device.async_initialize(self.hass)
File "/config/custom_components/thz/thz_device.py", line 56, in async_initialize
self._connect_tcp()
~~~~~~~~~~~~~~~~~^^
File "/config/custom_components/thz/thz_device.py", line 88, in _connect_tcp
self.ser.connect((self.host, self.tcp_port))
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: 'NoneType' object cannot be interpreted as an integer ```
the log indicates, that the communication fails directly at initialization, meaning that there is no answer form the heatpump at all.
If you have a terminal on the machine running FHEM you can disable the service with: sudo systemctl stop fhem
and restart it with sudo systemctl start fhem
Please try the integration again while FHEM is stopped.
I think I found the issue. I will integrate it into the next update. I fixed a lot of other stuff and need to test it first, so it’s going to be next year before i can finalize it.
I pushed the fix to git allready but I can’t guarantee that everthing is working correctly. If you are brave enough feel free to try it out.
ser.net is fixed, there was an actual issue in there where the port went missing. Thanks for catching that.
I fixed issue I was aware of. Please try it out and give me feedback.
For productive use, I recommend to adjust the logging level by adding the following to the configuration.yaml:
logger:
default: info
logs:
custom_components.thz: warning
Otherwise it will fill the logfile, it’s quite talkative right now.
PS: Some sensor values are not yet correct, I’m working on fixing it.
I have a LWZ 304 Trend and would like to know if development on this module is still continued or if there are other solutions available getting and setting data using the serial interface. This would be really great to get rid of FHEM someday.
