Solis API timeout

[abrasive-blueberry]

Hi Mark,

You are possibly experiencing this yourself,but since around 08:45 this morning, SAM has been unable to connect to the Solis API which is giving timeout errors.

It may just need Solis to fix it. However a thread relating to HA suggest it is possibly due to a change that Solis has made to the API endpoint.

hultenvp/solis-sensor#520

They are saying it may have changed from https://www.soliscloud.com:13333 to https://v3.soliscloud.com:13333

The latter is reported to be working.

It’s still unclear if this is a deliberate change or not so just a heads up to you at this stage.

[Scoobyscotty]

Abrasive,

You are spot on. I have just tested the revised address in the mysolar app and the connection was successful

[Scoobyscotty]

SM Now back up and running with the original API address

[abrasive-blueberry]

Yes it looks like it started working again at around 3am.

It seems both URLs are valid and one must have just fallen over for a while.

[Webreaper]

The old address is working fine again now. It was a DNS cockup by Soliscloud when moving their service, by the looks of things.

[dqj999]

Yes, I saw this too. It stopped my battery starting to charge at 11:30 last night so I'm a bit low on charge today :-(

[Webreaper]

I missed the whole pre-peak charge yesterday, so while I was cooking dinner at 6pm I was using peak electricity, instead of cheap electricity from charging earlier in the afternoon. I reckon that might have cost me somewhere between 50p and £1.

Wondering if I can sue Solis for incompetence to claim the money back. 😆

[Webreaper]

BTW, I've thought about adding an optional field for the SolisCloud URL, so that in a scenario like yesterday's people can point at v3.soliscloud.com instead. But since most people only found out that URL worked a few hours before the other one started functioning again, I'm not sure it's worth the bother...

[abrasive-blueberry]

I managed to set a charge manually using the Solis app to cover the overnight cheap rate. By the time I woke up it was working again.

BTW, I've thought about adding an optional field for the SolisCloud URL, so that in a scenario like yesterday's people can point at v3.soliscloud.com instead. But since most people only found out that URL worked a few hours before the other one started functioning again, I'm not sure it's worth the bother...

Sounds like one of those things that would be “nice to have” but isn’t essential. I’m sure it’s not very often that the API goes down.

[Webreaper]

I managed to set a charge manually using the Solis app to cover the overnight cheap rate. By the time I woke up it was working again.

Interestingly, I tried to set a scheduled charge to give me a boost before the peak period, but it didn't do anything...

[Nafeun1984]

Hi Mark,

Since the API went down the app is not communicating with Solis.
Latest App, Solis Cloud working through browser and app.

Error in log..

[14:06:00.510--ERR] Unexpected exception during inverter state refresh
System.NullReferenceException: Object reference not set to an instance of an object.
at SolisManager.Services.InverterManager.UpdateInverterState() in /home/runner/work/SolisAgileManager/SolisAgileManager/SolisManager/Services/InverterManager.cs:line 947
[14:07:00.514--ERR] Unexpected exception during inverter state refresh
System.NullReferenceException: Object reference not set to an instance of an object.
at SolisManager.Services.InverterManager.UpdateInverterState() in /home/runner/work/SolisAgileManager/SolisAgileManager/SolisManager/Services/InverterManager.cs:line 947
[14:08:00.513--ERR] Unexpected exception during inverter state refresh
System.NullReferenceException: Object reference not set to an instance of an object.
at SolisManager.Services.InverterManager.UpdateInverterState() in /home/runner/work/SolisAgileManager/SolisAgileManager/SolisManager/Services/InverterManager.cs:line 947
[14:09:00.511--ERR] Unexpected exception during inverter state refresh
System.NullReferenceException: Object reference not set to an instance of an object.
at SolisManager.Services.InverterManager.UpdateInverterState() in /home/runner/work/SolisAgileManager/SolisAgileManager/SolisManager/Services/InverterManager.cs:line 947

[Webreaper]

That error is nothing to do with communicating with Solis. I suspect there's some bad/unexpected data that's causing that exception. Have you tried restarting the SolisManager process/container?

[Webreaper]

@Nafeun1984 I've pushed some changes to add additional logging to see if I can understand your issue. Can you upgrade to this version: https://github.com/Webreaper/SolisAgileManager/actions/runs/21594202823 and then send me the logs of the crash?

[Nafeun1984]

Yep, will do, thanks mark