@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
@rob987 This is the most detail instruction regarding MQTT for new user. I highly recommend using his instruction. New user should check ma.log to check if data source is correct setup to read data from MQTT broker before working on data point.
I found the BACnet local devices menu in the Utilities section under "Admin Home". Here you can create or modify the local devices. Once you create a local device there, it is available in the add new data sources section
@cbyrne I think it is a side affect of why we implemented the 'Sets historical' feature. That is there to allow importing or generating large amounts of historical data which bypass the point-value event system. This prevents an overload of web socket messages and event detectors raising events.