I have a few managed counters to calculate my GAS and Energy. But they stopped updating the counters when I updated from 2022.2 to 2023.2. return { on = { -- timer = { 'every hour' } timer = { 'every 5 minutes' } -- timer = { 'every minute' } }, --[[logging = { level = domoticz.LOG_DEBUG, marker ...

I've found the new RMN app and did some certificate unpinning with frida and http toolkit. The new URL is for an adress in IJsselstein for example: 3402ta 17 https://europe-west3-burgerportaal-production.cloudfunctions.net/exposed/organisations/138204213564933597/address/206321157929710806/calendar ...

Got the dzVents code solved. Now I have a new hurdle. Before Domoticz starts I have to set the GPIO pins to the correct mode. When I change the behavior of the GPIO ports; the port is active / high and can't be changed instantly (after 200 milliseconds I can make a change). Even when I set it to low ...

Thanks; this works like a charm. Why I haven't tought about that myself. dzVents code is solved. Now I have to find out why the LED flashes for a while when I enable the GPIO ports. This is done prior to loading Domoticz, with the following: sudo echo 17 > /sys/class/gpio/export ; sleep 0.2; sudo ...

Here is an update to my current script. I am able to turn it off for .150 milliseconds, after the switchOn and it appears to only press the button once. But how can I use this in a switchselector or have its state show the right value if I am unable to use it as a simple button. So the bold code ...

I have 2 remotes which I want to control from my Pi3 with Domoticz. The problem is that I need to simulate a press once instead of continous, to overcome strange behaviour. Therefore I need a maximum trigger of 200 milliseconds approximately. Is this possible with a Pi and what do I need to do? I ...

Have a look at this

https://www.domoticz.com/forum/viewtopi ... 73#p226190

Thanks as always waaren and happy Christmas!

Damn; I thought I had solved my problem. But it still doesn't work exactly. I must be doing something wrong with the persistent data. Could someone have a look. --[[ wii charger if last seen more than 5 days ago, then turn on for 1 hour. If wii is turned off; then turn on for 2 hours. wii heet Wii ...

Well; as you have already found. The randomised duration is within! There is: withinMin(minutes); this enables to switch off or on within a random time. But I guess it might influence too much with your current idea. If you have: dz.devices(15).switchOn().withinMin(15) dz.devices(15).switchOff ...

Are you sure you show us the same script that produced this error? Line 29 of this script cannot have this error because line 29 does not contain code that concatenates anything. (local wiion = false -- is not a concatenation) You also commented the declaration of the wii as domoticz.devices(62)in ...

Have an update question about this code. I have too many false charges due to the sonoff which sends it's status. Therefore I modified my script to check whether a boolean has been set --[[ wii charger if last seen more than 5 days ago, then turn on for 1 hour. If wii is turned off; then turn on for ...

Great; that works, I had to play with the timeout and changed it to 150 though. Now I get it; while looking at the Availability this is only applicable for afterXXX. Next problem however is that it doesn't work inside a switchselector with GPIOx.switchOn() and direcly underneath the GPIOx.switchOff ...

Is it possible to trigger a hardware (sysfs GPIO) connected remote control only for a short period of time. I now have added the sysfs underneath hardware and get the exposed ports that I have configured as a regular on/off switch. I only managed to switch off the device after 1 sec in the GUI ...

I'm using this theme/skin for some time now; but I experience two strange things. The first is the CPU usage on my rPi3 stays above 1.2 while one of my browsers is on the domoticz page. Is there some way to disable this? Secondly; I have never seen the configuration menu although I'm on the latest ...

Hi all, I'm trying to get this function to work; but it doesn't trigger due to some logic problem or other error. Someone who could help me out with this. When I change the timer to every minute and turn on debug I only get the following information. Status: dzVents: Info: Nintendo: ------ Start ...

Great; the script works as expected and I have learned a bit more. I have changed some triggers and disabled some commands to not actually trigger the alarm; but still sending the Z-wave commands. But totally missed the nuance between these two calls: dz.openURL(baseURL .. strobe) triggerJSON ...

Okay; had some time to look at the script again and made some modifications. Furthermore I have commented it a bit inside the code. The script should be triggered only when the dummy switch (local alarmStatus = dz.devices('ALARMSTATUS')) is active. Furthermore the alarm (local alarmState = dz ...

2019-06-14 10:20:00.554 Status: dzVents: Info: wii charger: ------ Start external script: wii.lua:, trigger: at 10:20 2019-06-14 10:20:00.579 Status: dzVents: Debug: wii charger: Processing device-adapter for Wii-charger: Switch device adapter 2019-06-14 10:20:00.581 Status: dzVents: Debug: wii ...

--[[ wii charger if last seen more than 5 days ago, then turn on for 1 hour. If wii is turned off; then turn on for 2 hours. wii heet Wii en heeft IDX: 62 wii charger heet Wii-charger en heeft IDX: 63 --]] return { on = { timer = { 'at 00:58' }, -- wii heet Wii en heeft IDX: 62 devices = { 'Wii ...