Mine also came with the E-Linter and it worked. It’s the inverter serial you want, not the linter’s.
Look in the cloud portal and it should show a serial number for the inverter. I can’t check mine since I disconnected it from the cloud the minute my RS485 gateway was connected and now I’m fully local/offline.
Thanks for your reply. I had already entered my inverter serial number, but not tried entering it again for where it was asking for the dongle serial number.
So I tried this add-on and after a bit of bother having to create a text helper entity called solarsynkv3_**********_settings it sprung in to life. Next step is to automate between Octopus and SunSynk…
I used that Solarsynkv3 with the linter for a few days until my modbus adapter arrived then I switched to Sunsynk add-on. That’s is why it wouldn’t work with the linter and Sunsynk, which is meant for offline/local access and not using the cloud account".
Sadly after much trying with YAML.configuration coding I have only been able to read data from my SunSynk inverter. I understand my e-linter wifi stick is for logging data only but had hoped I could control the inverter via the SunSynk Connect cloud website. Sadly the solarsyncv3 add-on doesn’t do that and while I understand from the SunSynk support website there is a public API, and even a very helpful article on how to obtain an access_token, there is no other documentation on the API calls, what’s available or how to use it.
I have gotten my SolArk working with Pbix’s setup, using an esp32 as a modbus to tcp converter and all is well enough… however - i’m wanting to test the write sensors - change amperage / enable disable grid charge and so on. Does anyone know if this has been tried yet and if its been successful.