@Andyf66, I like your idea. I think it could be further simplified to something like: on = { devices = { 'Stairs Motion' } }, execute = function(dz) -- Must be the motion sensor... domoticz.runInMins(5, function(dz) -- Execute my 5 minute tasks ) domoticz.runInMins(10, function(dz) -- Execute my 10 ...

Yeah, I spoke too soon. When m_events is filled from the database for Blockly events, it just remembers a set of condition/action pairs and doesn't remember which Blockly each pair came from. For example, if I create this Blockly (call it A): 1. condition: temp < 25 action: ..... 2. condition: temp ...

It's a pretty simple change. There are four calls to parseBlocklyActions() in CEventSystem::EvaluateBlockly(). Change all four the same way:

Change: to:

Does anyone use timer plans for anything other than modes such as home, away, night, etc?

... however the move from openhab 1 to 2 made everything more complex instead of making it more user friendly.

I'm curious about this. Can you give a few examples?

I would like to get feedback from users of the passcode feature on a proposed change. Let's say you were able to configure a user's access to devices individually. For example, you could create a user with "User" permissions, but give the user only "Viewer" access to certain switches (and "User ...

There are actually many more setup options on the normal device pages than there are in device setup. The device pages have edit settings (depending on device type, there are a lot of options in here), timers, and notifications. The device setup page has toggle used/unused, rename, and delete. In ...

I'm currently working on extensive refactoring and usability improvements to Domoticz, and I will be starting discussions about a variety of topics to help guide the changes I'm making. First question is for users with zwave devices with a clock (only example I know of is thermostats). Domoticz ...