Closed sleepmaker closed 5 years ago
There is a reason I didn't include Ginlong in the current beta version, but I don't remember exactly. I will update this app in the summer (when I have got the time), then I'll look into Ginlong support again.
You're always welcome to submit a pull request!
It works for me, just installed it - did the same - also copied the plant id from the url like pid=1337 Too bad its removed in the beta
@snelis so you are using an older version, is that right? Currently I have 1.4.3 installed
v1.4.3 of the app in homey
I have the same. Then why the .... is it not working at my place?
so if you go to homey insights, and select the solarpanels u see no data points ?
Nope. Not a single one. And I just checked and rechecked my plantID. My energy suppliëren show my plant production, so that is Working. I just don’t get it. Maybe I need some help from the technical Guys out there ....
I will take a look into this some time in the next few weeks. Do you have an account for me to test? Just send it via e-mail or private message (if that is a thing on GitHub).
Ginlong, Omnik, Trannergy and Solarman all use the same API framework. The last three migrated to a new version, while Ginlong did not. I just manually tried approaching the Ginlong API, and logging in works but fetching data does not give any result. Their app probably has the same problem, could you try installing that (on Android/iOS)?
This is also the reason why I didn't migrate the Ginlong driver to the new version of this app.
I have the app on my iPhone. But this one does give me live output. As you may have noticed it is quite a sunny day today and my panels are producing 4.71 kW right now as I check the app
I'll reverse engineer the app again, in that case. It might use a different endpoint or API key.
OK. So Solis support is completely dropped as of the newest version?
Op 18 apr. 2018, om 15:07 heeft Diederik Bakker notifications@github.com het volgende geschreven:
Ginlong, Omnik, Trannergy and Solarman all use the same API framework. The last three migrated to a new version, while Ginlong did not. I just manually tried approaching the Ginlong API, and logging in works but fetching data does not give any result. Their app probably has the same problem, could you try installing that (on Android/iOS)?
This is also the reason why I didn't migrate the Ginlong driver to the new version of this app.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/DiedB/SolarPanels/issues/9#issuecomment-382379910, or mute the thread https://github.com/notifications/unsubscribe-auth/AQ55inwh_FvdkEqAYO0NmuAwAal7VXkFks5tpzqQgaJpZM4St-qs.
It is not supported in the current version, as they do not provide a documented API.
Hello,
Thanks for you effort in developing the app.
I've got a Solis inverter with the following wifi dongle:
https://www.cclcomponents.com/solis-plug-in-wifi-stick
I note that in the dongle interface it's possible to setup 3 remote servers (one of which I assume is the Ginlong site). The page states the following:
Your device can transfer data to several servers in the form of TCP/UDP if your device supports this function. Please make sure that the response to ping request function is enabled on the assigned server for receiving data.
Do you think it would be possible to use the functionality to send the data to Homey? I can assist with development if it helps.
Regards,
Their monitoring platform does not seem to have an API.
Maybe a direct connection to the inverter could be an option, but that is very hard to test if I do not have one of these devices in my own local network.
https://github.com/graham0/ginlong-wifi/blob/master/read-ginlong.py
If someone wants to look into this and create a pull request, feel free!
I might get a chance in the next week or two to try the above script on a Linux system but will Homey accept such data on an incoming port?
I can setup my system to point to a particular server if that helps with development.
Nice work fella’s. I don’t have the programming knowledge to help you out. But it would be greatly appreciated if you can get this to work
If there’s anything I can assist you with, please let me know
Thom
Op ma 1 apr. 2019 om 12:18 schreef leo389 notifications@github.com
I might get a chance in the next week or two to try the above script on a Linux system but will Homey accept such data on an incoming port?
I can setup my system to point to a particular server if that helps with development.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/DiedB/SolarPanels/issues/9#issuecomment-478521894, or mute the thread https://github.com/notifications/unsubscribe-auth/AQ55ijFy0xZPi8PUpQNpkJ67A232coSmks5vcd0SgaJpZM4St-qs .
@leo389 Ah, I see that the script opens up a server that listens for data from the inverter stick. That will probably not be possible using the current Homey SDK and is also a little too complicated for the app.
Bit of a pity as I just tested the script & it works as advertised!
Just had a look at the web traffic from the app & managed to capture what looks like the authentication process & then requests for data etc..
I'm not much of an expert on this stuff but 3 or 4 websites during signing-in, obtaining data etc.
Do you have a PCAP file?
Don't have a pcap, will try & grab one but the request from the app looks straightforward enough, a get request with a user ID & a token. The return is all the status info.
Will try & see if I can replicate a request.
On Tue 2 Apr 2019, 23:53 Diederik Bakker, notifications@github.com wrote:
Do you have a PCAP file?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/DiedB/SolarPanels/issues/9#issuecomment-479241892, or mute the thread https://github.com/notifications/unsubscribe-auth/AmUnW_FBn9bke2cXSwuh4KsQhHTBOI11ks5vc99dgaJpZM4St-qs .
Some success it seems!
I've managed to retrieve data using the following curl command (from a linux system):
curl 'http://apic-cdn.solarman.cn/v/ap.2.0/plant/get_plant_overview?uid=123456&plant_id=12345'
The pieces of info needed are straightforward to obtain:
Initially I thought a token was required but so far it seems to work without one. If the token is required I obtained mine by using a packet capture app on my phone to capture packets & picked the token from that. Hopefully it continues to work without the token.
I can send on the retrieved data if you like.
Whats the best way to help you reincorporate the Ginlong inverters? Is it to try & modify something like
https://github.com/DiedB/SolarPanels/tree/ca96283269138fb0e372e3c9369ebbd659ea4cde/drivers/solaredge
It seems to be implemented with parsing a json stream.
If you look at the alpha branch, the Enphase implementation I just pushed is a great example. Let me know if you have any questions and I'll be happy to help!
Just created an upload request with the work I've done. It's just a start but some work done. I'm unsure of some of the nodejs stuff (I use mostly C) so it's rough around the edges..
The app builds & runs but's getting stuck in api.js.
Also I'm unsure if I created the pull request properly..might be the wrong branch
Cool! I have removed and recreated the PR in the correct way, you can find it here: https://github.com/DiedB/SolarPanels/pull/55/files
I cannot give you access to push to the branch though, you will have to create a fork with your changes and then submit a pull request to allow that.
Can you share your Ginlong account with me for testing? My email address is [redacted]
I've built an implementation that runs fine. I do not trust this API one bit however. Invalid JSON, misspelled names, Chinese signs everywhere. We'll just see if it keeps working.
I'll add the two people that sent me an email with account details to the alpha version. Please report back if it's working for you.
Bummer. Installed the alpha. Thanx for the invite btw. I’m getting an error message. It’ll be attached to this mail. Hope it helps
Thom
Verstuurd vanaf mijn ZX-81
Op 17 apr. 2019 om 12:12 heeft Diederik Bakker notifications@github.com het volgende geschreven:
I've built an implementation that runs fine. I do not trust this API one bit however. Invalid JSON, misspelled names, Chinese signs everywhere. We'll just see if it keeps working.
I'll add the two people that sent me an email with account details to the alpha version. Please report back if it's working for you.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
It looks like the plantID has changed Using a new one (163753) the app goes on a little further but then another error message appears
Verstuurd vanaf mijn ZX-81
Op 17 apr. 2019 om 12:12 heeft Diederik Bakker notifications@github.com het volgende geschreven:
I've built an implementation that runs fine. I do not trust this API one bit however. Invalid JSON, misspelled names, Chinese signs everywhere. We'll just see if it keeps working.
I'll add the two people that sent me an email with account details to the alpha version. Please report back if it's working for you.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
....... Nevermind My plant id is somewhere else on the new website to be found (128306) This one works! For now
Verstuurd vanaf mijn ZX-81
Op 17 apr. 2019 om 12:12 heeft Diederik Bakker notifications@github.com het volgende geschreven:
I've built an implementation that runs fine. I do not trust this API one bit however. Invalid JSON, misspelled names, Chinese signs everywhere. We'll just see if it keeps working.
I'll add the two people that sent me an email with account details to the alpha version. Please report back if it's working for you.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
Can you document the process of finding the plant ID? I would like to include it in a README before publishing.
Login to "http://m.ginlong.com/main.html" using your Ginlong credentials Select "installatie informatie" in the upper part of the screen On the new screen you will find your "installatie-ID" Use this number as your "Ginlong PLANT-ID" in the Homey-app
Does this suffice?
Thom
Op wo 17 apr. 2019 om 12:39 schreef Diederik Bakker < notifications@github.com>:
Can you document the process of finding the plant ID? I would like to include it in a README before publishing.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/DiedB/SolarPanels/issues/9#issuecomment-484031428, or mute the thread https://github.com/notifications/unsubscribe-auth/AQ55itmcBFdtmd4IhCQS8GY7PCxOzdjsks5vhvnQgaJpZM4St-qs .
Many thanks for the work, I hope my stuff was of some use!
v3.0.5 is working for me, & the data it presents matches the Ginlong app.
If I may could I suggest the following editing/ addition to sleepmakers process
Would it be possible to include in the app some method of indicating that the API has broken? Perhaps push an Issue to this github repo or notifying the user on their phone?
I’m OK with this
Op wo 17 apr. 2019 om 14:01 schreef leo389 notifications@github.com
Many thanks for the work, I hope my stuff was of some use!
v3.0.5 is working for me, & the data it presents matches the Ginlong app.
If I may could I suggest the following editing/ addition to sleepmakers process
- Login to "http://m.ginlong.com/main.html" using your Ginlong credentials
- Select "Plant Info/ Installatie informatie/ " in the upper part of the screen
- On the new screen you will find your "Plant ID/ Installatie-ID/ "
- Use this number as your "Ginlong PLANT-ID" in the Homey-app
Would it be possible to include in the app some method of indicating that the API has broken? Perhaps push an Issue to this github repo or notifying the user on their phone?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/DiedB/SolarPanels/issues/9#issuecomment-484053793, or mute the thread https://github.com/notifications/unsubscribe-auth/AQ55iiq0lYahSr47SRqF0K_IY7aaTcmlks5vhw0agaJpZM4St-qs .
Has been released in v3.0.6. Forgot adding the guide, will do in a future release. Thanks for the help!
I've connected my Homey to my solarpanels, using the login credentials from the ginglong monitoring website. The credentials are accepted, I copied the plant-ID from what was shown in the browser bar after logging in. So far everything seems fine. But..... I can't see any energy production being recorded. When viewing through the dedicated ginglong-app on my phone I can see the energy production. Why is the Homey plugin not recording data?