
Then I tried strings:

But in both cases the temperature is apparently simultaneously above and below 25ºC!

Only thing I haven't tried yet is compare to another sensor, but that'd be silly!
Moderator: leecollings



Number should work. Suggest to first test without time and with just a logmessage. If that works add time condition and last step is to add message to notification subsystem.FearNaBoinne wrote: Sunday 07 July 2019 20:53 First I tried numbers:
Then I tried strings:
But in both cases the temperature is apparently simultaneously above and below 25ºC!
waaren wrote: Sunday 07 July 2019 21:18Number should work. Suggest to first test without time and with just a logmessage. If that works add time condition and last step is to add message to notification subsystem.FearNaBoinne wrote: Sunday 07 July 2019 20:53 First I tried numbers:
Then I tried strings:
But in both cases the temperature is apparently simultaneously above and below 25ºC!
Without the time I have to wait for it to change, which happens once a day at most, not a valid solution...Suggest to first test without time
Log or notification makes no difference.and with just a logmessage. If that works add time condition and last step is to add message to notification subsystem.
As you can see, the system *does* see the correct value (17, {{temperaturedevice[360]}}=="Max Today"), but comparing it to a value doesn't work.Number should work.
Just tested and with a differently placed time condition the Blockly solution works.FearNaBoinne wrote: Sunday 07 July 2019 22:52Without the time I have to wait for it to change, which happens once a day at most, not a valid solution...Suggest to first test without time
Code: Select all
2019-07-08 00:57:00.496 Status: Time > 00:50 and temperature < 60 -- Time triggered
2019-07-08 00:57:00.497 Status: 21.4;45;1
2019-07-08 00:57:38.411 (Aeotec Zwave stick) Temp + Humidity (Badkamer (Zwave)) -- device triggered
2019-07-08 00:57:38.696 Status: Time > 00:50 and temperature < 60
2019-07-08 00:57:38.696 Status: 21.4;45;1
2019-07-08 00:58:00.528 Status: Time > 00:50 and temperature < 60 -- time triggered
2019-07-08 00:58:00.528 Status: 21.4;45;1Fully agree but for some domoticz users without any previous programming experience, the learning curve for Lua / dzVents / PHP / Python might scare them a bit.I'll redid this in dzVents, because I really do not want to waste more time on this, when I can get this working in dzVents in 2-3 minutes!
I'll try this, just for testing, but the other way *should* work as well!waaren wrote: Monday 08 July 2019 1:07 Just tested and with a differently placed time condition the Blockly solution works.
tempcheck.png
Code: Select all
2019-07-08 00:57:00.496 Status: Time > 00:50 and temperature < 60 -- Time triggered 2019-07-08 00:57:00.497 Status: 21.4;45;1 2019-07-08 00:57:38.411 (Aeotec Zwave stick) Temp + Humidity (Badkamer (Zwave)) -- device triggered 2019-07-08 00:57:38.696 Status: Time > 00:50 and temperature < 60 2019-07-08 00:57:38.696 Status: 21.4;45;1 2019-07-08 00:58:00.528 Status: Time > 00:50 and temperature < 60 -- time triggered 2019-07-08 00:58:00.528 Status: 21.4;45;1
That's why I think it is a great concept, and why I keep trying it... mostly unsuccesfully...waaren wrote: Monday 08 July 2019 1:07Fully agree but for some domoticz users without any previous programming experience, the learning curve for Lua / dzVents / PHP / Python might scare them a bit.I'll redid this in dzVents, because I really do not want to waste more time on this, when I can get this working in dzVents in 2-3 minutes!
Quick update: Yes, the other way works for me as well... But nested IFs should work as well, esp. as it reduces the number of tests*... It looks that's where it broke... It just executed everything inside the outer IF, without taking the inner IF in to consideration...FearNaBoinne wrote: Monday 08 July 2019 8:34 That's why I think it is a great concept, and why I keep trying it... mostly unsuccesfully...
This remark triggered my memory. There are quite a number of posts on this forum that nested if's in Blockly does not seem to work. If you search for nested Blockly in the search window, you will find >= 57 postsFearNaBoinne wrote: Monday 08 July 2019 8:41 ... But nested IFs should work as well, esp. as it reduces the number of tests*...
Sounds like a bug that needs to be fixed!waaren wrote: Monday 08 July 2019 11:41This remark triggered my memory. There are quite a number of posts on this forum that nested if's in Blockly does not seem to work. If you search for nested Blockly in the search window, you will find >= 57 postsFearNaBoinne wrote: Monday 08 July 2019 8:41 ... But nested IFs should work as well, esp. as it reduces the number of tests*...
True but for some reason I think this will not get to the top of the list of things that needs urgent fixing any time soon..
Users browsing this forum: No registered users and 1 guest