Posibility to persistent store "on" evens

[komw]

I have some problems with my eBUS Adapter Stick C6 Ethernet module (usr-es1).
I had identical problems with previous eBUS adapters with the Ethernet module, so it seems to be an issue with the usr-es1 module itself.
The problem is that randomly the Ethernet network stops functioning. The module still shows LEDs, and the switch sees that the link is active, but despite this, I cannot connect to the adapter. The Wi-Fi connection works, but due to stability, I do not want to use Wi-Fi.

The option that works on my adapter is to restart the Ethernet module when it loses connection using:

on eth 0 "after 0 \"eth -o\"" 
on eth 0 "after --millis=500 0 eth -t" 
on eth 0 "after 1 \"eth -u\""

Unfortunately, after entering such events and triggers, the configuration disappears after restarting the dongle. It would be good to have the possibility of persisting a startup script where additional scripts could be executed on the device startup.

The next thing is, that there is a problem with passing commands with params to command "on" and "after", there is no way to nest quotes in such statements

[john30]

this feature is already on my todo list. anyway, it might be useful to add such a reset/restart option anyway

[komw]

@john30 Any progress on that? For me, the newest dongle is currently totally unusable. Sometimes it takes a few hours to reset the connection, but sometimes every 3–5 minutes the Ethernet stops working. Today I replaced the Ethernet cable on the Ebus dongle. Currently it's connected via a Cat7 Ethernet cable to my MikroTik switch, but it's still constantly disconnecting from the Ethernet.

[john30]

then you certainly have other issues and this feature wouldn't even help if it is "constantly disconnecting" as you say @komw (not sure what interval that means). I guess the Ethernet module is broken. did you try another one already?

[komw]

This is not the fault of the Ethernet module because I checked two and they behave identically. At the moment, I wrote a script that, when it detects that the Ethernet has stopped working (not responding to ping), sends commands via Wi-Fi to turn off and then turn on the Ethernet again.
It would be great if there was an option to force a module reset when the ethernet is disconnected.

[john30]

I've started a long-term test for one of my devices with an USR-ES1 on it and it didn't have any issue since 2 weeks, so I'm pretty sure your module is broken or you don't have a power supply that is sufficient/stable enough since the USR consumes quite some

[komw]

I would like to disagree with you. Let me explain why. Firstly, about 2 weeks ago I ordered another USR-ES1 -> it behaves exactly the same as the previous one. It means that I checked three different USR-es1 modules and each behaves the same way. Secondly, regarding the power source. I am currently using a power supply that provides about 20W. I have tried entirely different power supplies (about 4 different). I even thought it might be some interference in the power supply (the power supply and the heater are on the same outlet), so I also tried using the ebus module on a power bank -> zero difference, the problem occurs the same way. The only thing that surprises me is that sometimes the module can work for many hours without any issues, and then it starts disconnecting every few minutes, for example.

Today I will try to run the module without the heater connected, because there might be an issue with the ebus itself affecting the module's operation.

Maybe I can enable some debugging, etc., and send you the logs for you to see what exactly is happening?

[komw]

Okay, I checked with the ebus cable disconnected, and unfortunately, the same problem persists. After some time, the Ethernet connection gets disconnected. I’m afraid there might be an issue at the ebus adapter -> Mikrotik switch interface, and it seems like restarts are unavoidable here. I rule out a problem with the cable, as the module is connected with a shielded cat 7 cable about 20m long. Other devices plugged into the same cable do not cause any issues.