Auto reconnect

[keukenrol]

Hi

i have this module (updated fork from @apelders) running on a raspberry pi via wi-fi. Sometimes the wi-fi does disconnect but it seems the node does not reconnect.
The only option is to re-deploy the nodes.

Secondly, when the inverter stops working (when solar input is 0) the modbus data stops. In the morning when it is back online I also manually have to re-deploy the node in order to get it working again. It seems to be the same cause.

Thanks!

[keukenrol]

Edit: as soon as the inverter is turned off, i can restart the flows. It will try to connect as soon as the inverter restarts. At the moment my method is to restart the node every night before going to sleep.

[apelders]

Thanks for the trigger. I noticed the same issue.
After deploy the data flows in again.
I'm not sure if I'm able to fix it, but I will give it a try.
If anyone can help, that will be appreciated.

[keukenrol]

Maybe as a temporary solution you can add an extra user settable condition in which you can set when to restart the node. For example restart the node every night at 2AM.

I have the impression it might have something to do with the modbus library. In the code I do not see a reconnect condition.

[apelders]

I'm sorry. Due to illness I'm not able to solve this quickly.

[keukenrol]

I was thinking about adding an extra parameter to automatically close and reopen the connection at a set time, for example every day at 1AM. But no worries, health is a priority. Take care!

[apelders]

Hi keukenrol,
I found some time to test what I thought could cause and solve the problem.
In my pallette I saw some nodes were not up to date anymore.
My experience is that updating it from the pallete not always works as expected.
For that reason have setup my system using https://github.com/Paraphraser/PiBuilder
With prepared image and restoring the rclone backup I was able to rebuild my system.
During this rebuild it loads all latest nodes, setting and flows.
After that the connection seemed to be stable.
I will monitor the upcoming days and let you know if this solved the problem.

[keukenrol]

Hi keukenrol, I found some time to test what I thought could cause and solve the problem. In my pallette I saw some nodes were not up to date anymore. My experience is that updating it from the pallete not always works as expected. For that reason have setup my system using https://github.com/Paraphraser/PiBuilder With prepared image and restoring the rclone backup I was able to rebuild my system. During this rebuild it loads all latest nodes, setting and flows. After that the connection seemed to be stable. I will monitor the upcoming days and let you know if this solved the problem.

I will try that. However a remark about npm. The latest version available is 1.0.2 while yours is 1.0.4. I dont know about the dependency of modbus tcp.

Edit: I did remove and reinstall the package using npm, and afterwards I did overwrite the install folder in /.node_red/node_modules/ with the version 1.04 I downloaded from your github. First night went ok, no connection loss.

[keukenrol]

After a few days now I can confirm that the method I listed above does work.

I do have a remark:
In case the network resets / fails (router/switch reset) it still does not automatically reconnect. You have to restart the flows.

I can conclude this implementation does work under normal "ideal" circumstances, but does not account for possible 3rd party failure as no auto reconnect feature is implemented.

[keukenrol]

Few weeks later and we are back at how it started. Having to reset the nodes every 1-2 days, always after a night. As long as no reconnect functionality is implemented this issue will remain. I suppose the reconnect does situate itself in the used modbus-tcp library, rather than the solaredge sunspec implementation.
Still broken as off 30/10/2024. The issue arises 2 hours after the inverter shuts down for the night.