-
Notifications
You must be signed in to change notification settings - Fork 3
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
ShineWiFi-S compatibility #1
Comments
Sorry, I don't know. I just tested it with my wifi stick. But I guess it's compatible with older versions of the protocol as well.
With this setting you can see if the client get connected and every message that come in. |
got it, I'll report back when i get there later. |
I think the difference between these is the inverter models.. I've got one of the All In One Charger/Inverter: SPF 3000TL LVM P.S. in the readme you've got /ftui/ in the URL for install on your clone line. |
Ok, here's the output: `pi@Farm-pi:~/Growatt-server $ perl growatt_server.pl --debug=3 2021-04-22 13:52:11 ======= SERVER ==== REPLY ===== |
your ANNOUNCE message doesn't contain a valid date. It is all zeros.
|
this is what I ended up with:
which now produces: |
interesting, sometimes if i run it I get what looks like usable data: pi@Farm-pi:~/Growatt-server $ sudo perl growatt_server.pl --debug=3 2021-04-22 16:35:26 ======= SERVER ==== REPLY ===== timestamp: 2000-00-00 00:00:10 |
Not really. Something must be shifted when decoding. We need a little more verbose log. Please start with log level 4 to get the raw messages
|
pi@Farm-pi:~/Growatt-server $ perl growatt_server.pl --debug=4 split_message buffer_length 20 2021-04-22 22:59:57 ======= SERVER ==== REPLY ===== split_message buffer_length 0 split_message buffer_length 225 time diff:1619128805 2021-04-22 23:00:05 ======= SERVER ==== REPLY ===== 2021-04-22 23:00:05 ======= SERVER ==== REPLY ===== split_message buffer_length 0 split_message buffer_length 225 timestamp: 2000-00-00 00:00:10 split_message buffer_length 0 split_message buffer_length 23 split_message buffer_length 0 split_message buffer_length 25 |
you have protocol version 5. This have to be decodes differently. I try to figure it out and adapt the code accordingly. |
Don't spend too much time on it, I think someone has already figured it out. Check out the project over at Grott https://github.com/johanmeijer/grott |
I added some protocol 5 specifics, but the output values for your examples of message 0x50 make no sense to me. I tried a lot of position and also the settings from other projects. Eac_today: e.g. 3KWh |
Maybe you need to talk to JohanMeijer to coordinate a better version of both codes. |
Hello guys, Did some one managed to get it work recently ? Month '88' out of range 0..11 at growatt_server.pl line 416. |
Hey I don't expect you to know this, but maybe you do. I've got what I'm guessing is an older WiFi-F USB model. In your research on building this, did you come across anything that supports the protocol being the same? the -X seems to be an updated unit but I'm assuming they're interacting with the same growatt API, thus communicate identically.
Also, mine is reported as a -S model, but all online documentation and images match the -F linked above. I donno.
If you don't know, I'm willing to give it a go. I've got your script installed on a MQTT listening RPi onsite. but just need to go onsite and configure the module.
I think your approach is the best one of the many out there for getting data from these things and avoiding the bad growatt interface and communications.
The text was updated successfully, but these errors were encountered: