Closed mriksman closed 1 year ago
I see the grott
owner has a grott_ha
extension
https://github.com/johanmeijer/grott/tree/master/examples/Home%20Assistent
It drops the buffered packets.
# Need to decode the json string
jsonmsg = json.loads(jsonmsg)
if jsonmsg.get("buffered") == "yes":
# Skip buffered message, HA don't support them
if conf.verbose:
print("\t - Grott HA - skipped buffered")
return 5
What benefits are there to using homeassistant-grott
vs using the grott_ha.py
directly from the link above?
@mriksman - Thanks for the heads up on the grott_ha extension way of handling this - I'm going to implement this in my version.
Sorry for the delayed response, I've been away on holiday and I'm now catching up on all the various bugs and tickets that have been raised.
I also suffered from this buffering issue over the last couple of days (my graphs look hilarious) so I'll be implementing the same logic myself.
As for this integration vs the one from the Grott repo - it's totally up to you. Johan has openly admitted that he doesn't really support the HA integration in his repo. Plus it's quite a primitive read-only implementation, the plans for my version of the integration is to grow it to also allow configuration of the inverters so that people can use it to configure AC charging windows etc. for battery systems.
I'll keep you posted on when I've implemented the buffered data handling (note - Home Assistant doesn't support historic insertion of data, so I'll just have to drop it).
This functionality is now available on the main
branch for testing (you can select this in the re-download menu in HACS)
You should see something like this now when it encounters buffered data:
(I had a LOT of buffered data today due to a network issue at my house)
@mriksman - Has this been working correctly for you? I'm closing the ticket so that it can be included in the next release.
My
grott
was down for a few days. Now that it's back, the data from the last 3 days is being sent inbetween fresh data. However, MQTT/homeassistant-grott doesn't seem to care that it is buffered/different timestamp, so I am seeing this.These are the buffered messages coming in. See
"time": "2023-05-28T13:43:31", "buffered": "yes"
And the real-time data
Is there a way to