Never tried this, but could you perhaps use a virtual switch and use light.switchOn().forMin(5) to turn it on for a few minutes and use that virtual switch as trigger device so you 'catch' it again after 5 minutes when it goes off, and then do the calculations you want...?

My scripts use a lot of info I put in global_data. That file looks a bit like this: return { -- global persistent data data = { OWMForecast = {}, kelvinBuiten = {}, hueScenes = {}, sceneWoonkamerStatus = { initial = 'Auto' } }, helpers = { -- SYSTEEM idxNachtstand = 153, -- KAMERS -- woonkamer ...

Depends on how you installed it, I believe. I don’t know much about Docker, I found out that this works for me, if I change
to
but don’t ask me why

It was released about an hour later. The problem is solved, I only had to delete all the new devices.

https://github.com/zwave-js/zwave-js-ui ... elease.yml

Yep, I missed that. And he fixed it indeed very quickly. I'm waiting for the docker image to get to 8.0.2 and then I'll update again.

I updated my zwavejs2mqtt version 7.0.1 to the latest version 8.0.1. Big surprise, it is no longer called zwavejs2mqtt but zwave-js-ui. I did not know this. Zwavejs2mqtt used it own name as part of the unique identifier. Zwave-js-ui does this too. So EVERY DEVICE is rediscovered by Domoticz, because ...

Those are the numbers Domoticz reads from my TKB TZ-69E smart energy plug in . domoticz.devices(idxVerbruikWasmachine).WhTotal Oh hold on... WhTotal. Not kWh... Kilo... Kilo = 1000... The fog starts to clear up ;) So / 1000 will give me kWh from Wh! MachineUsed = (domoticz.data.MachineEndkWh ...

I used the script here in the forum to read values from my device. it needed some tweaking to make it work for me, but it works now. Almost. I just can't figure out the last step, the actual costs. After all is done, I have these numbers after a washing cycle: Start kWh = 39599 End kWh = 39975 Used ...

[*] I also have Fibaro smoke detectors these are recognized and added by MQTT discovery but there are only two devices added for each detector. - Air Temperature - battery_islow But in OZW I had several more, like heat switch, housing switch, fire alarm, etc. Especially the last one is quite ...

After discovering that my ceiling fan with TUYA can't be added to Domoticz, I accidentally stumbled upon this post. Tried my remote and I'll be damned! My 433 picks it up
Thanks for posting!

Hi there, I recently bought my first Tuya-driven product and I am trying to integrate it in Domoticz. It doesnt use the Tuya, Smart or Jinvoo app though, but they have their own app ('create'). I tried my login credentials with every setting anyway, but no luck. 2022-08-09 15:39:39.353 Error: TUYA ...

Sorry, I somehow missed the question... So with a bit of a delay: yes, the script changes the names of the virtual devices every hour. Something like this: forecast_temp_6h_deviceName = 'Temperatuur om ' .. os.date("%H", OWMMain.hourly[6].dt) .. ':' .. os.date("%M", OWMMain.hourly[6].dt) .. ' uur ...

I was hoping to present a nice clean script with fabulous options, but it takes me much longer than expected and there is so much to do and the weather is nice and ... Anyway, the core is this (this is just a test script, you will have to change it to make it work for you): return { on = { devices ...

Doh.

Changing hueScenesDz_hueId into a script level persistent variable seemed to work. I should have realized this sooner. Anyway... Onward!

I kind of dreaded this moment, because my skills suck, but my ambitions are huge. I am the Dr Frankenstein of scripting; I cut parts from things I think I can use and stitch stuff together with my basic knowledge, google and a lot of trial and error. So behold my monster: --[[ Purpose of the script ...

Right at the beginning of my script, I declare my table: execute = function( domoticz , triggerItem ) local myTable_devId = {} I have a function that adds values to the table, like: hueScenesDz_hueId[i] = {} myTable_devId[i].action = myUrl myTable_devId[i].name = theName Other functions want to use ...

TO get that to work, you would need to add all the devices in that hardware to a group and use the group as a trigger. Mm, but I would not know which device in the group caused the group-trigger, would I? Anyway, I 'solved' it by add a prefix to the devices and using a wildcard in the device ...

Thanks,

It helped me out a bit. Your examples & trial and error Not defining the arrays was one of the problems.

I've created a separate hardwareId for a dynamic collection of virtual switches. My script creates the switches when it needs to. But it also has to act when the switch is triggered. I use myDeviceTriggers = domoticz.hardwareInfo(myHardwareId).idx and I get a table with all the right idx's. But ...

I've spent hours reading at lua.org, lua-users.org and numerous other sites, looked at a lot of examples here at the forum, but somehow I still don't understand tables. Perhaps it has to do with the fact that I learned myself programming some 40+ years ago when i was a kid. BASIC and Pascal and ...