That’s a very strange error to get. And I’m getting it also. This is brand new behavior that I haven’t seen before. Something has happened in the backend. I have some triggers from Minimote buttons that worked fine yesterday, but are now throwing the same error.
I will have to investigate further. I have another Minimote app that is working, so I’ll dig into what’s going on.
I will post back here when I discover the cause of this.
Awesome thanks! this is an amazing app-- trying to migrate many of my old automations over to it.
OK, I found that bug, and it’s fixed. I messed something up a day or so ago. You can get the fixed version of Rule from Github, 1.6.12b
Rule github: https://github.com/bravenel/Rule-Trigger/blob/master/smartapps/bravenel/rule.src/rule.groovy. Save and Publish for me.
Please let me know if that solves the problem.
will update now and check. thanks!!
looks like its working. thanks!
I dont know if you take feature requests but…
I have a bunch of the Keen smart vents and a nest thermostat. I have them set to adjust how open they are based on room temp. what I would like to be able to do is close when the blower fan for the HVAC is off. There is no option for the thermostat features directly in the rule machine . think it can be done?
api(‘fan_mode’, modes.getAt(mode)) {
sendEvent(name: ‘thermostatFanMode’, value: mode)
poll()
def setThermostatFanMode(mode) {
def modes = [
on: [‘fan_mode’: ‘on’],
auto: [‘fan_mode’: ‘auto’],
circulate: [‘fan_mode’: ‘duty-cycle’, ‘fan_duty_cycle’: 900]
Rule Machine feature requests can be added in this topic:
keltymd - not elegant, but how about this:
IF Trigger Vent1 Temperature < 95 THEN Set Vent1 to 0%
where the 95-degrees was taken by observing the vent temperature in the IDE, and how it cools down when the furnace rests between heating episodes. This particular vent dropped down to as low as 85 - I picked 95 for it and might tweak it after observation.
EldRitch
kind of what I have. I have 98% if temp is under vent set point and once it hits point it goes to 20%. I dont want to close them all the way if the fan is blowing because the back pressure can cause issues with the HVAC unit when cooling or heating but I want 0% when the blower is off so that no or minimal heat/cooling leakage happens.
open rule
RelrDev2 enum <
ReltDev1 enum <
adjustDimmerTrue capability.switchLevel []
advanced bool false
alarmTrue enum ""
bulbsTrue capability.colorControl []
cameraTrue capability.imageCapture ""
closeValveTrue capability.valve []
condL1 enum Mode is Home
condR2 enum Temperature of Sensor-MBR Motion < 67
ctTrue capability.colorTemperature []
daysY enum []
delayedOffTrue capability.switch []
dimATrue capability.switchLevel Vent-MBedRoom
dimBTrue capability.switchLevel []
dimLATrue number 98
dimLATrue number 98
dimTrackTrue bool false
dimTrackTrue bool false
disabled capability.switch ""
fanAdjustTrue capability.switchLevel ""
garageCloseTrue capability.garageDoorControl []
garageOpenTrue capability.garageDoorControl []
isDev2 bool false
istDev1 bool false
lockTrue capability.lock []
modeTrue enum ""
modes enum Home
modesY mode []
myPhraseTrue enum ""
offSwitchTrue capability.switch []
onSwitchTrue capability.switch []
openValveTrue capability.valve []
operator2 enum AND
operator3 enum ""
pendedOffTrue capability.switch []
rCapab1 enum Mode
rCapab2 enum Temperature
rCapab3 enum ""
rDev2 capability.temperatureMeasurement Sensor-MBR Motion
ruleTrue enum []
state2 decimal 67
tCapab1 enum Temperature
tCapab2 enum Mode
tCapab3 enum ""
tDev1 capability.temperatureMeasurement Sensor-MBR Motion
thermoTrue capability.thermostat []
toggleDimmerTrue capability.switchLevel []
toggleSwitchTrue capability.switch []
tstate1 decimal 67
unlockTrue capability.lock []
Event Subscriptions
Name Handler Filter Source
mode allHandler true Home (Location)
temperature allHandler true Sensor-MBR Motion
Application State
Name Value
actsTrue Dim: Vent-MBedRoom: 98
cstCmds []
disabled false
eval [1, AND, 2]
howMany 3
howManyT 3
isExpert false
lastEvtName Sensor-MBR Motion
n 3
parenLev 0
str Mode is Home AND Temperature of Sensor-MBR Motion < 67
success false
token 3
close
Settings
Name Type Value
RelrDev2 enum >=
ReltDev1 enum >=
adjustDimmerTrue capability.switchLevel []
advanced bool false
alarmTrue enum ""
bulbsTrue capability.colorControl []
cameraTrue capability.imageCapture ""
closeValveTrue capability.valve []
condL1 enum Mode is Home
condR2 enum Temperature of Sensor-MBR Motion >= 67
ctTrue capability.colorTemperature []
daysY enum []
delayedOffTrue capability.switch []
dimATrue capability.switchLevel Vent-MBedRoom
dimBTrue capability.switchLevel []
dimLATrue number 25
dimTrackTrue bool false
disabled capability.switch ""
fanAdjustTrue capability.switchLevel ""
garageCloseTrue capability.garageDoorControl []
garageOpenTrue capability.garageDoorControl []
isDev2 bool false
istDev1 bool false
lockTrue capability.lock []
modeTrue enum ""
modes enum Home
modesY mode []
myPhraseTrue enum ""
offSwitchTrue capability.switch []
onSwitchTrue capability.switch []
openValveTrue capability.valve []
operator2 enum AND
operator3 enum ""
pendedOffTrue capability.switch []
rCapab1 enum Mode
rCapab2 enum Temperature
rCapab3 enum ""
rDev2 capability.temperatureMeasurement Sensor-MBR Motion
ruleTrue enum []
state2 decimal 67
tCapab1 enum Temperature
tCapab2 enum Mode
tCapab3 enum ""
tDev1 capability.temperatureMeasurement Sensor-MBR Motion
thermoTrue capability.thermostat []
toggleDimmerTrue capability.switchLevel []
toggleSwitchTrue capability.switch []
tstate1 decimal 67
unlockTrue capability.lock []
Event Subscriptions
Name Handler Filter Source
mode allHandler true Home (Location)
temperature allHandler true Sensor-MBR Motion
Application State
Name Value
actsTrue Dim: Vent-MBedRoom: 25
cstCmds []
disabled false
eval [1, AND, 2]
howMany 3
howManyT 3
isExpert false
lastEvtName Sensor-MBR Motion
n 3
str Mode is Home AND Temperature of Sensor-MBR Motion >= 67
success true
token 3
SmartApp Version Rule
State COMPLETE
Health HEALTHY
Development App False
Well that’s informative!
I don’t know if updating to the latest rule machine or SmartThings restored old data to the back end, but yesterday I swapped the location of two motion sensors (a first generation and a second generation). Both sensors had rules so I had to go in and change several rules to make everything work as it did. The change was made and everything was working correctly for the remainder of the day and throughout most of today. About 3-4 hours ago I notice things were not working correctly so I went back into rule machine and found a portion of the rule had revered back to the old setting. I have since corrected this but I am baffled as to how that could happen. Could upgrading rule machine cause this type of problem?
No, upgrading could not cause this. That is bizarre, to say the least!
If I am following, if someone continues to never publish Rule, we can keep on as we have, but for simplicity sake, one can save/publish and not affect anything, but it’s not required to keep Rule Machine working, Right?
I’m having some issues today as well where some of my rules didnt work and when I go into the rule everything looks okay but when i click the define a rule everything is blank or on some rules where I had more conditions then removed them they are showing up now if I click define a rule. I’m assuming something happened overnight with ST because I’m also having issues with some of my devices not working correctly.
Yes, that is correct.
The only thing is, if you publish it and aren’t fully aware that you did, like out of habit if you’re working on some app, then after that you always have to publish. So if you miss doing it, you may not be updating after that without being aware of it.
That’s interesting. It’s almost as if the current state got wiped, but when you go into the rule it gets rebuilt.
Are you guys in the UK? Similar weirdness, perhaps UK server hiccup?
Nope east coast US
20 characters