Device Does Not Handle Service/Action

Plugins & Plugin Development Reactor
1

I’m getting an error when using an expression to try and set the setpoint of my radiator valve and wondered if anybody has encountered this before?
Condition: Room goes below set temperature for the room.
Expression (LRrad5): Gets the set temperature of the room and adds 5.
Action: Sets the set point of radiator valve to the value of LRrad5.

When I try and run the action I get the following error:
urn:upnp-org:serviceId:TemperatureSetpoint1_Heat/SetCurrentSetpoint(NewCurrentSetpoint=“”, ): ERROR: Device does not handle service/action

I can see that the value isn’t being passed through, if I replace the expression with a value then the action runs as expected. I tried to pass the value as a string as well but this also failed. Any insights into what I’m doing wrong here would be appreciated!

2

Hmmm… your example shows parens around the variable name. It needs to be curly braces {LRrad5}. Also, check spelling of the variable… LRrad5, LRadd5? Failing any of that, please post a Logic Summary from the tools page (read the instructions at the top of the report carefully if this is your first time posting a logic summary).

3

Hey, I’ve been using the dropdown lists to populate the names so they have the correct curly braces around them, the parenthesis were just my poor explanation sorry! As far as I can see capitalization/spelling is correct, it seems to be failing for all expressions.
Here’s the logic summary:

*************************************************** REACTOR LOGIC SUMMARY REPORT ***************************************************
   Version: 3.4 config 19226 cdata 19082 ui 19237 pluginDevice 211
    System: Vera version 1.7.4453 on Sercomm G450; loadtime 1573635865; systemReady 1573635937; ALTUI v2.45; Lua 5.1; JSON dkjson 1.2
Local time: 2019-11-13T09:31:41+0000; DST=0; Godstone, England United Kingdom
House mode: plugin 1; system 1; tracking on
  Sun data: { "stamp": 2019317, "civdawn": 1573627014, "nautdawn": 1573624601, "sunset": 1573661754, "nautdusk": 1573666350, "latitude": 51.2478, "astrodusk": 1573668687, "longitude": -0.06914, "civdusk": 1573663937, "astrodawn": 1573622263, "sunrise": 1573629197 }
  Geofence: not running
