No Data after Soliscloud update AM 27/09

[corvus2606]

home-assistant.log After Soliscloud was updated early this morning, there is no data coming through on the sensors. on a HASS restart, I am seeing the below errors:

Config

• platform: solis name: "My Solis Inverter" portal_domain: "www.soliscloud.com:13333" portal_username: ****** portal_key_id: ****** portal_secret: !secret Solis portal_plant_id: ********

Versions HA Docker install, 2022.9.7 HACS version: 1.27.2 Integration version: 2.3.4

Debug logs

2022-09-27 10:20:39.686 INFO (MainThread) [custom_components.solis.soliscloud_api] Login Successful! 2022-09-27 10:20:39.918 DEBUG (MainThread) [custom_components.solis.soliscloud_api] Found inverters: ['************************'] 2022-09-27 10:20:39.918 WARNING (MainThread) [custom_components.solis.service] Failed to discover, scheduling retry in 180 seconds. 2022-09-27 10:20:39.919 DEBUG (MainThread) [custom_components.solis.service] Scheduling discovery in 180 seconds.

Screenshots

[defeatedbythecat]

Same issue this morning

[drsmarsden]

This is what I saw

2022-09-27 03:45:04.516 DEBUG (MainThread) [custom_components.solis.service] SMSM hour [3] min [45] energy [0.000000] 2022-09-27 03:45:04.516 DEBUG (MainThread) [custom_components.solis.service] Scheduling next update in 2 minutes. 2022-09-27 03:47:04.611 DEBUG (MainThread) [custom_components.solis.soliscloud_api] Error from URI (/v1/api/addUser) : 0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://www.soliscloud.com:13333/v1/api/addUser') 2022-09-27 03:47:04.611 DEBUG (MainThread) [custom_components.solis.service] Scheduling next update in 1 minutes. 2022-09-27 03:48:04.716 INFO (MainThread) [custom_components.solis.soliscloud_api] Login Successful!

[corvus2606]

so it seems they've probably made an undocumented change to their API, this is why i prefer to avoid cloud based services...

[liveware-problems]

This was working for me before the update to Solis Cloud, and this morning there is no data. However, I've checked the apiManage page and it now shows Nonactivated whereas before I had an active key. Trying to re-register for a key now results in the 'No Authority' error discussed on the Solis Cloud comment thread:

[defeatedbythecat]

Mine showing as active, but still having the issue above

[corvus2606]

I'm getting the same error when trying to reactivate the API access

[corvus2606]

I've logged a support ticket with their team, awaiting a response.

From what i can tell, the API has now been locked behind some extra permissions, even the API management option is missing from the basic settings page, we have to type the address directly.

Hopefully this is just an error and not a permanent move by them.

[RIA-Ingo]

same problem here.. but after Uptdate to 2022.9.7

[hultenvp]

so it seems they've probably made an undocumented change to their API, this is why i prefer to avoid cloud based services...

I believe this is a regression on their side. Let's hope it's not intentional.

Propose to await response on ticket logged by @corvus2606.

This is not the first time and will probably not be the last time SolisCloud will see instability. It looks they're still actively developing. I recommend to use m.ginlong.com if you require stability.

[liveware-problems]

I also logged a ticket with Solis Support about this.

The issue with using m.ginlong.com is that I'm not sure the newer datalogger supports this platform - I think older hardware registered on ginlong.com and then migrated to soliscloud, whereas the newer S3-WiFI-ST stick seems to only register on soliscloud and there is no option to migrate from there to ginlong.com

I'll have a try anyway 😄

[corvus2606]

this has been the prompt i needed to give in to my urge to avoid cloud based integrations. I'll be going down the route of an RS485 ethernet bridge and monitoring over modbus.

I never was super fond of the idea of freely giving away all of my electricity usage habits to a chinese entity anyway.

We'll see what they say on the support ticket and I'll feed back here regardless

[GillesC]

this has been the prompt i needed to give in to my urge to avoid cloud based integrations. I'll be going down the route of an RS485 ethernet bridge and monitoring over modbus.

I never was super fond of the idea of freely giving away all of my electricity usage habits to a chinese entity anyway.

We'll see what they say on the support ticket and I'll feed back here regardless

I agree. Could you share the procedure when you are able to get this work?

[usbrit]

Same issue, please keep progress updated. Thanks

[abbamust]

Mine also have the same issue. But do this have anything to do with the upgrade to HA 2022.9.7? Or is this a problem the SolisCloud have caused?

INFO (MainThread) [custom_components.solis.soliscloud_api] Login Successful! DEBUG (MainThread) [custom_components.solis.soliscloud_api] Found inverters: ['', ''] WARNING (MainThread) [custom_components.solis.service] Failed to discover, scheduling retry in 60 seconds. DEBUG (MainThread) [custom_components.solis.service] Scheduling discovery in 60 seconds.

[corvus2606]

this is not caused by Home assistant, this is a problem on the Solis Cloud side. I've had indications that they may have withdrawn API access citing GDPR issues. I'm awaiting confirmation of that

[dhoogfr]

