It was a simple back up (which was made while the VM was running). I can't find the shutdown-before-backup option though.

I had to restore my Domoticz VM this week and a simple restore of the VM was not enough to bring up a working system, I had to reboot the whole node (Intel Nuc). This was repeatable so maybe related to what PierreT is saying.

Ultimately it still worked though, just something to bear in mind.

Glad you got it sorted and thanks for tolerating MY ineptitude also.

This version should only turn the pump on every 4 hours if conditions are met. It will turn off as soon as condition are not met. return { on = { devices = { 'Switch1', 'Switch2', 'Switch3', 'Switch4', }, timer = { 'every 4 hours', }, }, execute = function(domoticz, item) local dz = domoticz local ...

Isn't that what you require or is there something more complex I have misunderstood ?

Ah yes, both true although I don't understand What if: 1. script was triggered by sw2-sw3 (status On) at 03:58 2. next script running is by timer at 04:00 - it will turn pump off because of state sw2-sw3 (see the point 1) So the next cycles pump will be turned off everytime. The pump should not ...

FredZ wrote: ↑Wednesday 22 January 2025 8:32 Hopefully this will clarify what I am attempting to do.

You mentioned a 4 hour timer in a previous post, is that not needed ? I left a 4 hour trigger in that script anyway but you can delete it if you don't need it.

Much much easier now I know the application. I also run 1 borehole pump, 1 well pump and 1 pool pump all integrated into Domoticz. This could work return { on = { devices = { 'Switch1', 'Switch2', 'Switch3', }, timer = { 'every 4 hours', }, }, execute = function(domoticz, item) local dz = domoticz ...

If switch2 is on then do nothing (this is a failsafe switch and is normally off. If for any reason switch2 is turned on Could you clarify this, it seems do be 2 outcomes for 'On' but I'm not sure what conditions are required. Anyway, you could give this a try. I've added logging, perhaps too much ...

119 dzVents scripts(828kb), in the dB (35mB) , 864 used devices(1419 total). Slowed down a bit my old rpi3b but sits at 10-20% cpu these days with about 400mb memory use. I make sure to turn on full logging on occasion to check for loops and race conditions. I use monitorix to check overall status ...

because it is not programming. It might not be good cleaned up code but a starting point for someone asking for help. Bar the "e" error it would most likely function. Sometimes it is easy to see why people don't ask for assistance here. Perhaps some constructive criticism would might even make you ...

Kedi wrote: ↑Monday 20 January 2025 15:46
The rest I did not test, but it seems to me that the test with the capital 'E' in

Code: Select all

if chatter == 'Every 4 hours'

will never met the condition.

Well spotted. Anything more to add to help the OP ?

No it's not from chatgpt. Just my basic starting point. What made you think it was from chatgpt ?

Here's how I would start with this return { on = { devices = { 'Switch1', 'Switch2', 'Switch3', 'Switch4', }, timer = { 'every 4 hours', }, variables = {}, scenes = {}, groups = {}, security = {}, httpResponses = {}, shellCommandResponses = {}, customEvents = {}, system = {}, }, data = {}, logging ...

@solarboy is it possible to install Domoticz on Proxmox?? I'm thinking about exiting the Raspberry 3B+ and running it on the Dell Wyse 5070 terminal, but I don't know if it makes sense, but I'll definitely have more DPI image outputs or USB ports. I installed Ubuntu server and then Domoticz on that ...

It's great to hear that Domoticz is here to stay! I recently gave Home Assistant (HA) a brief try, but I found it quite limiting when it came to scripting. In contrast, dzVents is fantastic. I agree that the Domoticz interface looks a bit dated, but since I'm the primary user, it doesn't bother me ...

Using SMA here which isn't a micro inverter system but is cloud free using the sma modbus plugin and smahub (sma2mqtt). You can also use sbfspot with cloud upload disabled. Working well so far and the hardware is very high quality. I shall be adding a Sunny Island + Pylontech LifePo soon.

jberinga wrote: ↑Saturday 04 January 2025 11:59 Isn't this the same issue as desriped in this topic: viewtopic.php?p=321073#p321073?

Thanks for that. missed that discussion, reverting to 9.18.1 solved the issue.

With lastest Domoticz stable and zwavejsui 14.3.7 I can change the colour in zwavejsui with its colour picker but if I do so in Domoticz nothing happens although the command appears in the logs. 2025-01-03 18:41:47.459 Status: setcolbrightnessvalue: ID: 8b9, bri: 12, color: '{m: 4, RGB: 02ff10, CWWW ...

I managed to install it 2 weeks ago doing exactly what you did and have a working system, on an Ubuntu 64 server VM.