I use both, the wemos on the 485-1 or 485-3 port and the shine stick on the usb (sph-8000). If you read the fine print in the extended warranty conditions it says somewhere that the device needs to be capable of being monitored. Specifically relevant for batteries.
The problem is mainly that it blocks the account during nighttime. That can most likely (pretty sure) be solved by adding the option to diable the polling after sunset and turn on again after sunrise.
The GROTT function works, I have this running actually (using the IP of my HA on my synology). At least GROTT forwards the data to Growatt.
Thge problem is MQTT, how does it work when you already have it running for a awtrix display (This is the BEST MATRIX DISPLAY CLOCK for Home Assistant!)
I think it needs to be configured for both, but it says it says it’s already configured. Also, no idea where the get the data from then, I just don’t see it which make me think MQTT is not working for GROTT in my case. To my knowledge MQTT needs a user to work, which is the case with the awtrix display. But there is no (I don’t see it anyway) about that in the descriptions. I’m lost with GROTT.
BTW, I also want home wizzard to work which needs the external data anyway. They have it workinh perfectly for Growatt, so it’s possible for sure.
I know about this problem but again, recently something changed to a new url…if you are already using the new url then I have no clue (and no interest myself)
For the MQTT, you need to configure this in grott (.ini or .cfg or something), follow th doc
I now tried every URL and the only one working (I tried them all) is openapi.growatt.com, but it lock out the account after a while.
Grott simply doesn’t work for me for some reason and I also don’t want to loose the Home Wizzard connectivity. Maybe it’s possible to for someone smart enough to figure out how home wizard is doing things and where it connects to.
Yeah,…the openapi is the one that Growatt themselves communicated (see below), it contains an email so maybe contact them directly? Maybe it is limited for a #calls a day ( I would also limit that if I would provide an API)
Then, I would not know why grott won’t work as it does for may others, maybe raise issues/errors s bit more detailed so people can try to help? But I reed that you need the growatt server for homewizzard, that I cannot help with…see above/below
the only thing is when its night or no power at all, the device shows unavailable. but does not affect data or history reading / writing.
As i dont bother about it i ignore it, but it is fixable.
It is possible htat my Growatt 8000 TL3-S inverter doesn’t measures the exported energy to the grid and imported from grid?
I have ShineWifi-S datalogger and I cannot see such kind of parameters.
does it still send the data to Growat Cloud servers If I flash the Growatt wifi dongle?
I am trying to understand the data flow and wonder if possible to send the data to Home Assistance and Growatt Cloud servers at the same time?
The ‘grott’ solution receives the data and forwards that to the Growatt cloud server (if wanted) acting as a proxy. I did not need to flash my shinewifi-x …it connects fine to grott. The use of the growatt cloud is 0 (zero) to me now that I have all in HA
I wonder if there is a solution out there that can provide some sort of fallback mechanisation in case of HA or ( Grott ) goes down?
I still would like to be able to send the inverter data to the Growatt cloud in case of the HA outage.
Is it really that important, would be my question…the inverter stores the total/growing amount and communicates that … so it would only show a gap on the per day/hour views if(!) this happens
2023-12-21 12:14:52: New connection from 172.XX…XX2:40219 on port 1883.
2023-12-21 12:14:52: New client connected from 172.XX.XX.2:40219 as Grott - HA (p2, c1, k60, u’addons’).
2023-12-21 12:14:52: Client Grott - HA disconnected.
2023-12-21 12:15:52: New connection from 172.XX.XX.2:36931 on port 1883.
2023-12-21 12:15:52: New client connected from 172.XX.XX.2:36931 as Grott - HA (p2, c1, k60, u’addons’).
2023-12-21 12:15:52: Client Grott - HA disconnected.
2023-12-21 12:16:05: New connection from 172.XX.XX.2:36470 on port 1883.
2023-12-21 12:16:05: Client closed its connection.
2023-12-21 12:16:52: New connection from 172.XX.XX.2:54753 on port 1883.
2023-12-21 12:16:52: New client connected from 172.XX.XX.2:54753 as Grott - HA (p2, c1, k60, u’addons’).
2023-12-21 12:16:52: Client Grott - HA disconnected.
I stopped logging MQTT, too much non-sense filling diskspace so cannot tell.
Grott log shows it is sending mqtt every 5 mins and my mqtt shows the topic (did you check with MQTT browser?)
I can’t find the entity in the energy dashboard. what could be the reason? The communication with MQTT seems to be working. However, the solar value remains at 0
That might be jumping things
The order of data
inverter (dongle) > grott > mqtt > HA
For me this provides in HA a MQTT entity: sensor.growatt_generated_energy_total which can be used in the dashboard
That’s correct - one of the reasons that retain should be enabled on the MQTT settings for grott. Otherwise you restart Home Assistant when it’s dark to install an update, and the sensors are not re-discovered until it is light again.