-
Notifications
You must be signed in to change notification settings - Fork 45
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
Still no PS are seen #18
Comments
Hi @hdymling, could you try to pull the latest release again? I re-released as the same version by mistake. |
I have now pulled the latest relase and recompiled, still same issue! |
Hmmm. Interesting. What about the command Just wondering there might be some different result because you have 4 inverters. |
I could share the credentials if you want to debug this. At least i guess this is the most easy way to see what the issue are. /Helge |
Hmmm. I'd rather not do that. Could you tell me your solar install name? (That is the name you called it when installing. Or the name that appears when you use the iSolarCloud app.) I can query using that. |
I have hit such problem as well. What I see is that if I use the account, that is used in my iPhone App - it works well and lists devices. Now I was trying to use the account one can create for read only purposes - and then it is unable to list inverters. |
I have now tried the HomeAssistant integration and getting the following in the log file. |
I have now got more access rights on Isolarcloud and our Plant, but still I cannot see any devices found. Do you know what access rights you have when i worked? |
@hdymling , |
I have the same issue, I only have 1 inverter in a Residential PV plant (my home installation) and |
Hi,
First I would like to thank you for all the work you are doing regarding this!
I have now updated to version 3.0. This is done on my windows 10 workstations as I plan to run and export daily graphs.
The bellow are what is happening when I run the list of PS. We have four inverters.
The text was updated successfully, but these errors were encountered: