Works the same as in Chrome 69, everything is ok. Probably local caching issue, could you please try to clear the browser cache?
New Domoticz Events design
Moderator: leecollings
-
- Posts: 59
- Joined: Saturday 14 January 2017 21:37
- Target OS: Linux
- Domoticz version: Beta
- Location: Ukraine
- Contact:
-
- Posts: 38
- Joined: Monday 12 February 2018 12:56
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Contact:
Re: New Domoticz Events design
Works and looks good. ThanksStasDemydiuk wrote: ↑Saturday 27 October 2018 17:23Works the same as in Chrome 69, everything is ok. Probably local caching issue, could you please try to clear the browser cache?
- bizziebis
- Posts: 182
- Joined: Saturday 19 October 2013 14:00
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.8805
- Location: The Netherlands
- Contact:
Re: New Domoticz Events design
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.
-
- Posts: 59
- Joined: Saturday 14 January 2017 21:37
- Target OS: Linux
- Domoticz version: Beta
- Location: Ukraine
- Contact:
- bizziebis
- Posts: 182
- Joined: Saturday 19 October 2013 14:00
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.8805
- Location: The Netherlands
- Contact:
Re: New Domoticz Events design
When you are editing a LUA script, you can press CTRL+,
That will open up the settings for the Ace Editor.
That will open up the settings for the Ace Editor.
Re: New Domoticz Events design
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.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.
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.
-
- Posts: 12
- Joined: Saturday 22 April 2017 13:47
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: New Domoticz Events design
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?
-
- Posts: 1601
- Joined: Friday 18 October 2013 23:33
- Target OS: Raspberry Pi / ODroid
- Domoticz version: BETA
- Location: Arnhem/Nijmegen Nederland
- Contact:
Re: New Domoticz Events design
MMMharolds 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?
I mis this option also...?
Is there perhaps someone that make a case on github for this??
Xu4: Beta Extreme antenna RFXcomE,WU Fi Ping ip P1 Gen5 PVOutput Harmony HUE SolarmanPv OTG Winddelen Alive ESP Buienradar MySensors WOL Winddelen counting RPi: Beta SMAspot RFlinkTest Domoticz ...Different backups
-
- Posts: 59
- Joined: Saturday 14 January 2017 21:37
- Target OS: Linux
- Domoticz version: Beta
- Location: Ukraine
- Contact:
-
- Posts: 1601
- Joined: Friday 18 October 2013 23:33
- Target OS: Raspberry Pi / ODroid
- Domoticz version: BETA
- Location: Arnhem/Nijmegen Nederland
- Contact:
Re: New Domoticz Events design
There was a option to change into the lua blockley to: time,device, all, variabele, security, etc..StasDemydiuk wrote: ↑Saturday 03 November 2018 9:21Could you please explain how it was working in old editor?
The change was also possible when you did make the lua blockley.
Now you have to choose before you make a lua blockley
Xu4: Beta Extreme antenna RFXcomE,WU Fi Ping ip P1 Gen5 PVOutput Harmony HUE SolarmanPv OTG Winddelen Alive ESP Buienradar MySensors WOL Winddelen counting RPi: Beta SMAspot RFlinkTest Domoticz ...Different backups
-
- Posts: 1601
- Joined: Friday 18 October 2013 23:33
- Target OS: Raspberry Pi / ODroid
- Domoticz version: BETA
- Location: Arnhem/Nijmegen Nederland
- Contact:
Re: New Domoticz Events design
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
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
Xu4: Beta Extreme antenna RFXcomE,WU Fi Ping ip P1 Gen5 PVOutput Harmony HUE SolarmanPv OTG Winddelen Alive ESP Buienradar MySensors WOL Winddelen counting RPi: Beta SMAspot RFlinkTest Domoticz ...Different backups
-
- Posts: 59
- Joined: Saturday 14 January 2017 21:37
- Target OS: Linux
- Domoticz version: Beta
- Location: Ukraine
- Contact:
Re: New Domoticz Events design
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
Will take a lookThere was a option to change into the lua blockley to: time,device, all, variabele, security, etc..
-
- Posts: 59
- Joined: Saturday 14 January 2017 21:37
- Target OS: Linux
- Domoticz version: Beta
- Location: Ukraine
- Contact:
Re: New Domoticz Events design
@Derik I was'n able to reproduce your issues both with old and with new events editor.
-
- Posts: 1601
- Joined: Friday 18 October 2013 23:33
- Target OS: Raspberry Pi / ODroid
- Domoticz version: BETA
- Location: Arnhem/Nijmegen Nederland
- Contact:
Re: New Domoticz Events design
MM you mean the old options like i say..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.
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..
Xu4: Beta Extreme antenna RFXcomE,WU Fi Ping ip P1 Gen5 PVOutput Harmony HUE SolarmanPv OTG Winddelen Alive ESP Buienradar MySensors WOL Winddelen counting RPi: Beta SMAspot RFlinkTest Domoticz ...Different backups
-
- Posts: 59
- Joined: Saturday 14 January 2017 21:37
- Target OS: Linux
- Domoticz version: Beta
- Location: Ukraine
- Contact:
Re: New Domoticz Events design
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
In old one select box with event type active but as I see it does nothing, that's why it was removed in update
- Attachments
-
- blockly.PNG (6.73 KiB) Viewed 2747 times
- Brutus
- Posts: 249
- Joined: Friday 26 September 2014 9:33
- Target OS: Windows
- Domoticz version:
- Location: Netherlands
- Contact:
Re: New Domoticz Events design
+1
1x Intel NUC8i5BEK (Windows 10 x64) Domoticz on Virtualbox with DietPi.
1x Aeon Labs USB Z-Stick S2
1x P1 Smart Meter USB
28x Fibaro Modules
SMA Solar System
Daikin Airco / Heating
Denon DHT-S716H & DSW-1H
1x Aeon Labs USB Z-Stick S2
1x P1 Smart Meter USB
28x Fibaro Modules
SMA Solar System
Daikin Airco / Heating
Denon DHT-S716H & DSW-1H
- EdwinK
- Posts: 1820
- Joined: Sunday 22 January 2017 21:46
- Target OS: Raspberry Pi / ODroid
- Domoticz version: BETA
- Location: Rhoon
- Contact:
Re: New Domoticz Events design
I just now noticed that I can only see one of the events I have in Domoticz. All the others seems to have gone.
Running latest BETA on a Pi-3 | Toon® Thermostat (rooted) | Hue | Tuya | IKEA tradfri | Dashticz V3 on Lenovo Huawei Tablet | Conbee
-
- Posts: 59
- Joined: Saturday 14 January 2017 21:37
- Target OS: Linux
- Domoticz version: Beta
- Location: Ukraine
- Contact:
Re: New Domoticz Events design
Could you please explain what do you mean by "trigger mechanism". Currently I don't understand what are you asking for.
-
- Posts: 14
- Joined: Thursday 24 November 2016 12:14
- Target OS: Linux
- Domoticz version:
- Contact:
Re: New Domoticz Events design
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
Who is online
Users browsing this forum: No registered users and 0 guests