If I fysically move the device from outside to my attic, I leave the device connected to the Zigbee network.
It does not drain the batteries that much and I replace those in the spring anyway when I put the device outside again.
I must say that my device works flawless for years now.

I use those moisture device and it works quite good. I get notifitied by Domoticz if moisture is below a certain level. I also use Lithium batteries and change those once a year. The Woox is very stable and water passing thrue is closed when there is no power from the battery. But I suppose that the ...

I think the failsafe is that when the power is off, the valve will be closed. (Did not check that) So when battery is depleted the valve will proberly be closed. There is also battery percentage send over the Zigbee network and send to Domoticz, so you could monitor that. Warning: when it is ...

I have more then one device with LQ below 75 and they all work perfect.
B.t.w. my Woox has LQ of 86 and also works perfect for years now. LQ also varies a little bit over time.
Just make sure that the batteries are OK.

You can do both. I have an Ikea E1743 bind to an Ikea IKEA ICPSHC24-30EU-IL-1 I do my normal switching and dimming (based on lux) via Domoticz and dzVents. But in the rare case that Domoticz crashes, you can at least turn the light(s) on to investigate why Domoticz crashed and put it back to work ...

@HvdW What does this 'stripped' script return? return { on = { devices = {'YourSwitch'}, }, execute = function(dz, Item) dz.log("whTotal " .. dz.devices('Laadpaal').whTotal, dz.LOG_INFO) dz.log("whToday " .. dz.devices('Laadpaal').whToday, dz.LOG_INFO) end }

I know, but generally speaking any application that has ID and Name labels uses the ID as primary look ups not the names I do not agree. Numbers are for computers and Names are for humans. The numbers are unique, so should the names be. If you use Google (dzga) You can call your lights, switches or ...

Why run through all changed variables, instead of

What happens to the error if you select something else then 'average' in the compare graph.

Why not create 2 dummy devices, which you can delete later on, and test what happens when you replace one by the other. So simple.

The content of %eventvalue1% should be 2 values separated by a ;
See https://wiki.domoticz.com/Domoticz_API/ ... d_counter)
The doc of espeasy writes that there should be a comma between SentToHTTP and the first parameter.

@waltervl was quicker.

Try I suppose %eventvalue1% is transleted to a value. B.t.w. what is that value? And is it a string?
Or should those comma's separate the values for the function?

I love it :D , but just a few remarks: 1. Personnal is incorrect, it should be personal with just 1 'n' 2. Personally I like the black background beter, perhaps that var could be transfered to the personal_settings.h file. So everybody could use its own personal background color more easily. 3. I ...

In https://www.lua.org/manual/5.1/manual.html you can see that the select statement is used for somewhat different.
What would be the benefit over "if then elseif end" method?

WOW, so that is what Claude.ai does? So complicated. I use my phone agenda for this.

If you put more that 1 service in 1 compose file, I always put some healthchecks and depends_on in those files.
You can have race conditions for starting up the different services.
Beter is to have separate compose files for each service, than you have at first manual control about the startup order.

Put /update after the 192.168.1.117 -> 192.168.1.117/update

Look in the 'corrupt' database at devices 2584 and 2592 and look for some data inconsistancy e.g. string or nil And I don't think the database is corrupt, but some of the data might be not consistant. I don't think device have a status 'deleted', so if the device is deleted you can't delete it 'for ...

NaN means Not a Number. So the database has not a number where the program expects one.
You can't just have the program delete records based on that error.

Domoticz uses a SQLite database. SQLite transactions are ACID. ( https://en.wikipedia.org/wiki/ACID ) So this could not have happened. " Somehow, deleting them was halfway interrupted " Cause must have been something else. B.T.W. you don't need to stop Domoticz to execute those 3 SQL commands. I ...