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
I'd like to report an issue with this entity. It's likely specific to the Czech Republic due to some smart individuals' efforts. However, I believe it should be named "SolaX Phase Power Unbalance X3", as it is in the cloud. When enabled, the inverter operates in asymmetric mode and does not balance the load across all phases. When incorrectly set in Czechia, this can significantly increase your energy bill.
Homeassistant preview
SolaxCloud preview
Integration Version
2024.05.7
Homeassistant core version
2024.7.2
Inverter brand
SolaX Power
Plugin used
plugin_solax.py
Serial prefix
H34A15
Inverter firmware versions
DSP v1.42 ARM v1.41
Connection Method
Waveshare adapter
Dongle firmware
Unknown
Detailed Error Log
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Hi. Sorry for offtopic comment. Xeudoron, can you please see my question regarding asymmetric mode at #954
For the topic - you are right, the entity name suggests the opposite setting.
Describe the bug
Hi,
I'd like to report an issue with this entity. It's likely specific to the Czech Republic due to some smart individuals' efforts. However, I believe it should be named "SolaX Phase Power Unbalance X3", as it is in the cloud. When enabled, the inverter operates in asymmetric mode and does not balance the load across all phases. When incorrectly set in Czechia, this can significantly increase your energy bill.
Homeassistant preview
SolaxCloud preview
Integration Version
2024.05.7
Homeassistant core version
2024.7.2
Inverter brand
SolaX Power
Plugin used
plugin_solax.py
Serial prefix
H34A15
Inverter firmware versions
DSP v1.42 ARM v1.41
Connection Method
Waveshare adapter
Dongle firmware
Unknown
Detailed Error Log
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: