-
I am using this integration with a google nest thermostat in the US. I have a external thermometer sensors. HA is set to Fahrenheit and the current temperature is 155 and the target is 356. I know this is the unit. Is there a way to force a conversion? |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments
-
Hello @ucphinni , Welcome to US friends !. Yes I think it should work with Fahrenheit temperature. I get the configuration of the HA and use this units to configure the VTherm. What is wrong in the behaviour you observe ? |
Beta Was this translation helpful? Give feedback.
-
During the configuration wizard, I saw all units are in C and entered them in C (e.g. 20 instead of 68). My temperature at google nest was 68 F. The external sensor is set to my elderly mother's bedroom downstairs. The google nest thermostat was originally set by better thermostat to 69 F. When I switched to VTherm, it moved it up and back so I know VTherm adjusted it.. However, since my target on VThem was set to 355, I was afraid to adjust it and switched back to better thermostat (its cold outside and cant afford to experiment at the expense of someone else's discomfort) It might have worked except for the 355 target in VTherm. 68 C is 155 F so the display is doing a double conversion. Not sure what would have happened and I somewhat panicked. I also, lost a degree F during switch over because I had to reboot the entire docker stack because BT got into an inifinite loop. VTherm doesn't have that problem. It seems VTherm has more features that I wanted (I eventually want to have the target temperature move to occupied rooms and not only that have different scheduled minimum target temp per room on schedule when occupied. I plan on putting mmsensor in mom's bedroom to detect when she is in there and also when she is sleep so I can slightly drop the temperature and turn off her tv.) |
Beta Was this translation helpful? Give feedback.
-
I will try again tonight (Eastern standard time) |
Beta Was this translation helpful? Give feedback.
-
This is the screen snapshot of the google nest (top) and VTherm bottom. The sensor is a connected to a bluetooth sensor set to Fahrenheit if that makes a difference. When I press the already selected VTherm heat button, the target of VTherm jumps to 95 F but does not affect the "Dining Room" therm at all. The target of "Dining Room" stays at 53 F. I have an idea. I am going to create a template from the sensor to convert it back to Celsius and see if that works. |
Beta Was this translation helpful? Give feedback.
-
That fixed the display but now getting these errors when turned on debug. I was probably adjusting the target on VTherm or maybe it was doing it on its own. Cant tell.
File "/usr/local/lib/python3.11/site-packages/google_nest_sdm/auth.py", line 145, in _raise_for_status The above exception was the direct cause of the following exception: Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): |
Beta Was this translation helpful? Give feedback.
-
Confirmed it is working great for me with v6.7.0. |
Beta Was this translation helpful? Give feedback.
Confirmed it is working great for me with v6.7.0.
Nothing special other than setting all of the set points in fahrenheit.