Here's the default script for LUA/Device (click on "+", right most on scripts tab): -- -- Domoticz passes information to scripts through a number of global tables -- -- device changed contains state and svalues for the device that changed. -- devicechanged['yourdevicename'] = state -- devicechanged ...

devicechanged is not a variable but a table, that may contain more than one value.

The right way to extract name and value of changing devices is :
[code
for deviceName,deviceValue in pairs(devicechanged) do
<<Use here deviceName and deviceValue>>
end
[/code]

If you're using "classical" LUA, then time elapsed since device's last update in seconds could be computed with: function lastSeen(device) timestamp = otherdevices_lastupdate[device] or device y, m, d, H, M, S = timestamp:match("(%d+)-(%d+)-(%d+) (%d+):(%d+):(%d+)") difference = os.difftime(os.time ...

You may perhaps (I didn't tested it) use multiple listeners, with "per_instance_settings = true". On one port, you may have a "classical (non TLS)" connection, used by tools that doesn't support TLS, and on the other a port for TLS connections. This way, you can connect you "TLS only" button. If you ...

There's an undocumented API,responding at http://<domoticz_ip>:<domoticz_port>/json.htm?idx=<deviceIdx>&type=lightlog
This may change at every new version, use it at your own risk.
IMHO, keeping changes in a persistent dzVents data, as suggested, is probably the best solution.

Personally, no, but you have only to solder 4 wires to an ESP8266, and plug the connector in A/C.

EAN 6970504212527 is clearly a ZigBee device. It should be managed by a Zigbee coordinator. Unless you have a bridge between ZigBee and 433 MHz (I never saw one, but this can even perhaps exist), there's no way to get it from RFlink. Could you send us a print screen of this device line into "Setup ...

Are you using a DJT11LM Aqara vibration sensor?
If not, what's the exact reference of you sensor?

What kind (reference) of aqara sensor do you have?

ZHA stands for ZigBee Home Automation. So protocol is ZigBee.

Rflink protocol is 433 (and sometimes 868) MHz. You may eventually add a NRFL01 to support MiLight protocol. But no ZigBee.

Some people don't like to much using external servers (like MelCloud) and do prefer having a direct, local control on AC, working without Internet access. Some, including me, are connecting an ESP8266 into CN105 AC connector (https://github.com/SwiCago/HeatPump), and use Domoticz plugin (https://www ...

Error code 500 means "Internal server error". Otherwise said, the remote server (here MelCloud) has a problem...
You may perhaps contact them to ensure they know there's a problem

What you can eventually do is a small Python code that read MQTT data of your hub, and publish to another topic last received data every 30 to 60 seconds. You can then read this topic, with less updates. Load of this small Python code will be small.

Should I make the script so that I read the values (reading from Shelly device via MQTT) for power, which seems to update more often, and then read and update the usage at that time? I guess the meter will use the actual time of update to do its calculations.. I don't understand why you want to ...

or

Did you tried using a P1 smart meter (energy)? It does it by default.

Was Domoticz alive at midnight?
Some daily routines are done at that time...

Is Totaal Zonnepanelen a kWh counter?

The "issue" you had is something common, happening when a cumulative counter goes back to zero (is reset) externally. Is probably occurred when you installed your second SMA inverter. Using "shift click" method, you'll only loose the 4 October production. If you have a way to known/estimate it, it's ...

I have a bit more with computers (since 1976, when PC didn't exist yet), leaning Linux at 50+ was not a big deal ...

In addition if you connect a screen to your RPi, you won't see a big difference with Windows...