-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wrong register for Grenztemperatur / Bivalenztemperatur / Bivalenztemperatur VV #35
Comments
I got another modbus register documentation which is different from the one used in this project. From this documentation I can confirm your observations.
I got a Weishaupt WBB12 with firmware version 5.2. As soon as we know whether the modbus register documentations are firmware specific, I can create a pull request with the updated modbus register values. |
Can you please post your documentations here? |
Unfortunately I can not post the original documentation files here, but I'll extract the values and will post them here asap. |
If there are other variables in your docu that we do not use up to now, please let us know, too. |
Here you can find copies of my documentation. Unfortunately, the quality of some of the PDFs is very poor, sorry. |
Thank you! We'll compare and include the updated registers. Also check the power input.. |
This is ho it is implemented today: ModbusItem( address=34101, name="Status 2. WEZ", mformat=FORMATS.STATUS, mtype=TYPES.SENSOR, device=DEVICES.W2, resultlist=W2_STATUS, translation_key="status_2_wez"), Can you canfirm this on your installations? Or please let me know what to change. Otherwise this topic will be re-opened for the PV input power topic.. |
Bivalenz and Grenztemperatur are fixed. On the Betriebsstunden and Schaltspiele there seems to be a problem on the Mobus side. I will close this. |
Biblock 20 V5.3
weishaupt_modbus V1.0
could you check with your heappump that this is not just a topic with a newer software version?
vs
these are the correct register for my heatpump:
The text was updated successfully, but these errors were encountered: