Like I said. The Temperature isn’t changing (unless you have logs that your haven’t posted showing the temp changing). All of the logs posted show the Temperature with the same value. Until the value changes the rule will not trigger. If you want it to trigger for every update, change the trigger to “received update”. Otherwise you need to wait for it to actually change temp to see the rule trigger.
Here I can show my temp changing, I am listening and understanding everything you are saying and appreciate your time. as you can imagine this is very frustrating for me too.
2015-12-08 20:43:11.619 [INFO ] [runtime.busevents ] - Temperature state updated to 24.2
2015-12-08 20:43:41.618 [INFO ] [runtime.busevents ] - Temperature state updated to 24.3
2015-12-08 20:43:49.134 [INFO ] [runtime.busevents ] - Luminance state updated to 0
2015-12-08 20:43:51.754 [INFO ] [runtime.busevents ] - Humidity state updated to 49
2015-12-08 20:44:11.634 [INFO ] [runtime.busevents ] - Temperature state updated to 24.2
2015-12-08 20:44:41.635 [INFO ] [runtime.busevents ] - Temperature state updated to 24.2
2015-12-08 20:44:49.151 [INFO ] [runtime.busevents ] - Luminance state updated to 0
2015-12-08 20:44:51.770 [INFO ] [runtime.busevents ] - Humidity state updated to 49
2015-12-08 20:44:57.549 [INFO ] [runtime.busevents ] - Battery state updated to 100
2015-12-08 20:45:11.631 [INFO ] [runtime.busevents ] - Temperature state updated to 24.2
2015-12-08 20:45:41.650 [INFO ] [runtime.busevents ] - Temperature state updated to 24.2
2015-12-08 20:45:49.166 [INFO ] [runtime.busevents ] - Luminance state updated to 0
2015-12-08 20:45:51.786 [INFO ] [runtime.busevents ] - Humidity state updated to 49
2015-12-08 20:46:11.646 [INFO ] [runtime.busevents ] - Temperature state updated to 24.3
2015-12-08 20:46:41.666 [INFO ] [runtime.busevents ] - Temperature state updated to 24.2
2015-12-08 20:46:43.196 [INFO ] [c.internal.ModelRepositoryImpl] - Refreshing model 'default.rules'
2015-12-08 20:46:49.183 [INFO ] [runtime.busevents ] - Luminance state updated to 0
2015-12-08 20:46:51.803 [INFO ] [runtime.busevents ] - Humidity state updated to 49
2015-12-08 20:46:57.581 [INFO ] [runtime.busevents ] - Battery state updated to 100
2015-12-08 20:47:11.663 [INFO ] [runtime.busevents ] - Temperature state updated to 24.2
2015-12-08 20:47:41.685 [INFO ] [runtime.busevents ] - Temperature state updated to 24.3
2015-12-08 20:47:49.199 [INFO ] [runtime.busevents ] - Luminance state updated to 0
2015-12-08 20:47:51.818 [INFO ] [runtime.busevents ] - Humidity state updated to 49
2015-12-08 20:48:11.679 [INFO ] [runtime.busevents ] - Temperature state updated to 24.2
2015-12-08 20:48:41.679 [INFO ] [runtime.busevents ] - Temperature state updated to 24.2I can only see what you provide and make assumptions from there.
I see no reason the rule does not trigger. Have you tried “received update” to see if it triggers then?
@rlkoshak Yes I have tried this no luck , could you show me your items and your rules file for zwave?
Many Thanks
All I have are simple switches:
Switch S_L_Front "Front Room Lamp" <light> (gLights, gOffTimerLights, gWeatherLights, gMorningLights) {zwave="3:command=switch_binary"}
Switch S_L_Family "Family Room Lamp" <light> (gLights, gOffTimerLights, gWeatherLights) {zwave="4:command=switch_binary"}
Switch S_L_Porch "Front Porch" <light> (gLights, gOffTimerLights, gSunsetTimerLights) {zwave="6:command=switch_binary"}
But your Items are working correctly as they are being updated on the bus.
Look for typos between your Items file and your rules file.
Load your config into Designer and look for red underlined words. Those indicate a syntax error. Its a great way to find typos.
@rlkoshak I think I know what the problem was (although I have not tested it)
So I loaded the designer over the rules file and I was complaining about my comments for a rule (See below) I had coded above the temperature rule.
I realised that I was using *** rather than //****
Maybe this is the error that stopped my temperature rule from triggering. Let’s see this evening. (Fingers crossed)
You can see the erroneous rule below.
***************************************************************************************************************
* Its evening so set global variable
***************************************************************************************************************
rule "Its the evening"
when
Time cron 0 0 19 1/1 * ? *
then
// Set global variable to 1
itsEvening = 1;
end
**> Damn this formatting - appologies
I’ve been fighting with it too. Something changed a couple days ago and now I can’t get it to format code in these postings reliable either.
Indeed without the “//” that could cause some problems. I would have expected to see some errors in the logs when it loaded the files but maybe it just failed silently.
The thing is I am programmer by trade and the language I use allows comments without //*.
Its easy to slip up in this way.
Also being a relative beginner you always seem to think that the problem is much bigger that this.
Thanks for your time, patience, and attention to my problem. They say software is only as good as its community. You are credit to this community.
Thank you.
No problem. I hope that is the problem.