I've had the same happen to me past 2 nights. Seems intermittent since other requests during the day worked fine.
But it would be good if the system tried the command again a few minutes later when getting communication issues since they are typically temporary. That way you wouldn't loose the entire cheap slot...
Maybe retry once, don't want to hammer services
I would like to add to this - my growatt system failed to charge last night and is still failing now. I can see you had issues with the data logger above - but the chances of it being a connection issue for multiple people seems slim. I will reset my inverter and see if it changes anything before reporting back. - Edit - just to add I can view my real time data on the growatt app
Regards above, I also had issue were the batteries failed to charge last night. I log growatt data at 10s intervals and could see that the growatt inverter received the charge start/stop instructions, however no change in battery SOC.
I also noticed that the sysenable mode was a value that I hadn't seen before during previous scheduled charges.
Data values and decodes from growatt MODBUS document.
Further more I zoomed into BAT1 enable/disable/charge rate settings for the period were batteries failed to charge. I also observed that the charge rate 'jumped' to 100% shortly after starting the scheduled charging session.
NB the BAT1 start/end values when decoded give start / end times.
Growatt Gremlins at work?
admin Thats really unusual that it has suddenly decided your access is denied. I will check the account settings and reset passwords. Nothing has changed from my perspective in the last few days. I was not able to do anything with the shinephone app when I was testing this morning, but I managed to get a charge on after I reset the "server" and the inverter.
cjohnstone How are you managing to log at 10s intervals? My shine server can barely cope with a ping
Slamc I use the RS485 port on my SPH3600 inverter and poll using python script. Data gets uploaded to INLFUX DB database.
Works well for me, I wrote a python script to run as CRON job. I run it every hour for 59 minutes just in case the program crashes so I dont lose too much data. (tho ive never had any issues apart from my own outages when updating the script).
A search for growatt inverter modbus RTU protocal should bring up document describing the protocol. There are several versions out there. V 1.24 works for my system.
The 10 second polling basically gives me real time monitoring of the inverter.
cjohnstone That is likely causing inverter timeouts where it gets overwhelmed with so many requests, especially when we issue instructions.
I think @WindyMiller had a similar issue on his Giv inverter and had realtime polling set up on multiple devices and once reduced, the inverter timeouts pretty much disappeared.
My suggestion would be to up the interval time and experiment with that.
What is your WattID by the way? Just to see if we had any failures in the logs or whether it all looked OK from Growatt API responses.
admin - wattid - major-start
Fisrt time I have seen this issue since I started logging AUG 23. The inverter did receive the command for BAT First and the time slots and charging rate were enabled, I did see some values in the syssetenable register that I havnt seen before.
A subsequent manual charge from quick schedule menu option was successfull.
cjohnstone Thanks for that.
Can't see any exceptions in the logs, so the instructions sent were all received fine by Growatt as far as we can tell.
admin Yep...definately a growatt thing, not wonder watt. if I get time I'll investigate further. From historical data I've observed changes in state of register 1008 (system enable). The particular value recorded last night 17208 was one I hadnt seen before. (I have a python script I use to decode the number).
If I have time, I will investigate further.
regards
cjohnstone Good sleuthing though, please share when/if you find out more.
