Domoticz

QSKONE wrote: ↑Saturday 27 October 2018 16:53 In Chrome 70. Events are broken

Works the same as in Chrome 69, everything is ok. Probably local caching issue, could you please try to clear the browser cache?

StasDemydiuk wrote: ↑Saturday 27 October 2018 17:23

QSKONE wrote: ↑Saturday 27 October 2018 16:53 In Chrome 70. Events are broken

Works the same as in Chrome 69, everything is ok. Probably local caching issue, could you please try to clear the browser cache?

Works and looks good. Thanks

I'm missing the option to save the editor settings once they are changed. I like to set a dark theme. With the previous version it would save those settings along with the save of the event. Now they keep on reverting to default.

bizziebis wrote: ↑Saturday 27 October 2018 23:01 I'm missing the option to save the editor settings once they are changed

What editor settings do you mean, didn't found the ability to update them

When you are editing a LUA script, you can press CTRL+,
That will open up the settings for the Ace Editor.

thelbekk wrote: ↑Friday 26 October 2018 13:00 Not exactly an editor issue, but I notice that Blockly "scripts" may be enabled and disabled, and the system does what you expect, but dzvents scripts, once created, are forever active: you can disable them, even delete them, but they keep on working -- even after a restart.

Actually, it's much more subtle than that, and the reason I saw the problem was that I *didn't* have any internally generated scripts in place already.

I've tested using timer triggered scripts, of all three internal types (blockly, lua, and dzvents). The dzvents case is special, in that it has a "generated_scripts" directory, where active scripts are kept, next to the "scripts" directory for manually added ones. If I understand correctly, activating an internally generated dzvents script is done by writing it to the generated_scripts directory, and, conversely, deactivating is done by removing it from that directory.

It turns out that if you have only one script active, and it's a dzvents script, then it will not get removed from generated_scripts when you deactivate it. You must have another lua or dzvents script active for the disabling to work properly. (A blockly script will not do it.) Activating another lua or dzvents script after deactivating that final dzvents script will make the deactivation "take".

In other words, as long as you have at least one internally generated lua or dzvents script still active, you're not going to see this bug.

I like the new editor but I'm missing the option to specify the trigger mechanism (time/device) for blockly's. So now all my blockly's are not triggered anymore. Or am I missing something? Maybe the naming of blockly's is important not to indicate the triggering?

harolds wrote: ↑Wednesday 31 October 2018 20:47 I like the new editor but I'm missing the option to specify the trigger mechanism (time/device) for blockly's. So now all my blockly's are not triggered anymore. Or am I missing something? Maybe the naming of blockly's is important not to indicate the triggering?

MMM
I mis this option also...?
Is there perhaps someone that make a case on github for this??

harolds wrote: ↑Wednesday 31 October 2018 20:47 I'm missing the option to specify the trigger mechanism (time/device) for blockly's. So now all my blockly's are not triggered anymore.

Could you please explain how it was working in old editor?

StasDemydiuk wrote: ↑Saturday 03 November 2018 9:21

harolds wrote: ↑Wednesday 31 October 2018 20:47 I'm missing the option to specify the trigger mechanism (time/device) for blockly's. So now all my blockly's are not triggered anymore.

Could you please explain how it was working in old editor?

There was a option to change into the lua blockley to: time,device, all, variabele, security, etc..
The change was also possible when you did make the lua blockley.
Now you have to choose before you make a lua blockley

Dear developers...

Please make the old setting work again..
And also make the missing device option work..
When there was a missing device in a event, the text color changed to purple..
Now there is no different between a working and a not working [ with a missing device ] event

I'm missing the option to specify the trigger mechanism (time/device) for blockly's.

When there was a missing device in a event, the text color changed to purple..
Now there is no different between a working and a not working [ with a missing device ] event

There was a option to change into the lua blockley to: time,device, all, variabele, security, etc..

Will take a look

@Derik I was'n able to reproduce your issues both with old and with new events editor.

StasDemydiuk wrote: ↑Saturday 10 November 2018 9:39 @Derik I was'n able to reproduce your issues both with old and with new events editor.

MM you mean the old options like i say..

Perhaps in a/the stable version you can see the old options.
Only i do also not have a slave version running with a stable version..

I used 4.10073 for old event editor and 4.10164 for new one.
In old one select box with event type active but as I see it does nothing, that's why it was removed in update

bizziebis wrote: ↑Saturday 27 October 2018 23:01 I'm missing the option to save the editor settings once they are changed. I like to set a dark theme. With the previous version it would save those settings along with the save of the event. Now they keep on reverting to default.

+1

I just now noticed that I can only see one of the events I have in Domoticz. All the others seems to have gone.

harolds wrote: ↑Wednesday 31 October 2018 20:47 I like the new editor but I'm missing the option to specify the trigger mechanism (time/device)

+1

ak97 wrote: ↑Sunday 06 January 2019 7:48

harolds wrote: ↑Wednesday 31 October 2018 20:47 I like the new editor but I'm missing the option to specify the trigger mechanism (time/device)

+1

Could you please explain what do you mean by "trigger mechanism". Currently I don't understand what are you asking for.

https://www.domoticz.com/wiki/Events

Event Type. Controls what events events will cause Domoticz to execute the script. Drop down values:
All - Will run whenever anything happens that triggers the event system to run a script
Device - Will run whenever ANY device state/value change
Security - Will run whenever there is a security event
Time - Will run once per minute. Scripts are executed one at a time.
User Variable - Will run when User Variables are updated