@Jérôme-Girard if you're using a non root user you'll need to configure linux to allow non root users to use sub 1024 ports.
sudo sysctl net.ipv4.ip_unprivileged_port_start=502
sudo nano /etc/sysctl.conf
That should enable you to fire the publisher up on 502
@till There may be an option under system settings -. permissions -> alarms view permissions.
Try removing the user permission (every user inherits that by default from 3.7+)
Hopefully then, events can only be viewed by the respective users that have the correct permissions to view those datapoints...
@MaP Sorry for the late reply, for some reason I'm not receiving notifications...
Yes, thermal shutdown can definitely be a faulty fan. that and how the unit is stored.
They are usually the leading causes of the ES units failing (maybe IO as well?)
Get yourself a replacement if you can, they're usually around $5 USD mark...
A dead give away is the noise of the bearings in the fan itself.
Also how is the unit stored? is it in an open air case or is it sealed with an IP rated box that gets really muggy.
I do know the ED units are prone to overheating, but they have a guts load more kick than the GT's spineless raspberry pi 3
The best way around this is to provide us with a copy of raw output from the developer's console (ctrl + shift + i) element viewer and store it in code </> blocks for us to look at.
Given how you've presented it means there could be different types of formatting that needs to be "filtered" out in order to retrieve the correct variables you are looking for.
Assuming that the variables you have are exactly as we see them, here's the regex to get you started:
Just replace 1: with 2: and so on