after starting the system from fresh (originally on 3.1.0, but updated in my frustration to 3.2.0.M5), using an individual toggle switch in the OH interface to turn on (for example) the lawn watering would work as expected, and appear in the log as:ġ5:32:04.554 - Item 'waterVeggiesLawn' received command ONġ5:32:04.554 - Item 'waterVeggiesLawn' predicted to become ONġ5:32:04.556 - Item 'waterVeggiesLawn' changed from OFF to ONġ5:32:04.556 - Item 'gWateringStations' changed from OFF to ON through waterVeggiesLawnġ5:32:04.557 - Watering turned on - timer set for: 15 minutes. I have a separate rule to create a timer to turn the stations off a certain amount of time after they are turned on, but that was working fine. Item waterGardenBeds changed from ON to OFF Therefore, I had coded the following rule: rule "run front yard after running garden beds" The lawn and veggie beds station runs on different logic to the other two, but the other two I always want to run in sequence. I have three active stations on my OpenSprinkler - one that does a lawn and veggie beds, and two that do all the garden beds. 
However, in the hope of avoiding others having to follow in my footsteps, I hope posting this can be useful in fixing whatever is going on behind the scenes.
#Opensprinkler raspberry pi firmware how to
However, I think I’ve figured out what was causing it - or at least how to cause it to misbehave and therefore how to avoid triggering the misbehaviour. I was tearing my hair out for a while this afternoon, because I had coded something that should have been super-simple, and suddenly my OpenSprinkler binding was behaving super weirdly.
0 kommentar(er)
