You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Version V3.90.1 of the luxtronik controller, there exists a so-called SmartHomeInterface. It can be enabled in the settings of the controller (or via parameter 1161, I think). It listens via Modbus-TCP on Port 502 and 'controls' the registers 10.000-19.999 (only a few of them are in use currently). There are some registers for reading (input registers) and others for reading/writing (holding registers). Via the holding registers, it is, e.g., possible to control the "desired return flow temperature". The advantage is that the written values are not saved in the persistent memory of the controller, i.e., these writing operations should not add wear to the NAND memory, see #158.
Should we add access to this interface to this library?
The text was updated successfully, but these errors were encountered:
Is there any kind of official documentation about this interface? Is it built for integrating with other / third party solutions and/or is it some internal development for AIT itself?
Technically there is a ModBus TCP interface for a long time already. Officially it needs to be activated via a license (expensive) or "hacked" by other means. I'm using it for quite some time. However it is lacking some of the more advanced "features" that this library provides.
The new interface uses the same port as the "old" ModBus interface, but it uses other registers.
Edit: Can you do something via the ModBus interface which is not possible via port 8889 (this library)? Do the parameter writes via the old ModBus interface (GLT) go into the permanent memory?
Since Version V3.90.1 of the luxtronik controller, there exists a so-called SmartHomeInterface. It can be enabled in the settings of the controller (or via parameter 1161, I think). It listens via Modbus-TCP on Port 502 and 'controls' the registers 10.000-19.999 (only a few of them are in use currently). There are some registers for reading (input registers) and others for reading/writing (holding registers). Via the holding registers, it is, e.g., possible to control the "desired return flow temperature". The advantage is that the written values are not saved in the persistent memory of the controller, i.e., these writing operations should not add wear to the NAND memory, see #158.
Should we add access to this interface to this library?
The text was updated successfully, but these errors were encountered: