-
Notifications
You must be signed in to change notification settings - Fork 45
FAQ
This section contains common questions and issues. The items are sorted on General, platform v2 and SolisCloud
There are 2 main causes for this problem
- non-hybrid inverters switch off in the night and switch on again in the morning. Platform v2 only resets in the morning when it receives new data. Until then the server returns the old value. The integration tries to filter out these old values. This works fine if it wasn't complicated by hybrid systems with a battery that happen to switch off at unexpected times in the night and the fact that the solution must survive a HA restart. The solution is relatively robust now, but with all varieties of inverters in the field there might still be cases where you see the integration resetting at the wrong time. In those cases file a bug with a complete debug log and a screenshot of "energy today" and "state".
- SolisCloud timezone configuration. Make sure that you have correctly configured the timezone in the settings and that you enabled Daylight Saving Time (DST)
Yes, if they're all registered under the same plantId/stationId then the integration will do it automatically for you. If you have more than one plant or more than one account then for now you'll need to add an extra config in the configuration.yaml for each additional plant and/or account. You can also run platform v2 and SolisCloud in parallel. Inverters can be registered at both services at the same time and the integration can use both of them as well. Just add 2 configs to your configuration.yaml; one for the platform v2 account and one for the SolisCloud account
I do assume you know where to find the HA logs. Typically you'll only see errors and warnings in the logs. To switch on debug level logging for the Solis integration add the following lines to your configuation.yaml:
logger:
default: warning
logs:
custom_components.solis: debug
Restart HA and collect the debug info from the log.
See general section
When starting up the integration looks up all configured inverters in the plant and detects which sensors to create for each inverter. The integration only looks at inverters that produced data in the past 48 hours. Others are considered stale and are ignored. You'll need to restart HA to refresh detection.
The platform v2 server is hardly ever down for maintenance, but if it is down then the integration will simply continue to retry until it gets data again and recover automatically.
SolisCloud is still under development and things can break at any time. For example there are workarounds in the code to correct wrong values, these might come and go at any time. Also SolisCloud is way more often down for maintenance and can be down for hours. The integration is working, but still in beta and grows along with SolisCloud. So if you use the SolisCloud option and file a bug I do expect you to help me out isolating the bug by providing complete bug reports with logging, screenshots and full description as well as running test versions for validation. If that's not your thing then perhaps platform v2 is a better primary solution for now. Note that you can run both in parallel: Just add 2 configs to your configuration.yaml.
Navigate to https://soliscloud.com/#/apimanage and follow the menu flow to obtain key and secret. Copy them to your HA config and you're good to go. Sometime people can find the link under "basic settings" others don't. If you do not see it, just use the link.
If you navigate to station details on the SolisCloud webpage you'll see the following URL: https://soliscloud.com/#/station/stationdetail_1?id=. The number is your stationID. Copy it to your config.
See general section