Wattsonic - improvements to the config UI and data #23010
Description
Describe the bug
Hi, I checked the new Wattsonic config and wanted to check active battery control you added based on my comment, thanks for that! I found out some issues with the implementation.
- Config UI suggests MODBUS ID 247 but I know that only 255 works. You can check in my manual config I used before.
- SOC is not being read out correctly. It should be visible on the register 33000.
- You can read also PV1 and PV2 separately. Check my config as well.
Manual config I used before is below in config delays.
Steps to reproduce
1.Start with fresh EVCC installation
2.Add Wattsonic device (either battery, PV or grid meter)
3.You see wrong MODBUS ID
4.When you add battery you can see that SOC cannot be read out.
...
Configuration details
Previous working manual config:
meters:
- name: meter-pv1
type: custom
power:
source: modbus
delay: 100ms
uri: 192.168.1.71:502
id: 255
rtu: false
timeout: 10s
register:
address: 11062
type: holding
decode: int32
currents:
- source: modbus
delay: 100ms
uri: 192.168.1.71:502
id: 255
rtu: false
timeout: 10s
register:
address: 11039
type: holding
decode: uint16
scale: 0.1
- source: const
value: 0
- source: const
value: 0
- name: meter-pv2
type: custom
power:
source: modbus
delay: 100ms
uri: 192.168.1.71:502
id: 255
rtu: false
timeout: 10s
register:
address: 11064
type: holding
decode: int32
currents:
- source: modbus
delay: 100ms
uri: 192.168.1.71:502
id: 255
rtu: false
timeout: 10s
register:
address: 11041
type: holding
decode: uint16
scale: 0.1
- source: const
value: 0
- source: const
value: 0
- name: meter-grid
type: custom
power:
source: modbus
delay: 100ms
uri: 192.168.1.71:502
id: 255
rtu: false
timeout: 10s
register:
address: 11000
type: holding
decode: int32
scale: -1
powers:
- source: modbus
delay: 100ms
uri: 192.168.1.71:502
id: 255
rtu: false
timeout: 10s
register:
address: 10994
type: holding
decode: int32
scale: -1
- source: modbus
delay: 100ms
uri: 192.168.1.71:502
id: 255
rtu: false
timeout: 10s
register:
address: 10996
type: holding
decode: int32
scale: -1
- source: modbus
delay: 100ms
uri: 192.168.1.71:502
id: 255
rtu: false
timeout: 10s
register:
address: 10998
type: holding
decode: int32
scale: -1
- name: meter-battery
type: custom
power:
source: modbus
delay: 100ms
uri: 192.168.1.71:502
id: 255
rtu: false
timeout: 10s
register:
address: 30258
type: holding
decode: int32
soc:
source: modbus
delay: 100ms
uri: 192.168.1.71:502
id: 255
rtu: false
timeout: 10s
register:
address: 33000
type: holding
decode: uint16
scale: 0.01
currents:
- source: modbus
delay: 100ms
uri: 192.168.1.71:502
id: 255
rtu: false
timeout: 10s
register:
address: 30255
type: holding
decode: int16
scale: 0.1
- source: const
value: 0
- source: const
value: 0
capacity: 11.7Log details
I am sorry, I do not know how to take it when I am running on Home Assistant. Please pardon me.
What type of operating system or environment does evcc run on?
HomeAssistant Add-on
External automation
- I have made sure that no external automation like HomeAssistant or Node-RED is active or accessing any of the mentioned devices when this issue occurs.
Nightly build
- I have verified that the issue is reproducible with the latest nightly build
Version
0.207.3