Domoticz

So the doorbell is always on, as far as domoticz/your logic is concerned. This will happen based on your script:

- you press the doorbell, domoticz gets signal from bell.
- light switches on for 1 minute. After minute light switches off.
- Domoticz gets signal light off, and since doorbel status is always group on, the first rule applies again. You're in a loop now.

You can always disable the event in blockly, no need to reboot. But you will have to wait a minute since there will always still be a delayed event active.
It would be safer to edit the deurbel in switches, add a slave device called "deurbel alarm" as a normal on/off. That way deurbelalarm would only go to on if someone actually presses the deurbel. If you make a blockly action based on the deurbel alarm do something like:

if deurbel alarm = On do/set something, set deurbel alarm = Off

Hmmm that makes sense.

I did not know blocky updates once a minute. Good to know.

Your solution seems like the best way to go.
Thank you for your insight.

edit:
It seems I can assign a slave device to the doorbell, but when the doorbell is pressed the slave device stay's off.
I tried the AC and ARC switch types. Maybe this is simply not possible?

I created an event to check if my bedroom-temperature is bigger than the outside-temperature (so it's better to open the windows for some cooling down), but the event is spamming me every minute with the same advice (to test, I used < instead of >).

I changed < into > (so the event doesn't apply anymore), but it is still sending me messages. Then I tried do deactivate the rule, but the messages are still coming in. What to do?

I dont know if the weather underground temperatures work yet. The second one now probably evaluates to 0, making this true everytime the slaapkamer temp comes in. Buy a real one for outside in the mean time, I can confirm they work. It's probably not such a good idea to trigger events based on an external source anyway, what if they send 0 temp by accident all day?

- v1.933: Implemented: trigger url/api as Do command

Just playing with the security settings. Should this work? Because it isn.t

Did you update recently? I fixed this a few days ago.

Edit: the security status is not a device (yet) so it doesnt trigger blockly. Only if you combine it with another device or time constraint blockly will use it.

CopyCatz wrote:Only if you combine it with another device or time constraint blockly will use it.

Right, this works, thanks running 1.945

Dynamic wrote:I created an event to check if my bedroom-temperature is bigger than the outside-temperature (so it's better to open the windows for some cooling down), but the event is spamming me every minute with the same advice (to test, I used < instead of >).

I changed < into > (so the event doesn't apply anymore), but it is still sending me messages. Then I tried do deactivate the rule, but the messages are still coming in. What to do?

This also doens't work with my own sensors... I have the same problem with sensors I bought and installed. I also tried to swithc < to > and vice versa, but it keeps spamming me...

Hi CopyCatz,

Any idea why the event screen is not working over HTTPS?
http://www.domoticz.com/forum/viewtopic ... &t=68#p915

SweetPants wrote:Hi CopyCatz,
Any idea why the event screen is not working over HTTPS?
http://www.domoticz.com/forum/viewtopic ... &t=68#p915

SweetPants,

The event system is loading in an iframe, that does not work with reverse proxy at the moment. I don't think cross-posting your questions will solve this any earlier

I can use the events panel fine through https reverse proxy via nignx...

@CopyCatz, do you have a "add_header X-Frame-Options" in your nginx sites-available config?

Let's discuss this over here http://www.domoticz.com/forum/viewtopic.php?f=18&t=189because it is a nginx issue

SweetPants wrote:Hi CopyCatz,
Any idea why the event screen is not working over HTTPS?

See http://www.domoticz.com/forum/viewtopic ... p=993#p993

CopyCatz wrote:I can use the events panel fine through https reverse proxy via nignx...

I don't think cross-posting your questions will solve this any earlier

I'm sorry for cross-posting, but i did not know if this was a nginx or event system issue.

Followed pepijns advise and it is working now, thnx

fl1p wrote:

Dynamic wrote:I created an event to check if my bedroom-temperature is bigger than the outside-temperature (so it's better to open the windows for some cooling down), but the event is spamming me every minute with the same advice (to test, I used < instead of >).

I changed < into > (so the event doesn't apply anymore), but it is still sending me messages. Then I tried do deactivate the rule, but the messages are still coming in. What to do?

This also doens't work with my own sensors... I have the same problem with sensors I bought and installed. I also tried to swithc < to > and vice versa, but it keeps spamming me...

I tested this as well with my own sensors and I too am receiving emails by the minute. I guess that's how the notification system works in blocky?

If you just specify "send me a notification when temp > X" you will get a notification each time the device reports in. That is literally what you get with such a rule; couple it with another device like "if temp >x and fan = off set fan = on and send notification". Then the rule will trigger once because the fan is off, second time the fan is on.

I really want to keep blockly simple in the sense that it does what it says/you say. Use lua if you only want the notification once, put in a time constraint like my garage door example. I don't want to put hidden clauses in blockly that say "well only send this notification once" without it being very intuitive what is happening. When would be the next time to send one? Blockly = keep it simple, stupid, lua = advanced.

Totally agree with simple. The way it is working at the moment, for me, it is excellent. Great work and great philosophy. Thank you.

How about adding the ability to disable/enable events from within events?
That way you could do something like: "when temp > X --> send me a notification AND disable eventY (this event) event" and add another event which does "when temp < X --> enable eventY"
That way you don't need to rely on virtual devices, plus i think it would offload the events system a bit because it has less events to process.

So Invent Inception? An event in an event? I could play a wav that goes "noooooonnnn rien de rien" whenever the event in the event triggers so whe know at which level of conscience we are