R076 Rules Regression

[brycied00d]

Hello all,
I updated from R072 to R076 without any major hitches. Unfortunately I've noticed a regression in rule handling.

# Overall Setup
I have a number of Hue bulbs that are connected through the Hue hub to my Almond+. They show up on the LCD and web GUIs and I can control them normally from those places. (Both 72 and 76)
I have a z-wave door sensor. It correctly triggers when the door is opened and shut, and sends a notification. (Both 72 and 76)
I have a rule configured to turn the entryway light when the door opens. This rule is triggered by the door opening, sets the brightness levels and turns the lights on. This has worked great under 72 for several weeks.

Upon upgrading to 76, the lights are no longer triggered. The notification is still sent so I'm sure the Almond+ is seeing the door sensor triggered. I am still able to manually turn Hue lights on from the Almond+ (as mentioned above). However the rule seems not to fire, or if it does then it's not turning the lights on.

So far I've "refreshed" the Hue bulbs from the LCD GUI, toggled active/inactive on the rules, as well as re-setting the rules. I've not done anything truly destructive (reset to factory defaults and reconfigure) in case there's any other useful information I can provide. (And because I really don't feel like reconfiguring everything again, to be blunt.)

Nothing is added to the the system or kernel logs when I open the door.
On the device itself, /tmp/rulesEngine.log seems to indicate the rules were fired.

Code: [Select]

[2015-5-28 15:20:18.657913163] {PRINT} Callback Received for Device 2,Index:1,Value:true
[2015-5-28 15:20:18.658158608] {PRINT} Msg Received for Device 2,index:1,Value:true,EventType:0,ruleslist size:2,bytes read:44
[2015-5-28 15:20:18.658329751] {PRINT} rulesEngine:device and index matched,cvalue:true,Avalue:true
[2015-5-28 15:20:18.658452080] {PRINT} Rule 1 executing for AND condition is success
[2015-5-28 15:20:18.658600022] {PRINT} setting Job after 300 seconds for Rule 1 Result 1
[2015-5-28 15:20:18.658750659] {PRINT} rulesEngine:device and index matched,cvalue:false,Avalue:true
[2015-5-28 15:20:18.658861287] {PRINT} All Rules Done

[2015-5-28 15:20:20.398043352] {PRINT} Callback Received for Device 2,Index:1,Value:false
[2015-5-28 15:20:20.398292210] {PRINT} Msg Received for Device 2,index:1,Value:false,EventType:0,ruleslist size:2,bytes read:44
[2015-5-28 15:20:20.398473747] {PRINT} rulesEngine:device and index matched,cvalue:true,Avalue:false
[2015-5-28 15:20:20.398621010] {PRINT} rulesEngine:device and index matched,cvalue:false,Avalue:false
[2015-5-28 15:20:20.398742306] {PRINT} Rule 2 executing for AND condition is success
[2015-5-28 15:20:20.398878008] {PRINT} setting Job after 60 seconds for Rule 2 Result 1
[2015-5-28 15:20:20.398988250] {PRINT} All Rules Done

[2015-5-28 15:21:20.486132077] {PRINT} runResult:Received job 2, result 1
[2015-5-28 15:21:20.486349608] {PRINT} runResult:Executing Rule 2 Result 1
[2015-5-28 15:21:20.488321524] {PRINT} runResult:setting Device 7 Index 1 to Value 0.
[2015-5-28 15:21:20.488512041] {PRINT} runResult:setting Job after 300 seconds for Rule 2 Result 2
[2015-5-28 15:21:20.488617997] {PRINT} runResult:Done with execution
[2015-5-28 15:25:19.182875732] {PRINT} runResult:Received job 1, result 1
[2015-5-28 15:25:19.183093363] {PRINT} runResult:Executing Rule 1 Result 1
[2015-5-28 15:25:19.185039506] {PRINT} runResult:setting Device 7 Index 1 to Value 51.
[2015-5-28 15:25:19.186933695] {PRINT} runResult:setting Device 6 Index 1 to Value 51.
[2015-5-28 15:25:19.188785510] {PRINT} runResult:setting Device 6 Index 2 to Value true.
[2015-5-28 15:25:19.190708220] {PRINT} runResult:setting Device 7 Index 2 to Value true.
[2015-5-28 15:25:19.190879643] {PRINT} runResult:Done with execution
[2015-5-28 15:26:21.262873877] {PRINT} runResult:Received job 2, result 2
[2015-5-28 15:26:21.263086781] {PRINT} runResult:Executing Rule 2 Result 2
[2015-5-28 15:26:21.265034284] {PRINT} runResult:setting Device 6 Index 2 to Value false.
[2015-5-28 15:26:21.265198527] {PRINT} runResult:Done with execution

/tmp/Hueserver.log and LastFailedHueServer.log both contain messages "{ERROR}    username is not present", however this doesn't seem to be "fatal" because I can use the GUI or LCD to turn on Hue's lights.

This is a screenshot of my rules at present (it's the best way I know of to "share" rules) https://dl.dropboxusercontent.com/u/3167967/screenshot_2015-05-28_15-18-10.png

Please let me know if there's anything I can do the help debug and resolve this.

[umar]

hi

have a hue bulb with zigbee door sensor too i will test and report later...

[Ohiomedic]

Not at home to try with my Hue bulbs, but it seems to be a bug with smart bulbs in this release. GE link, and Wemo bulbs are also having problems which they didn't before.