Hey all, is there a way to change the minheattemp value from 1.5? I understand that it is a failsafe for freezing temps, but I am using this in a detached garage and only want the heat to come on at -5 sometimes. as far as I can see, this is not possible.
Thanks for any help
Only way is to change the setting in the drivers code (Advanced vThermostat Device) on line 60. Once this is done you will have to remove the existing vThermostat instance (garage) and then create a new instance that will be programmed with the new minHeatTemp setting.
If you use it elsewhere I would recommend setting it back to the default setting, updates should not affect this setting once the instance created.
@ady.adrianu, don't worry did not forget about this, I did changes to the code like you suggested but on fast heating systems, I'm overshooting by 1 degrees many times a day (asking 20C it will stop heating when it gets there like expected, but I often get a new temp report with 21.xxxC or close to it.
So I finally found a way to predict when it will reach the expected temperature and stop before I get a temp report from a sensor. Each time I get a temp report I calculate the heat/cool rate based on temp and time. I'll be testing this code for a week and see if the numbers are consistent and publish it if successful, but it's looking good on paper. I think I might need to average out these rates over a day or so to be consistent.
i just used a smaller threshold since my heating system has a slow start and continues to heat after its stopped. I tried 15 degrees with 0.2 threshold and it usually doesn't go above 15.5-15.7 depending on the room
Would it be possible to integrate modes into the thermostat so that only certain temperature sensors are used during certain modes and maybe even only certain heating and cooling elements are used during certain modes? I know ecobee thermostats can do this kind of thing with the temperature sensors so this would be a cool addition.
Use case: During sleep/night mode only look at the bedroom sensors and only control the bedroom heating/cooling elements.
Obviously this could be achieved with multiple instances of this app, but imo that will get messy very quick.
Sorry, but no plan do add this kind of functionality built in, this is only meant to be like a regular thermostat (but virtual) and that's it. Just like scheduling that is added to it via Thermostat Scheduler, you might be able to get that kind of functionality by using Thermostat Controller that is built in HE, don't know if it incorporates modes but you might ask if it could be added if it's not already included.
Any chance of adding a circulate fan outlet/control? Reason being is that I would like to integrate the HVAC blower to come on if temperatures are more than 5 degrees apart among sensors throughout the house. I know this can be done with the rule machine, but would like to use the control buttons in the dashboard panel for thermostat as well.
Yes I was planning on adding fan control support in the near future, I'm being swamped at work right now and barely have time to work on this. As soon as I can get it implemented, I'll let you know, I was thinking of having it turn on when heating / cooling turns on and turn off an x amount of time after that. I was not planning on having more controls than that on the fan for now (just like a regular advcanced thermostat).
I have seen analysis that shows that running the fan in circulate mode is not very effective at equalizing temperatures. In other words, given the heat capacity of air, the airflow rates, and the temperature differences, the rate at which heat is moved from the warm areas to the cold areas is negligible.
I have been happily using this for my Thermostat needs and syncing to Google Home, but now it seems that the thermostat cannot be controlled any longer with Google, not by voice nor by screen.
I can still control it via my dashboard and the resultant change will be reflected near instantaneously in Google, but all changes made directly in Google home will briefly show, but then "roll back" and no change is made. You can see this behaviour here in this video.
Do you have any idea what might be going on here ?
Hi - I'm looking for (or looking to develop myself if I can't find one pre-made) something that will let me play with "comfortable temperature" calculations based on things like outdoor temperature, humidity, etc. A naive heat index calculation would be a start, but I'd like something with a little more flexibility.
Is that a feature you might add to this anytime soon? Can you recommend anything along those lines?
Just found @JohnRob's dew point calculator and it looks like it is very close to what I want. I may still tweak it a bit, but it probably will address by basic needs.
This is kind of weird, I have it working perfectly with Echo devices and/or google mini and yet some users just can't get it to work, now you come here with he Google Home not working and to tell you the truth I'm stumped on this one, nothing changed on my side of the code, I have all the required methods in my code (even if it's not doing anything for some), works for some, doesn't work for others. I would really like to help on this one but I just don't know where to go to do that.
This is not a feature I would add to this for the only reason that this app/device is meant to imitate a regular connected thermostat.
I do believe this could be a very nice app to complement this and any other connected thermostat just like Thermostat Scheduler and/or Thermostat Controller do to make them more "intelligent". Just not something I would implement here since this thermostat is actually just used to control a dumb space heater more than anything. It is only as precise as the temp sensors you use and how fast they report temp changes unlike a regular thermostat that has instant access to the actual temp all the time.
Yes, very strange, as it has worked really well up until now. As you mention, there have been no changes from your side and I haven't updated your app since installing so that must mean there is something on the Google Home side or due to updating hubitat (which i just did, from 2.2.4 to 2.2.6 ?
I also have some Google Mini's and the same situation there, I can ask for the change to temp, but it will not execute. However, making the change on Hubitat will almost immediately show the change in Google. So it seems to be from Google to Hubitat.
I will do some tests and report back.
That makes sense. Thanks so much for getting back to me!
@nclark Thank you for sharing. Exactly what I'm looking for controlling panel heater with temperature sensors and smart switch / power outlet.
Suggestion: Ability to disable "fan" in the preference as there is no fan in many heating appliances.
Thanks again.
Just found this driver for a special control system i am building. It also does not respond/work for me with Alexa. The Alexa app shows "there was a problem", and doesn't present a control dialog for the device in the alexa android app.
Sonoff S31 lite Zigbee can be added, the relay they use is actually rated for 16A 240V so a meer 1800W is no big deal for it.
So I got my Sonoff switches in and made my advanced vthermostats. They work great, thanks for the code @nclark !
Unfortunately that was only from the dashboard. From Google Home using either the app or the assistant the heat setpoints would not change. I'm using the official integration and it works fine for my physical zwave thermostat.
So I created a virtual thermostat using the built-in virtual device type and that can also be controlled fine from Google Home. Any idea why the vThermostat devices can't be controlled this way?
For now I have a rule that makes both Vthermostats track the virtual device setpoint but it's starting to feel a bit inception like with all these layers of obfuscation going on.
Download the Hubitat app
