Sunsynk integration

[jpmoriarty]

Any chance my sunsynk device could be added for input? Also any synology install advice appreciated! I think I've set up the Docker and done what I think is needed but am flying a bit blind!

Happy to provide any details from my system if that's helpful or needed. Thanks

John

[BorisBrock]

Hi John,
adding a new input plugin shouldn't be too hard, if the device offers a usable API. Feel free to create a pull request for sunsynk device integration.

Regarding Synology:
I've run Sunalyzer on my Synology DS for years. It works very well. Just make sure you have created a local folder somewhere to safely store the container's data.
Is there anything specific you are unsure about?

[jpmoriarty]

Ah hello, thanks so much for responding. Sadly my coding skills are playing around with a bit of HTML, Javascript and PHP and not much more, so I don't think I'd know how to go about doing a pull request! I had a look yesterday and it looked like I needed to write up the code and submit it?? Not sure that would be something I'd be able to pull off, although I might have a play with some of the coding GPTs and see if they have any ideas... Similarly on the docker installation, I'm pretty adept at following instructions and figuring things out, but i was just a little bit too "in the dark" yesterday to get it all up and running. So steps I took: * Created a container with the synalyzer:latest image * Added a "sunalyzer" folder under the docker file structure - that then gave me an error with a red box after that folder name, with the message "incorrect value" - really no idea what it's after there. I just added "required" in that box and it still gave me "incorrect value", so i changed it to "/" and that seemed to work * left the "environment" settings as they were - the path looked a little odd (/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin) but i wasn't sure what to change it to * that gave me a "container manager API has failed" error, which appeared in the log as " Create container sunalyzer failed: {"message":"invalid volume specification: '/volume1/docker/sunalyzer:/:rw': invalid mount config for type \"bind\": invalid specification: destination can't be '/'"}." Sadly i gave up at that point, particularly if it didn't look like there was a way to get the data from my device at this point in any case! As I say, happy to help if i can in any way, but suspect you need support from people with more skills than I have! Thanks in advance, John

…

On Wed, 19 Feb 2025 at 04:32, Boris Brock ***@***.***> wrote: Hi John, adding a new input plugin shouldn't be too hard, if the device offers a usable API. Feel free to create a pull request for sunsynk device integration. Regarding Synology: I've run Sunalyzer on my Synology DS for years. It works very well. Just make sure you have created a local folder somewhere to safely store the container's data. Is there anything specific you are unsure about? — Reply to this email directly, view it on GitHub <#86 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJBMXA6W3WV4XDQIJTFIJST2QQCPXAVCNFSM6AAAAABXLZBNK2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRUGUYDENY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- *John* 0779 271 4045 | ***@***.***

[jpmoriarty]

PS, I found this page which seems to be reverse engineering the Sunsynk API, which again might be useful / required! https://www.4x4community.co.za/forum/showthread.php/366452-Demystifying-the-Sunsynk-API John

…

On Wed, 19 Feb 2025 at 04:32, Boris Brock ***@***.***> wrote: Hi John, adding a new input plugin shouldn't be too hard, if the device offers a usable API. Feel free to create a pull request for sunsynk device integration. Regarding Synology: I've run Sunalyzer on my Synology DS for years. It works very well. Just make sure you have created a local folder somewhere to safely store the container's data. Is there anything specific you are unsure about? — Reply to this email directly, view it on GitHub <#86 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJBMXA6W3WV4XDQIJTFIJST2QQCPXAVCNFSM6AAAAABXLZBNK2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRUGUYDENY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- *John* 0779 271 4045 | ***@***.***