search

OStrama / weishaupt_modbus

This integration allows you to monitor and controll your weishaupt heatpump via modbus.
MIT License
21 stars 6 forks source link

modbus register wrong? #20

Open backuprestore opened 2 weeks ago

backuprestore commented 2 weeks ago

Hi please check

ModbusItem(34102,"Betriebsstunden 2. WEZ",FORMATS.TIME_H,TYPES.SENSOR,DEVICES.W2),
ModbusItem(34103,"Schaltspiele 2. WEZ",FORMATS.NUMBER,TYPES.SENSOR,DEVICES.W2),

to my research this should be

ModbusItem(34102,"Schaltspiele 2. WEZ E1",FORMATS.NUMBER,TYPES.SENSOR,DEVICES.W2),
ModbusItem(34103,"Schaltspiele 2. WEZ E2",FORMATS.NUMBER,TYPES.SENSOR,DEVICES.W2),

grafik vs. grafik

also there are some more registers, like 33 106 input Verdampfungstemperatur
33 107 input Verdichtersauggastemp.

Parameter Elektrische Leistung Soll in W (0 … 30.000 W) 40002 Holding R/W WBB_WP_ModbusTCP.xlsx

thank you for your work

OStrama commented 2 weeks ago

Thanks for the info! We‘ll change it in next release. Much thanks also for the register info!

thetschulian commented 2 weeks ago

About elektrische Leistung:

I have no value in my dashboard for this

image

OStrama commented 2 weeks ago

Ahh yes, that‘s my Shelly Powermeter which measures the real heatpump consumption.

thetschulian commented 2 weeks ago

AH I see, okay, so with the

Parameter Elektrische Leistung Soll in W (0 … 30.000 W) 40002 Holding R/W

EDIT: ups, its Elektrische Leistung Soll and net the current Elektrische Leistung (IST)

OStrama commented 2 weeks ago

Exactly. As far as I understand it right, address 40002 allows setpoint specification for usage with PV-optimizaton. Means: The value can be adapted to optimize usage of PV energy. (High value when sun is shining, low val if not,..)

Up to now, I did not find a real electrical power signal from the HP. I guess they only estimate it from nominal values of the certain components. I wanted to know it exactly, so I installed a Shelly. If I compare it with the statistic values, it looks like this:

{A83C2C34-03C9-4B5E-AFC2-17557AF332A2}

So I ask myself if it would make sense to add 0.5 to all statistical values to reduce the error of only taking the integer part..

OStrama commented 2 weeks ago

Have changed the register configuration and added the other values. The unknown ones as "?" without any translation. If we know more, they will be updated

MadOne commented 1 day ago

I think this is still wrong. Reopening it. Additional info in #35

OStrama commented 21 hours ago

At my WBB12 I only see useful values at Schaltspiele and active. Operating hours are always zero. What do we have to change?

backuprestore commented 20 hours ago

The Unit is Hour … so it‘s possible that your wbb12 did not reach this 1 Hour? You can Check in wem Portal or on the biblock (Fachmann -> Info -> 2 WEZ). Mine has Counted 17 Events With 0 Hours total

Von: OStrama @.> Gesendet: Monday, November 18, 2024 7:00:47 PM An: OStrama/weishaupt_modbus @.> Cc: backuprestore @.>; Author @.> Betreff: Re: [OStrama/weishaupt_modbus] modbus register wrong? (Issue #20)

At my WBB12 I only see useful values at Schaltspiele and active. Operating hours are always zero. What do we have to change?

— Reply to this email directly, view it on GitHubhttps://github.com/OStrama/weishaupt_modbus/issues/20#issuecomment-2483754976, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BKKYHC7X63JMZKI6KIUM3JL2BITM7AVCNFSM6AAAAABQ2WJSP6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBTG42TIOJXGY. You are receiving this because you authored the thread.Message ID: @.***>

backuprestore commented 20 hours ago

So for me it's fixed with v1.0...

Von: OStrama @.> Gesendet: Monday, November 18, 2024 7:00:47 PM An: OStrama/weishaupt_modbus @.> Cc: backuprestore @.>; Author @.> Betreff: Re: [OStrama/weishaupt_modbus] modbus register wrong? (Issue #20)

At my WBB12 I only see useful values at Schaltspiele and active. Operating hours are always zero. What do we have to change?

— Reply to this email directly, view it on GitHubhttps://github.com/OStrama/weishaupt_modbus/issues/20#issuecomment-2483754976, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BKKYHC7X63JMZKI6KIUM3JL2BITM7AVCNFSM6AAAAABQ2WJSP6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBTG42TIOJXGY. You are receiving this because you authored the thread.Message ID: @.***>

MadOne commented 20 hours ago

Bildschirmfoto vom 2024-11-18 20-08-48

WEM: Bildschirmfoto vom 2024-11-18 20-09-22

dhoeld commented 19 hours ago

@MadOne which firmware version is installed on your WBB?

backuprestore commented 19 hours ago

@MadOne: did you checked this with a different modbus tool like ModbusTool of OpenModScan? Maybe Weishaupt is doing wrong: this is how it look at my side... but i can't check, because i didn't reach 1h in real live so 0 is ok for my device grafik

MadOne commented 18 hours ago

Bildschirmfoto vom 2024-11-18 21-19-36

Bildschirmfoto vom 2024-11-18 21-37-15

At least the value weishaupt has in wemportal is not on modbus.

OStrama commented 18 hours ago

In Wem portal it‘s more than 10 hours..

backuprestore commented 18 hours ago

i thing they don't but data in the register ... because documentation was also wrong with the description of reg 34102 grafik

meanwhile i'm reverse engineering the RS485 RTU bus... https://github.com/backuprestore/weishaupt_modbus_rtu

problem: it's "single-master", so i can only listen... otherwise i get errors on the bus (and also some permanent and not erasable warning in WEM Portal - fun with warrenty). but i can get some nice infos like "rpm of the inverter" or "Druckgastemperatur" etc... so lot of hardware related information that is missing on modbus TCP side.

i'm not done yet because there are 2 different buses but i need to diassamble the front panel to get access on the "main-computer" for the second bus. will take some time.

best regards Maik