-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is the intention to add control via the /v2/api/control endpoints? #278
Comments
I didn't know there was a control api document. Would it be possible to share it? |
I'm not sure I'm allowed to share it publically as it says "classification: Secret". Much of the security seems to be the same as you have in this repo (the hashed content header etc). Interesingly the password it requires in the v2/api/login {"userInfo":"username", "passWord": "md5hexdigestofpassword"} where the UserInfo is your username (or email?) and teh passWord is the md5 hex digest of the password. So far I've got it to login and give me a token (the login gives a lot more than just the token), I'm just not sure where to add the token as section 3.2 just says "need to use Token". I'll try to just add a "Token" header and see if that works 🤷 |
As I said, not sure if I'm allowed. However I just raised a request and asked for details of how to control via the api and they sent me the document in a few days. |
got a working example... https://github.com/stevegal/solis_control/blob/main/solis_control.py Note this this quite brittle and is more of a WIP at this stage! (note must have 3 time slots in the config for example!) there are a lot more control "cid" available as well, but being able to control the charge & discharge times is a good start. |
Nice! I've been thinking what entities to use if this is to be integrated with home assistant. I need to look deeper into it, but I guess it should be a derivative of a base entity. Then it would also need its own custom card or so to be able to control |
Mind Sharing how to get this working? (Looking for an solution to disable and enable powerexport remote by HA) |
Sure, you need to install pyscript HACS plugin first, then just paste the service code into the a file called solis_control.py in the pyscript directory and you should be ready to add it into your automations... or just it as a base for other scripts to call. https://github.com/stevegal/solis_control readme has the info you need. The plant id etc can be found in the same way as in awesome plugin, but it needs your username and password in addition to api keys. I'm not sure it needs turning on from solis for you. I asked if tehy had an api where I could change times and they responded with some documentation, which I got working without further contact with them, so I'm not sure if it gets turned on when you ask for your API keys (this would be my guess) |
That would be awesome! Is it on some how possible to retrieve a list of push/pull api index? The is i would love to control remotely is the "backflow/export grid setting" |
The api that I was using seems to have changed. There is, however, a new tikcet type of |
I don't suppose you have had any further luck with this. |
I'm very interested in this functionality as well. |
the control in the linked repo seems to be working fine. There was a bit of instability as solis rolled out their (unpublished) next version that they use in their web app, but the v2 control functionality seems to be stable. |
Hi @stevegal - I requested remote access, signed the nda, installed pyscript HACs plugin, installed solis_control.py and setup a script to call the service with my credentials. When I run the script, no errors are generated but there is also no effect to my inverter settings. Do you know if this is still working? Do you have any tips on debugging, for example how can I tell if the api has been called and if any error messages were issued? Thanks for the good work! |
@stevegal I asked Solis for the API this morning and I was not asked to sign an NDA. The docs are on their OSS server. |
What email pls. is only think stopping me from using it 😊
Refuse to sign an NDA
From: Steve Workman ***@***.***>
Date: Monday, 8 July 2024 at 3:01 PM
To: hultenvp/solis-sensor ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [hultenvp/solis-sensor] Is the intention to add control via the /v2/api/control endpoints? (Issue #278)
@stevegal<https://github.com/stevegal> I asked Solis for the API this morning and I was not asked to sign an NDA. The docs are on their OSS server.
* API https://oss.soliscloud.com/doc/SolisCloud%20Device%20Control%20API%20V2.0.pdf
* List of commands https://oss.soliscloud.com/doc/SolisCloud_control_api_command_list.xlsx
—
Reply to this email directly, view it on GitHub<#278 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AUESEBQ7C5PBYXQR6CL6LVDZLI2LRAVCNFSM6AAAAAAXBSNVPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJTGE4TCNRWGQ>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
I contacted Solis support through their official channels and the above was what I got
|
I got it working today, maybe the API changed recently and stevegal branch was not working to me. I´ll create a branch with my changes. |
I've added this via PR #398 |
I've asked solis for the control api documentation and they sent me a pdf of the control api.
Would this be something that would be considered for support in the future?
The text was updated successfully, but these errors were encountered: