Blocky event stil active after deletion?

[Ron]

Is it possible that a blocky event is stil active/present if the event as been deleted?
At our place, the kitchen light sometimes go to on state while the presence sensor is off.
I replaced the Kaku (Klikaanklikuit/Coco) actor, with no result, the log shows that the licht is switched on from Domotics
but is not switched on by an active event.

I think it is possible that an old Blocky event is stil present somewhere, allthought i can't see it.
If that is thrue, in which directory or file are the Blocky events stored?

PS, update 11:50
It looks like the presence sensor is not always switching to OFF
This Aeon Labs Multi Sensor presence sensor is not always reliable on battery's, maybe is should replace it or put an adapter on it.
Tips are stil appreciated

Status kitchen light:

Knipsel.PNG (22.29 KiB) Viewed 1535 times

Status presence sensor:

Bewegingsmelder.PNG (24.03 KiB) Viewed 1535 times

Blocky event:

Event.PNG (31.78 KiB) Viewed 1535 times

In the event i used a Set Level 99% state on purpose.
If a Kaku dimmer switch is set to ON for a second time by the presence sensor in case the dimmer was already on
the lights start to dim from min-max-min-max just likt klikking two times on the actual switch.

[markjgabb]

hi ron...im dealing with a simlilar issue of blocky double running...did you by change rename your blocky at any point?

[Ron]

Yes, i did.
You can also see the unwanted on state is always 93% and not 99% as programmed in the active Blocky event.

[markjgabb]

ok so also linking my thread
https://www.domoticz.com/forum/viewtopi ... 62&t=18198
as i believe they are both the same issue....
have you rebooted your entire server since then?
i think its the only thing i havent done yet

[markjgabb]

ron: which version of domoticz are you using and on what platform?

[Ron]

Raspberry Pi, Domoticz version V2.3530
(haven't seen any updates after this one)

[markjgabb]

have now checked the DB file as much as i can with a text editor, unless its in the mutitudes of code i cant read in text, i cant find any reference to a second blocky instance running that could cause this issue going to update to 8072 to see if this resolves or not