[App][Obsolete]Sofar / Solarman

Https is only used for the Solarman cloud. The local connection is via a socket to a local IP and port.

1 Like

But your new app Sofar isn’t it local only?
When trying to install a solar panel device, it says new devices found and should check the modbus address, why would it then give HTTPS: error ?

Even though I’m not really aware what you need, here’s what i found using:

https://www.google.com/search?q=sofar+mudbus&rlz=1CDGOYI_enIL992IL992&oq=sofar+mudbus&gs_lcrp=EgZjaHJvbWUyBggAEEUYOTIJCAEQABgNGIAEMggIAhAAGA0YHjIICAMQABgNGB4yCggEEAAYCBgNGB4yCggFEAAYCBgNGB4yCggGEAAYCBgNGB4yCggHEAAYCBgNGB4yCggIEAAYCBgNGB4yCggJEAAYCBgNGB7SAQg2MzM3ajBqN6gCALACAOIDBBgBIF8&hl=en-US&sourceid=chrome-mobile&ie=UTF-8#ip=1

Lots of articles here. Some of the articles seem to assume a wired connection, others go via tcpip/wifi antenna.

I selected a few, but if you provide some pointers I can search better.

https://library.loxone.com/detail/sofar-solar-inverter-892/overview

Sofarsolar ModBus-RTU Communication Protocol
https://solaranzeige.de/phpBB3/download/file.php?id=5254

If you use an application/library that supports Modbus to do the polling, then all you really need to tell it is that to get the ‘active power output’ value, poll register number 12 (0x000C in hex) and read an unsigned integer of size two bytes (16 bits), with a scaling factor is .001 and in kW units

The fact he reported an https error is why I keep reiterating that the Solarman cloud connection won’t work anymore. There is nothing in the new app that will report that error.

The Sofar inverters wrap the MODBUS packet inside another packet (they call it V5 protocol), so it’s not simply MODBUS.

However, the issue is that different inverter models use different MODBUS registers for the parameters, no idea why they couldn’t have standardised. So, you mention register 12 as active power, but that’s different for each model.
The app currently has maps for 4 different models and it tries to automatically determine which map to use by reading the ‘known’ register for grid frequency. If a valid frequency is returned then it assumes it has found the correct map, else it tries the register for grid frequency register the next map.

1 Like

Thank you for the explanation.
I am confused about what you refer to as the new app.
The https error is when creating a new device in the app Sofar v1.1.13

PS Sofar/Solarman v1.1.12 was not uninstalled, it is a lifeline we hope will work from time to time :slight_smile:

Would it be possible to add an user-input for the API-Key (App-settings-Field)?
So everyone uses its own ?
If I would be capable of developing my own app, I would setup something on the local http page from deye inverters. But I can’t :frowning:

FYI also problems here, perhaps join the effort?

I did consider that but obtaining a key from Solarman is not easy and Athom wouldn’t allow that method for Homey (cloud).
My code for the old app is still in my GitHub repo GitHub - AdyRock/ady.solarman so if anyone wants to install it via the CLI and make their own env.json file with their own keys they can.

2 Likes

The MODBUS app won’t work with the Sofar inverters as the MODBUS packet is wrapped inside their V5 packet.

2 Likes

Yes, but it seems like the guys there are trying to add more inverters like the Huawei to the SolarEdge+Growatt TCP modbus app. I was hoping to find some synergies to your efforts.

1 Like

Unfortunately, I have to admit that I lack the skills to connect otherwise. Did I understand correctly that if I want to transfer data to the Homey device, I will not be able to see it in the Solarman cloud?

Kontakt Adrian Rockall via Homey Community Forum (<notifications@athom.discoursemail.com>) kirjutas kuupäeval P, 3. märts 2024 kell 19:42:

I appreciate your trying to help and it makes me think, so thank you for that, and please keep suggesting things and asking questions as it could spark an idea.
But at the end of the day, the issue is tracking down register maps for each model of inverter.

I have found the misleading https error message, which is just a copy and paste issue that should have removed the https part.

2 Likes

No, that’s not the case. The inverters can update both local Homey and Solarman cloud. I can see my data in both, but I never use the Solarman app anymore as it’s too slow. The local connection updates Homey every 10 seconds whereas the cloud is limited to about 10 minutes.

1 Like

Here, in fact, the Homey developers themselves could show their good sales work and make it clear to Sofar the possible added value of their product in cooperation with Homey and Adrian. Thank you for your efforts - Adrian.

I just managed to add a panel and inverter with Sofar 1.1.13 SUPER - Hopefully it will work longer now.
image

2 Likes

Great! That means your SOFAR 15000TL-G2 MODBUS TCP address 01 is now sharing its data with the cloud (rate limited) and locally (unlimited) with your Homey.

@Adrian_Rockall Great job and thanks so much for your hard work!

2 Likes

The data didn’t start showing until the morning when I had to restart the Sofar app. Is there a possible solution here, or does Homey have to restart the app every morning?

Could you check the log to see if there are any errors?
I normally have the app running for weeks at a time and it only gets restarted if I’m adding new features or when Homey updates.

I must have explained it wrong. When the sun started to shine in the morning, the panels and inverter icons added to the Homey app last night did not show data. After restarting the Sofal app 1.1.13, the necessary data also appeared. At night, when the sun is not shining, the inverter and the logger turn off, and at that moment it cannot transmit data to the network. If in the morning the inverter started the application as a result of sunlight, I guess for some reason Homey did not start receiving data until the application was restarted.
diagnostic log too long to add here. I tried to send a log with your forum username. Hope I did the right thing.

1 Like

Ok, so the Diagnostics log shows error 404 which means the inverter was not found at 7:26 this morning. It looks like that was after the app was restarted, but it’s not entirely clear.
Could you check if the IP address of the inverter changes when it restarts?
If it’s using DHCP to get the IP the router might give it a different one each time it starts and the app might not pick that up until it is restarted and performes the discovery again. If that is the case then maybe assign a fixed IP, either in the logger or via a reservation in the router.
I will also look at triggering the discovery process again if the app gets a 404 error.

It could be useful to add a state online/offline, so we can test for the state in Homey and then restart the app if needed

@Adrian_Rockall
Side-question: How do I disable the built in AP in the Sofar inverter? Don’t need it anymore, since it is set up, and can connect through my regular network. It seems to interfere with the regular Wifi network.