device enabled/disabled

[giorgino]

please, does anyone know how it is possible for a device to disable itself after a while ?

I've many devices connected to an ESP32 that collect the sensor of my boat and publish via MQTT on a home assitant dashboard, all working good, but when I left the boat, after a while, this data (TASK 4) stop to publish; coming back to connect I find the device without the "enabled" flag

What's appened? Any idea?

[giorgino]

device list

[TD-er]

When the ESPEasy node detects lots of crashes during boot, ESPEasy starts to disable tasks one by one until it succeeds booting.

But you're running a build which is about 9 months old, so maybe try a newer build as it might be those issues are already fixed.

[giorgino]

It sounds strange...
when espeasy disable it, than all works good. So you mean that that task cause crash during boot? so that is the one that has some issue ?

[TD-er]

It is most likely....
But the only thing we can conclude is that the crash/boot loop was apparently resolved after the task was disabled during the last boot.

Sometimes just enabling the task will make it run perfectly fine, indicating it may be some issue when starting lots of tasks all at once. (e.g. memory allocation issues when starting lots of tasks at the same time).

But like I said, there have been quite a lot of fixes and improvements in the past 9 months, so perhaps it is already fixed in newer code.

[giorgino]

I should try to connect remotely (the "box" is onboard, faraway from home), via the router onboard.

is this the procedure? : static ip assigned (i.e. 192.168.1.85), portforward on the archer tplink gsm/lte router (internal 85, external 3384), configured the a dyndns.org on that router, connecting via browser "xxxyyyy.dyndns.or:3384"
any other setup in espeasy? pherhaps device allowed?

[TD-er]

Ehh port forward to open up the ESPEasy device to the internet?

Well the general consensus on this topic is: Nope! Don't make an ESPEasy device publicly accessible online.
You shouldn't do this with ANY IoT device, but especially not with devices that lack all kinds of post-1996 levels of security.

[giorgino]

Ehh port forward to open up the ESPEasy device to the internet?

yesssss, your right! , BUT I'm in a special "testing mode", with the device is 130 km far from home:
I write the code, at home, then in the weekend I upload on my sailboat, then - sometimes on the way back home - it starts to susped data transfer to the dashboard... very frustrating
so I have to wait an whole week to come back to the device to try to fix....., so I was planning to connect it to the web, just for a few time.... just to connect from home during the week

[TD-er]

Does this router support setting up a VPN to home?
If so, then it is all a lot more safe to use.

To access the web interface of ESPeasy, you only need to port-forward port 80, but I strongly advice against opening it from the internet.

[giorgino]

you only need to port-forward port 80,

sure is it enough? what about this settings:

Client IP filtering
Client IP block level: ALLOW LOCAL SUBNET

???

[TD-er]

If it is set to local subnet only, then that must be changed on the ESPEasy side too to accept all IPs.

But you can easily check this while being on location.
Setup your router + ESPEasy and then connect your phone to 4G (or 5G...) only so you must be on a different subnet.

[giorgino]

ok, there is another big problem: the wifi network is build with a tplink router 3G/4G/LTE and there is no public IP, or the address is not reachable from outside I don't know how.... also using the port forward and dyndns (or other service like it)

[TD-er]

Can this router setup a VPN to your own local network?
If so, then you may have a very convenient way of allowing access to your remote node and still keep it safe from online threats.

[giorgino]

Can this router setup a VPN to your own local network?

this is a bit out of my skills