Curious what kind of GDPR issue that could be. I mean, the data is still being send to Solis Cloud, the API only makes it available for the user via a different method than the website. Unless they gather statistics on the API usage and additional approval is needed for that (or it isn't about GDPR, but about security...)

[corvus2606]

yeah, until we get an official answer, it's all rumour and speculation unfortunately. Either way, the end result for us is the same...

[hultenvp]

this has been the prompt i needed to give in to my urge to avoid cloud based integrations. I'll be going down the route of an RS485 ethernet bridge and monitoring over modbus.

I never was super fond of the idea of freely giving away all of my electricity usage habits to a chinese entity anyway.

We'll see what they say on the support ticket and I'll feed back here regardless

There was a link in one of the issues or in the discussion thread to an integration that would potentially work. EDIT: Found here: https://github.com/hultenvp/solis-sensor/discussions/71#discussioncomment-2921478

Regardless of what will happen to the SolisCloud I will continue to maintain this integration. Mostly because it's fun and a great learning experience ;-). For now I'll monitor the situation and leave the ticket open, not much I can do to deal with a disabled/broken service. Please post any new info anyone might have here.

[corvus2606]

@hultenvp Of course, nothing against you or the work you've done, this integration would have been the perfect solution had solis chosen to be a reliable data provider.

Thank you very much for the work you've done on this!

[abbamust]

It looks like the datalogger I have is not working with ginlong, so for now I am a little stuck. Anyone tried to read from the new datalogges via IP adress?

[Moondevil-ha]

I have a datalogger with serial starting "5A" which will not allow me to set up any local access. I was going to attempt it, but can see no way forward without building an MQTT2RS485 interface?

[tobes49]

I also logged a ticket with Solis Support about this.

The issue with using m.ginlong.com is that I'm not sure the newer datalogger supports this platform - I think older hardware registered on ginlong.com and then migrated to soliscloud, whereas the newer S3-WiFI-ST stick seems to only register on soliscloud and there is no option to migrate from there to ginlong.com

I'll have a try anyway 😄

I've got the same problem so fingers crossed they fix it soon.
I too have the S3 stick and have looked at direct access but cant seem to find a username or password to let me access the stick (tried admin/admin also admin/S/N etc) - would anyone have this?

[corvus2606]

It looks like the datalogger I have is not working with ginlong, so for now I am a little stuck. Anyone tried to read from the new datalogges via IP adress?

the newer model of datalogger is locked in to Solis Cloud and also doesn't publish any data that can be read using the solismon integrations, you can't even scrape the data off the page thanks to ajax. The only option with those is to replace them with an older model, or use an RS485 module and interface directly with modbus

[corvus2606]

I also logged a ticket with Solis Support about this. The issue with using m.ginlong.com is that I'm not sure the newer datalogger supports this platform - I think older hardware registered on ginlong.com and then migrated to soliscloud, whereas the newer S3-WiFI-ST stick seems to only register on soliscloud and there is no option to migrate from there to ginlong.com I'll have a try anyway 😄

I've got the same problem so fingers crossed they fix it soon. I too have the S3 stick and have looked at direct access but cant seem to find a username or password to let me access the stick (tried admin/admin also admin/S/N etc) - would anyone have this?

the username is 'admin' and the password is your wifi password.

but as i said above, it doesn't support rest api requests like the old ones did, so you can't use it to pull data

[corvus2606]

I have a datalogger with serial starting "5A" which will not allow me to set up any local access. I was going to attempt it, but can see no way forward without building an MQTT2RS485 interface?

I am waiting to receive a RS485 ethernet bridge. you can then integrate with it using the modbus integration in home assistant without the need to have MQTT in the middle.

I'm working off a lot of the things in this thread: https://community.home-assistant.io/t/getting-data-from-solis-inverter/302189/70?u=corvus2606

[spetrie13]

S3 stick.

Not found a way to get data from it.

Once configured and connected to your network, login with admin password is your wifi password

On Wed, 28 Sept 2022, 10:23 tobes49, @.***> wrote:

I also logged a ticket with Solis Support about this.

The issue with using m.ginlong.com is that I'm not sure the newer datalogger supports this platform - I think older hardware registered on ginlong.com and then migrated to soliscloud, whereas the newer S3-WiFI-ST stick seems to only register on soliscloud and there is no option to migrate from there to ginlong.com

I'll have a try anyway 😄

I've got the same problem so fingers crossed they fix it soon. I too have the S3 stick and have looked at direct access but cant seem to find a username or password to let me access the stick (tried admin/admin also admin/S/N etc) - would anyone have this?

— Reply to this email directly, view it on GitHub https://github.com/hultenvp/solis-sensor/issues/162#issuecomment-1260631009, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYRF45ZNBOOTX3UOWSOED33WAQFABANCNFSM6AAAAAAQWS2U5Q . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[rmhomecouk]

I was loving the simplicity of this integration but the outage has pushed me to stick an Ethernet bridge in place of the stick. So far so good (the bridge is a PE-11 unit which seems really solid).

[liveware-problems]

Is that an AC powered PE-11 you are using @rmhomecouk ? So the yellow cable is just the RS485 data connection? I'm looking at these options, but think the port on the inverter (as used by the stick) only supplies +5v DC:

Protoss-PE11-M is RS485 to Ethernet server, no wifi, power input 9V to 48VDC;

Protoss-PE11-H is RS485 to Ethernet server, no wifi, power input 100V to240VAC;

[Moondevil-ha]

I am looking at something like this: Serial Port RS485 to WiFi Device Server Module Elfin-EW11 f TCP/IP Protocol Data: https://bit.ly/3UIQh1I I'm ordering and going to get my thinking cap on.

[corvus2606]

I ordered this unit: https://www.amazon.co.uk/dp/B08NW79RNK?psc=1&ref_=chk_typ_imgToDp

It takes 5v power from the port, so hopefully it'll be self contained. I'll report back when it arrives