-
Notifications
You must be signed in to change notification settings - Fork 200
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
DEYE SUN-M80G4-EU-Q0 not able to connect! Which Profile? #650
Comments
Try this more advanced version: |
I have same problem. It suddenly lost contact. It worked for months without any error. The integration is loaded, but all entities are unavailable in Solarman. What happened? How can I fix it? Thanks in advance for your advice. |
Hi guys. Had the same issue. |
Hello, thanks for your answer. |
Sure, I can try. Since mine is far back in the garden, I'll have to go there. If you are logged in you will see a menu on the left. I think that's it, you can ignore the options with Hide AP SSID and Co for now and leave them unchecked. The inverter will then restart once. I hope I was able to help halfway :'D Otherwise it's best to wait until your son is available |
You are very kind :) Thanks. I will try it. |
To be honest, no idea. I don't have the Solarman App Only HomeAssistant doesn't want to. |
Hello all, I always geht the error message inside of the integration menu: I am not sure which is the correct debug log and where to find it. I added the System log (Settings->System->Logs). Included are only parts that reference Solarman. Furthermore, i am a little confused: I have not entered any credentials like in the Solarman App or inverter login. Did i miss something? Attached you find my system log: |
Hello all,
i cannot connect to Homeassistant Solarman with the deye_string.yaml Profile.
In the PC Webinterface (No Homeassistant) I can see the Data logger with all information.
Where the used configuration is stored?
Do i need to modify the configuration?
I added my IP address and serial number in the UI.
Thanks in advance for help!
The text was updated successfully, but these errors were encountered: