![]() ![]() ![]() In the end, I decided that a likely culprit was the rapid sequence of commands (possibly even overlapping?) through the OpenSprinkler API, so I added a 5 second delay to the rule as follows: rule "run front yard after running garden beds" When checking the OpenSprinkler interface after this happened, I discovered a weird thing on the display: the stations weren’t all just on or off - they were in a “Scheduled” state (I’ve tried to attach a screenshot here, but it didn’t work - I might try in a reply).Īfter using the OpenSprinkler app to send a “stop all stations” command (returning them all to the normal “off” state), I could once again turn on individual stations through the OH interface, but as soon as I triggered the rule at the start of this post, I got the OFF->ON->OFF behaviour again, along with the “Scheduled” state in the OpenSprinkler interface. Once this had happened, any attempt to turn on any station manually (through OH) would receive the same results - on, then back off again almost immediately. If I turned off the waterGardenBeds item, it would trigger the rule given above, but not with the expected results:ġ5:33:12.852 - Item 'waterGardenBeds' received command OFFġ5:33:12.853 - Item 'waterGardenBeds' predicted to become OFFġ5:33:12.854 - Item 'waterGardenBeds' changed from ON to OFFġ5:33:12.854 - Item 'gWateringStations' changed from ON to OFF through waterGardenBedsġ5:33:12.855 - Item 'waterFrontYard' received command ONġ5:33:12.856 - Item 'waterFrontYard' predicted to become ONġ5:33:12.856 - Item 'waterFrontYard' changed from OFF to ONġ5:33:12.857 - Item 'gWateringStations' changed from OFF to ON through waterFrontYardġ5:33:12.858 - Watering turned on - timer set for: 15 minutes.ġ5:33:16.360 - Item 'waterFrontYard' changed from ON to OFFġ5:33:16.361 - Item 'gWateringStations' changed from ON to OFF through waterFrontYardĪs you can see, the station that was meant to be turned on by the above rule did initially turn on, but then turned off again within a matter of seconds. I could then manually turn off that station, and manually turn on the first of the other stations - again, responding as expected:ġ5:32:36.709 - Item 'waterVeggiesLawn' received command OFFġ5:32:36.710 - Item 'waterVeggiesLawn' predicted to become OFFġ5:32:36.710 - Item 'waterVeggiesLawn' changed from ON to OFFġ5:32:36.711 - Item 'gWateringStations' changed from ON to OFF through waterVeggiesLawnġ5:32:51.092 - Item 'waterGardenBeds' received command ONġ5:32:51.093 - Item 'waterGardenBeds' predicted to become ONġ5:32:51.094 - Item 'waterGardenBeds' changed from OFF to ONġ5:32:51.094 - Item 'gWateringStations' changed from OFF to ON through waterGardenBedsġ5:32:51.095 - Watering turned on - timer set for: 15 minutes.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. 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 Comments
Leave a Reply. |