binsoul / node-red-contrib-deye-sun-g3

MIT License
6 stars 1 forks source link

Randomly stops working #5

Open mintdaniel42 opened 1 year ago

mintdaniel42 commented 1 year ago

Hello 👋🏼 I tried your node works really well in general but it always stops randomly and says "unavailable" although the inverter is only. The only way to reset the node is to restart node red.

GerhardLang commented 9 months ago

Hello. I have to jump in - similar problem. Sometimes the inverters stay on state updating or unavailable and after that no injection helps, only a restart of the flow by changing something, saving and then it works again. I do have 12 inverters I want to check, the bug occurs randomly on these.

It is a great node, so it would be really incredibly helpful for me if there is a possibility to have a reset of the node without manually interaction, or an error correction. @binsoul do you think you can find a solution?

binsoul commented 9 months ago

So the node enters a state where the inverter is permanently marked as unavailable? Is there anything visible in the log files of Node-RED? Maybe an uncaught exception happens and Node-RED deactivates the node or something.

GerhardLang commented 9 months ago

Hello. Thanks for the answer, yes mostly half of the inverters are going unavailable, always different ones. With a node change = flow restart it begins working with the same problem. I did not check the logs. Meanwhile I did help myselft with a github solution deye to mqtt container which works perfectly without any unavailability. Maybe my hint helps you, maybe it is only because I do have such an amount of inverters running.

mcponta commented 8 months ago

Hello I have the same problem and one more.

sometimes the node stay in updating for ever in loop, I need to reploy the flow to restart.

Forgive my English mistakes.