Honeywell T6 Pro Min-Max Incorrect

[Walt12]

I have installed 2 Honeywell T6 Pro thermostats. They work fine but HA incorrectly has the min/max (set in C 5 and 40) rather than F 41 and 104. Therefore when I try to change the temperature setpoint via the Climate card, nothing happens. You can see the problem in the MQTT broker:

My fix has been to manually fix the setting in MQTT by running the following commands

mosquitto_sub -t homeassistant/climate/Main_Floor-Thermostat/climate/config > Main_Floor
mosquitto_sub -t homeassistant/climate/2nd_Floor-Thermostat/climate/config > 2nd_Floor
grep -rl ‘“min_temp”:5,’ Main_Floor | xargs sed -i ‘s/“min_temp”:5,/“min_temp”:55,/g’
grep -rl ‘“max_temp”:40,’ Main_Floor | xargs sed -i ‘s/“max_temp”:40,/“max_temp”:85,/g’
grep -rl ‘“min_temp”:5,’ 2nd_Floor | xargs sed -i ‘s/“min_temp”:5,/“min_temp”:55,/g’
grep -rl ‘“max_temp”:40,’ 2nd_Floor | xargs sed -i ‘s/“max_temp”:40,/“max_temp”:85,/g’
mosquitto_pub -t homeassistant/climate/Main_Floor-Thermostat/climate/config -f Main_Floor
mosquitto_pub -t homeassistant/climate/2nd_Floor-Thermostat/climate/config -f 2nd_Floor

Once I do that I can then set the temperature correctly.

Is there some fix so that I dont have to do this every time HA restarts.
Thanks
Walt

[petro]

Well, you wouldn’t have this problem if you used websockets instead of MQTT for ZwaveJSUI. There’s really no reason to use MQTT over ZwaveJSUI websockets

[petro]

FWIW, I use both zwave and zigbee and I use websockets for Zwave and MQTT for zigbee.

[Walt12]

I would love to, but for whatever reason, ZWaveJsUI never starts listening on port 3000 even though it is configured properly.

[Walt12]

Sorry… wrong screen

[petro]

Home assistant connects to your ZwaveJS UI, not the other way around. So this phrase doesn’t make sense.

@Walt12

ZWaveJsUI never starts listening on port 3000

[Walt12]

The Zwave server instance must start listening on tcp port 3000 in order for HA to use the zwavejsui agent to connect to the server. My ZwaveJSUI is on a seperate sever from the HA server

[petro]

Yes, that’s fine. You can configure that in HA. As long as HA can see that IP, then HA can connect to the server in ZwaveJS UI.

Not sure if you’re running it in a docker container or what (for zwavejsui), but you just need to have that exposed under services → ports

[Walt12]

[petro]

my man, you said it was on another machine, why are you using HA’s IP address

Nevermind, I’m blind

[petro]

Then it seems you don’t have your other machine setup correctly to allow connections to port 3000

[Walt12]

HA runs on 192.168.1.63 and the MQTT broker, ZwaveJSUI, and Zigbee2mqtt run on 192.168.1.61

[petro]

So, assuming you’re using docker containers, you want to set up the ZwaveJSUI container’s ports the same way you set up MQTT’s port for the broker. It’s the same thing. If you can connect to MQTT, then you need to employ the same process you did for MQTT to ZwaveJSUI

[Walt12]

Agreed, but I cannot get the zwave docker to start the server on port 3000.

[petro]

then use another port, any port will work. Just can’t be the same as something else that is used on that machine.

[Walt12]

nothing is using port 3000, but regardless I just set it for 3005, and the tcp port never shows up.

Both of the images from from 192.168.1.61

[petro]

Just another question, you did set up the home assistant section too right?

[petro]

are you using docker?

[Walt12]

Yes I am using a docker container.

[petro]

Ok, and is your container for zwavejsui set up to expose the port? Or better yet, how are you creating the container for ZwaveJS UI?