====================================================================================================================================
Heating ON (#243) tripped
    Version 19082.38 11/13/19 09:30:59
    Message/status: Tripped
    Variable/expressions
       0: livingroomsetpoint       getstate( 139, "urn:upnp-org:serviceId:TemperatureSetpoint1", "CurrentSetpoint" ) [last "19.00"(string)]
       1: masterbedsetpoint        getstate( 100, "urn:upnp-org:serviceId:TemperatureSetpoint1", "CurrentSetpoint" ) [last "16.00"(string)]
       2: maxsetpoint              getstate( 232, "urn:upnp-org:serviceId:TemperatureSetpoint1", "CurrentSetpoint" ) [last "18.00"(string)]
       3: LRrad5                   getstate( 139, "urn:upnp-org:serviceId:TemperatureSetpoint1", "CurrentSetpoint" ) +5 [last 24(number)]
       4: MBrad5                   getstate( 100, "urn:upnp-org:serviceId:TemperatureSensor1", "CurrentTemperature" ) +5 [last 26.5(number)]
       5: MXrad5                   getstate( 232, "urn:upnp-org:serviceId:TemperatureSetpoint1", "CurrentSetpoint" ) +5 [last 23(number)]
    Condition group "Reactor Sensor 6" (AND)  TRUE as of 01:46:08 <root>
      &-T-housemode in 1,3 [1 at 14:26:41; T/T as of 14:26:41/14:26:41] <cond0>
      &-T-group "Temperatiure Sensors" (OR)  TRUE as of 01:46:08 <grpkc40vuv>
      |     |-F-group "LRbelowtemp" (OR)  false as of 08:24:58 <grpkcgyux6>
      |     |     |-F-service Wall Thermostat (139) urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature < {livingroomsetpoint} [19.30 => 19.60 at 09:07:11; F/F as of 08:24:58/08:24:58] <condkc418n5>
      |     |-F-group "MBbelowtemp" (OR)  false as of 07:34:34 <grpkcgz5f7>
      |     |     |-F-service Temperature Sensor (158) urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature < {masterbedsetpoint} [19.37 => 19.31 at 09:30:01; F/F as of 07:34:34/07:34:34] <condkc5mxsh>
      |     |-T-group "MXbelowtemp" (OR)  TRUE as of 01:46:08 <grpkcgz6ye>
      |     |     |-T-service Room Thermostat (232) urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature < {maxsetpoint} [16.47 => 16.41 at 09:27:04; T/T as of 01:46:08/01:46:08] <condkc5o1g5>
    Activity grpkcgyux6.true
        Device Living Room Radiator (241) action urn:upnp-org:serviceId:TemperatureSetpoint1_Heat/SetCurrentSetpoint( NewCurrentSetpoint="{LRrad5}" )
    Activity grpkcgz6ye.true
        Device Max Radiator (183) action urn:upnp-org:serviceId:TemperatureSetpoint1_Heat/SetCurrentSetpoint( NewCurrentSetpoint="{MXrad5}" )
    Activity root.true
        Device Heating (137) action urn:upnp-org:serviceId:HVAC_UserOperatingMode1/SetModeTarget( NewModeTarget="HeatOn", NewHeatSetpoint="1" )
    Activity grpkcgyux6.false
        Device Living Room Radiator (241) action urn:upnp-org:serviceId:TemperatureSetpoint1_Heat/SetCurrentSetpoint( NewCurrentSetpoint="{livingroomsetpoint}" )
    Activity grpkcgz5f7.false
        Device Bedroom Radiator (100) action urn:upnp-org:serviceId:TemperatureSetpoint1_Heat/SetCurrentSetpoint( NewCurrentSetpoint="{masterbedsetpoint}" )
    Activity grpkcgz6ye.false
        Device Max Radiator (183) action urn:upnp-org:serviceId:TemperatureSetpoint1_Heat/SetCurrentSetpoint( NewCurrentSetpoint="{maxsetpoint}" )
    Activity grpkcgz5f7.true
        Device Bedroom Radiator (100) action urn:upnp-org:serviceId:TemperatureSetpoint1_Heat/SetCurrentSetpoint( NewCurrentSetpoint="{MBrad5}" )
    Events
        11/13/19 09:05:32 reload: notice=Luup reload
        11/13/19 09:05:32 start: 
        11/13/19 09:05:33 variable: oldval=28, variable=MBrad5, newval=26.5
        11/13/19 09:07:01 devicewatch: device=232, old="16.68", name=Room Thermostat, var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, new="16.51"
        11/13/19 09:07:11 devicewatch: device=139, old="19.30", name=Wall Thermostat, var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, new="19.60"
        11/13/19 09:07:51 devicewatch: device=158, old="19.68", name=Temperature Sensor, var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, new="19.62"
        11/13/19 09:12:53 devicewatch: device=158, old="19.62", name=Temperature Sensor, var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, new="19.56"
        11/13/19 09:16:55 devicewatch: device=158, old="19.56", name=Temperature Sensor, var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, new="19.50"
        11/13/19 09:17:03 devicewatch: device=232, old="16.51", name=Room Thermostat, var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, new="16.47"
        11/13/19 09:20:58 devicewatch: device=158, old="19.50", name=Temperature Sensor, var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, new="19.43"
        11/13/19 09:27:00 devicewatch: device=158, old="19.43", name=Temperature Sensor, var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, new="19.37"
        11/13/19 09:27:04 devicewatch: device=232, old="16.47", name=Room Thermostat, var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, new="16.41"
        11/13/19 09:30:01 devicewatch: device=158, old="19.37", name=Temperature Sensor, var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, new="19.31"
        11/13/19 09:30:13 configchange: 
        11/13/19 09:30:17 configchange: 
        11/13/19 09:31:00 configchange: 
    Devices
        ZWave (1) urn:schemas-micasaverde-com:device:ZWaveNetwork:1 (19/0); parent 0; plugin -
        Temperature Sensor (158) urn:schemas-micasaverde-com:device:TemperatureSensor:1 (17/0); parent 1; plugin -
        Wall Thermostat (139) urn:schemas-upnp-org:device:Heater:1 (5/2); parent 1; plugin -
        Room Thermostat (232) urn:schemas-upnp-org:device:Heater:1 (5/2); parent 1; plugin -
4

Everything looks good and right in the setup, and the conditions are performing as expected. I missed before in your text that you seem to be using the “Try” button (running man) to test the action, but it doesn’t fetch variable values like the core code (that’s a limitation more than a bug, but could go either way).

I think you’re OK with what you have set up. Let it run. See what happens. Keep running Logic Summaries and watch the “Events” section. It’s not the easiest to read (it’s meant for me to look at mostly), but you should quickly get the gist of it and prove to yourself that the actions are working.

5

Another user ran into this issue and correctly discovered that it works properly if you mark the variable for export. That’s a “workaround”, but it’s still a bug, and I now have a “hotfix” for it if you or anyone else reading cares to patch their install: Reactor 3.4 Hotfixes - Reactor - Ezlo Community

6

Awesome, thanks so much! Yes I was using the Try function to test, I’ve applied the hotfix and that now works perfectly as well.