Domoticz

Hello,

I just installed Domoticz (3.5877) on a Raspberry Pi 3. Using HUE, RFXCOM (also had some trouble with this device, don'y think it is related to my problem below, but maybe worth mentioning it).

Created some (simple) events which work on this version.
When I update to e.g. 6265, none of my events work anymore.

Am I overlooking something? Is there someone with similar problems or some help?

Thanks,
Ludwig Kempenaar

I have the same issue. All Blockly events won't run any more. All LUA events run fine.

I have also the same issue. Did a downgrade to the release version and all events working again.

Same problem here with blokly. It looks like it doesn't recognize the device changed status running version 3.6277. On another system running 3.6235 all is fine

Some devs did some modifications to the eventsystem, i will check it

ludwigkempenaar wrote:Hello,

I just installed Domoticz (3.5877) on a Raspberry Pi 3. Using HUE, RFXCOM (also had some trouble with this device, don'y think it is related to my problem below, but maybe worth mentioning it).

Created some (simple) events which work on this version.
When I update to e.g. 6265, none of my events work anymore.

Am I overlooking something? Is there someone with similar problems or some help?

Thanks,
Ludwig Kempenaar

Do post your simple event also please

It only happens when "Log 'event script triggers'" is disabled

I created a test blockly

if dummy_switch_1 is On
then dummy_switch_2 if on

and another

if dummy_switch_1 is Off
then dummy_switch_2 if off

and this works... and logging is enabled

Now testing with disabled logging

Now it does not work

So you people here have disabled this new option... okey, going to see where it goes wrong, the logging should be enabled by default bdw, hope thats true

Fixed... new beta is building (#6272+)

gizmocuz wrote:So you people here have disabled this new option... okey, going to see where it goes wrong, the logging should be enabled by default bdw, hope thats true

The menu is unclear If selected the events appear in the log if un-selected, the problem occurs and no events.

Thanks I will try!

Working again, thnx

SweetPants wrote:

gizmocuz wrote:So you people here have disabled this new option... okey, going to see where it goes wrong, the logging should be enabled by default bdw, hope thats true

The menu is unclear
logging.png
If selected the events appear in the log if un-selected, the problem occurs and no events.

I dont have this option: "Log event script triggers". But updating to the new version solved the problem with blockly.

BobbyNL wrote:I dont have this option: "Log event script triggers". But updating to the new version solved the problem with blockly.

That's weird because the problem was introduced when this option was implemented.

I´m having problems with both Blockly and Lua scripts and also time events..
Checked that the box is not set to inactive. (tried both options and it´s the same)

Upgraded to the new 3.5877 recently. Have been doing just fine for over 1 year or more but thought it was time to upgrade.
Bought at lot of new sensors at the same time, outlets and door sensors from nexa.

I have tried to implement an alarm with the security panel to send a notification when the panel is armed and door opens but nothing happens.
Have tried some simple LUA scripts and they dont work either..? Notifications set on switches works perfectly so its not that.

Even more strange is that my kitchen lights is set to start 20 minutes before sunset and turn of 20 min past sunrise, that have worked for 2 years perfectly. After the upgrade I got 6 more outlets and have set 2 of them to the same schedule. But both of them refuse to start ...? I have tried to set other starting times on them to but nothing happens? But the kitchen lights works perfectly.

I upgraded to the beta 3.6343 and still the same. Some blockly scripts seems to work but other don't ? Some time events work and some dont.
If nothing worked I would be less suprised. I did a backup of the database before upgrade, can there be some corruption in the DB.?
Should I try to do a clean install and add all sensors from scratch to get a new DB?