Missing thermostatMode() attribute values in Rule Machine 4.0

[bravenel]

If you are trying to trigger a rule from the driver sending Dry mode, then use Custom Attribute against that device, and it will offer all of the attributes the device sends. Select ThermostatMode, and then select from the values it offers.

This won't be "fixed" anytime soon in Rule Machine, as this mechanism already exists to get at any attribute/value pair for any device that is not otherwise already part of RM.

[jasonbalsor]

I am trying to send the dry mode command as an action in a rule based on time of day. Not using dry as a trigger.

[bravenel]

Then look at Run Custom Action. Select your device, and it will give you every command it supports.

[jasonbalsor]

Like this?

[jasonbalsor]

It is listed as a supported mode but not showing up in the list.

[jasonbalsor]

The dashboard supports the dry mode and it works great.

[marktheknife]

@jasonbalsor

Like this?

Yup, as long as the string you entered exactly matches the mode (spelling, capitalization etc.) that should do it.

[bravenel]

@jasonbalsor

Like this?

Looks like that driver is not implemented properly if it's not giving you that choice in the pulldown.

[jasonbalsor]

If you read above in this thread, back in March it was explained by the developer and you had posted that you would put it on the list to add/fix

[bravenel]

What driver is this? I was referring to the driver, not to RM. RM does not pull "supportedThermostatModes", and it appears that the driver isn't presenting them either.

[jasonbalsor]

This was the post from the developer in this thread

@cybrmage

the attribute "thermostatMode" is a standard attribute.

When used with the dashboard "thermostat" tile, the (list) contents of the attribute "supportedThermostatModes" is used to tell the tile what modes are supported by the specific thermostat device.

In Rule Machine, the attribute "thermostatMode" is presented with the default modes and the "supportedThermostatModes" attribute is ignored.

Similarly, "thermostatFanMode" is a standard attribute. This attribute can also be customized in the dashboard with the "supportedThermostatFanModes" attribute.

AND both of these attributes, "supportedThermostatModes" and "supportedThermostatFanModes" are documented in the developer documentation for the thermostat capability.

So... Using standard attributes, the Dashboard tile operates properly, but Rule Machine does not... Seeing that the supported modes attributes work in the dashboard, it makes sense that they should work in Rule Machine.

I believe this to be a bug (or oversight) in Rule Machine. I will ping @bravenel and @mike.maxwell to get their opinion...

[bravenel]

@jasonbalsor

This was the post from the developer in this thread

Yes, I know.

What driver are you showing above?

[jasonbalsor]

[WITHDRAWN - Use the new Broadlink integration by @tomw] NATIVE Broadlink RM/RM Pro/RM Mini/SP driver

RC HVAC Manager (BETA) (Remote Controlled HVAC Manager) Features: Supports creating multiple virtual thermostats Supports generating and sending Generic and specific IR/RF signals using a Broadlink RM Pro or RM Mini device Supports Fujitsu, Mitsubishi, Toshiba, Daikin, Sanyo and other protocols Supports device refresh to help prevent device setting from being changed Before you begin: Make sure you hubitat is upgraded to Hubitat platform v2.1.7 or greater Make sure that the Broadlink mana…

[bravenel]

I'm going to make the changes to RM to use supportedThermostatModes and supportedThermostatFanModes. A couple of interesting points: not all thermostat drivers support these attributes, and the attributes are not intrinsic in the thermostat capability (as implemented currently). That means that a default set of modes and fan modes must exist.

There is another issue for the situation when multiple thermostats are selected that have different available modes or fan modes. For this only the intersection of the modes available will be offered (least common denominator), as otherwise one could hit a thermostat with a mode it doesn't support.

[jasonbalsor]

Thanks!