foxthefox
foxthefox
looks to me that a direct access to data should be checked for existance before
First we have to find the suitable data for integration. I have made a small writup how to connect to the mqtt broker via node-red: https://gist.github.com/foxthefox/11ac35433c228085a8f5e25d5651632a If you can make...
can you post the collected data?
Thanks a lot, I will have a look into it. Even it might not be the newest fw, it is a starting point
I have played around with messages and decoding them. Sometimes is a stacking of protobufs. This worked for me to get the data: ``` message inverter_heartbeat { optional uint32 invErrCode...
Basically I have added only the stacking of messages for HeaderMessage, InverterMessage, PowerMessage, EnergyMessage, the basis for this is the same as yours. One exception, in the Header I deleted...
Did you take over my protodefinition? Fo me the deletion of the pdata=1 in the Header was important. The first id is the inverter heart beat and then is the...
> @foxthefox could you run this payload through your proto descriptor and let me know what the output is please? > Hex Bytes > > ``` > 0a2f0a04e003ef0410351820200128014014480150045801800103880103ca011058585858585858585858585858585858 > ```...
I will think about a proper reconnection. What should happen in your opinion when the device is switched OFF? In such cases there will no mqtt packets send.
I have created a checkbox in the config page, checking it enables the reconnection. Please have a trial with version 0.0.13 if it satisfacatory. Hopefully the reconnect counter is not...