Domoticz

I have an event that should trigger after 20:00 and it was working well when I noticed some days after it started running also in the mornings. I checked the blocky event and it was ok. To be sure what was going on I deleted the event but I realized the trigger was still working, without event. I put the service down "sudo service domoticz stop" but the trigger still works.

Did anyone have this same behaviour with the events? I really don´t know what to do.

Sure you do not have a second domoticz instance running? If domoticz is down (service stopped) everything is stopped.

Using "top" command I didn´t see any other domoticz instance running. Is there another way to check it?

dlgoes wrote: ↑Monday 06 November 2017 21:26 Using "top" command I didn´t see any other domoticz instance running. Is there another way to check it?

ps -ef | grep domoticz

Tks for the help but the problem now is not in some instance running. I formatted the sd card twice (in Mac and Windows erasing data) and installed again Ubuntu Mate but before installing (while my raspberry pi 3 has just turning on) the trigger started again!!! So, I can see that is nothing related to domoticz server or running instances. I have some devices from Aeotec (z-stick, multisensor and a smart switch) and my multisensor is using my "old" blocky event to send a command to the smart switch through the z-stick but as I have formatted the sd card (erasing data) it should not be running anymore. Maybe I should have to reset the z-stick because is very weird what it happening. I really don´t have more ideas why this is happening. Is there a cache on z-stick?