We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi @PatrikTrestik , the problem is that when I want to set the EV Charger to Enabled, it switches to Disabled.
2024.05.7
2024.6.2
Solax Power
plugin_solax.py
H34A10
ARM1.40 DSP1.41
Packet Wifi + LAN 3.0
1.002.09
No response
The text was updated successfully, but these errors were encountered:
Working on it.
Sorry, something went wrong.
No branches or pull requests
Describe the bug
Hi @PatrikTrestik ,
![1](https://private-user-images.githubusercontent.com/129114957/339329720-3becdadf-0f8b-431f-adb3-ed8456ec7ad8.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA2ODYzMTUsIm5iZiI6MTcyMDY4NjAxNSwicGF0aCI6Ii8xMjkxMTQ5NTcvMzM5MzI5NzIwLTNiZWNkYWRmLTBmOGItNDMxZi1hZGIzLWVkODQ1NmVjN2FkOC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNzExJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDcxMVQwODIwMTVaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT04NjgxZWE1OWFiNzUwOWU5N2ExZjQ5NGUyNGI0ZjI5NDYxYWYwNDRhNDhhNzAxN2M5ZjQzMDhlZDdlNTI5N2QyJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.oDTClMwDsWr_2vVclr3xXl8EU3eWoclPNP0KN4Pqm54)
the problem is that when I want to set the EV Charger to Enabled, it switches to Disabled.
Integration Version
2024.05.7
Homeassistant core version
2024.6.2
Inverter brand
Solax Power
Plugin used
plugin_solax.py
Serial prefix
H34A10
Inverter firmware versions
ARM1.40 DSP1.41
Connection Method
Packet Wifi + LAN 3.0
Dongle firmware
1.002.09
Detailed Error Log
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: