Never used node red, can it be ran on a home assistant yellow cm5?
Yes, it can be run on same piece of equipment. It can be Home Asst Add-On.
In HA, Goto Settings --> Add-ons --> Click the Add-On Store button in bottom right corner. Then, search for Node Red. Enjoy the new rabbit hole.
6 Likes
I run Node-RED, InfluxDB, and Grafana as Add-Ons on my HA Yellow. Works great!
4 Likes
There seems to be a bug for Thermostat Modes and Thermostat Fan Modes in the HomeAssistant Hub Parent.
I just connected a Midea AC unit in HA, and HADB brought it in as a thermostat. Everything works well, except for the commands for Thermostat Mode and Thermostat Fan Mode.
In the Attribute states, it does set the supported modes as are defined in HA.
However, these options are not set for the setSupportedThermostatModes and the setSuportedThermostatFanModes as options in the command dropdowns.
The dashboard tile does use the attribute settings, so I can set the modes correctly from a dashboard tile, but not from the device page.
In the Log, it seems to set it both ways, one for the specific thermostat modes from the HA integration, and then again for default modes. So I end up with default modes in the command dropdowns.
So, the command dropdowns end up with only the option for the second default settings for the supportedThemostatModes and supported ThermostatFanModes.
For now, I modified the HADB Generic Component Thermostat driver to have command buttons for each of these modes I cannot select with the dropdowns for modes, which is working for me, but a fix would be nice
Thanks!
Edit: I found an even better work-around, as I can override the mode commands by specifically adding the commands to the driver with the correct options.
1 Like
This is by design because Hubitat doesn't natively support every mode your thermostat does. By not conforming with the native list of modes it causes issues with native components like dashboard tiles, rules, etc.
This was adjusted in v2.7 in August 2024:
3 Likes
Well, the dashboard tile only uses the supported modes attributes, so the tile works fine.
I'm good with my driver edits to give me what I need, so if this is not a bug, my post can just be considered a work-around for anyone else who wants these controls.
As it was, there was no way for me to change to the missing modes at all besides using the dashboard tile, so my other apps could not change the mode to fan only since there was just no way to do it with a command, so it really leaves the integration lacking key features to send certain needed commands from other apps, even though the missing commands are actually supported by HADB to be sent.
Sounds like there is just no "good way" for HADB to set the command dropdowns for the unique mode commands that are actually available.
I suggest that maybe HADB could create a command button for any non-capability defined thermostat modes and fan modes it finds, instead of just leaving it with no way at all to send the command from the driver page.
Either way, I'm good.
If you use HPM to manage HADB, make sure you clone the thermostat driver and make your own version versus editing the one that comes with HADB. Otherwise the next update will overwrite your changes.
This already exists on the parent HADB device, "Call Service" command. Now it is not specific to thermostats but it will allow you to invoke a command on any HA entity. Here is an example on how to use it:
2 Likes
Thanks. Yes, I made a custom component Midea AC driver so it won't get changed with updates.
Good to know about using the Call Service, that could be handy. I think in this case, the modified driver with the commands that I need is the way to go for simplicity in just calling the commands in the component device.
Edit:
If anyone else wants to use my driver modified for the Midea AC commands, it is here:
2 Likes
Hi, I am using the bridge to access Carrier Thermostats and it has always worked great.
However Home Assistant deprecated so Auto is no longer used, it is now heat_cool .. the other entities (Off, Heat and Cool) all work fine .. it’s just Auto (which is what the bridge thermostat driver gives as option) doesn’t work anymore, can we change (or clone) the generic thermostat driver to use heat_cool instead of Auto to match the available HA entities?
In HA "auto" and "heat_cool" are two different modes and one did not replaced the other. Both are still in use and are not interchangeable.
Originally HADB was trying to translate HE modes to compatible HA modes but this cause numerous incompatibilities. Since last year this behavior was change to match whatever the HA thermostat was advertising regardless of HE build-in modes. Hence the HE auto mode is no longer translated to heat_cool. This allow for all available mode on a HA thermostat to be usable which was not the case before.
Unfortunately the choices for mode selection are fix. A possible workaround would be to overload the thermostat mode command with all the possible HA modes.
What would it take or mean to creat a work around? I assume I’m not the only one using HA to control Carrier/Bryant units.
It would be great if Hubitat (HADB) would allow the selection or use of heat_cool or auto … as the other options (off, heat and cool) that are provided in Hubitat thru HADB still work fine.
The issue at hand is that we use WebCoRE to turn off AC if the sliding door is open for longer than a predetermined time, this still works. However if the sliding door is closed for a predetermined time, then the AC needs to go back on, and the only option in Hubitat (and by extension WebCore) is Auto and that doesn’t work anymore … heat_cool is what is expected by HA
Sorry, I thought you were refering to the themostat mode command on the device page. I don't know about WebCore but in RM you allready can choose any supported mode declared by the device.
Do you have the latest version of HADB? Does your device use the "HADB generic thermostat component" instead of the build-in one?
Maybe someone who knows WebCore could chime in.
Hi, I’m the device page it’s the same result .. can only select Auto ….
In the Hubitat device page (using the generic HADB thermostat driver) you can only select Auto, but further down on the page in the Supported Thermostat Modes it does show heat_cool .
Hi,
And to confirm, I am running v 2.17 of HADB installed with Package Manager. And the device is using the HADB thermostat driver, see below
It confirm what I was saying: HADB report the supported thermostat modes declared by the HA entity. RM use that in automation. I don't know about WebCore though.
But the actual Hubitat device page does not provide an option to turn the AC on, as I copied in the screen … it has only the auto option and not the heat_cool in the device page … eg I can use the Hubitat device page to turn the AC off, set it to just heat or cool as thermostat mode, but I can’t turn it on back to auto (heat_cool) mode.
Is that not an issue in the device page/driver itself then?
I will check later today the RM and see if it does show the heat_cool option
Thanks for the quick responses!
Sorry I got confuse with these statements.
I have to circle back to my first answer: The build-in command on the device page is fix. I will message you a modified generic component for you to try.
