Update on my situation (for those that care and are waiting for updates and new features), I have now finally had eye surgery in both eyes and eyesight is getting better by the day. Still have about a month of eyedrops, but I'm now able to read pretty clearly on the computer screen although my brain still needs to get used to the dual focus lenses I got implanted. So should resume work on the computer in the weeks to come and be able to finally update the code. I have a long list of things to do and will most likely squash a few bugs and release new features as time goes by with updates every 1 to 2 weeks until we got everything working for different scenarios.
BTW, for those that tested the V2 version with the builtin HE virtual thermostat, this will be abandoned because of the fact that Hubitat decided to let us be able to use custom virtual devices on Homekit. I will use parts of the V2 code to update the current version to make it more reliable.
Glad to hear about your successful eye surgery @nclark .
Hey, I have a fireplace thermostat that think's it's in heating mode, yet the fireplace is off (was manually turned off, I guess) and the temperature is above the set point. Shouldn't the thermostat code notice that the measured temperature is above the set point, and turn itself off, and also turn the fireplace switch off even though the fireplace switch is already off?
I could try to make this change in the code and do a pull request, if it's smart to do so.
hi @nclark can I somehow set the switching temp difference to switch on/ off at +0.2c / -0.2c instead of +0.5c / -0.5c ? if its possible, can you pls let me know where can I set it in the code ?
I'm heating with electric radiators and I don't mind if it switches on/off more often. thanks
Let me check that tonight, this is a one time setting but when I tried it, the child app says it's at .2 but the device says .5. I will need to investigate this tonight and find what's going on.
I think the solution is / was (still checking if works) is to update the threshold both in the driver's code and in the thermostat's code. I've deleted everything, updated both files and then started from scratch. now testing. sorry I didn't want to be a pain with my questions but you know.... happy (non-freezing) girlfriend = happy life. I was just hoping to be able to update this without deleting the whole thermostat with the childs , re-add and update all depending automation jobs but,dashboards, etc.. I really had to do this.
Ya I understand, saw the first post but had limited cell phone coverage at a friends camp for the weekend and could not test the app to give you an answer, then completely forgot about it and since I had already read the post, did not have a notification about it until you posted again
I had released a V2 of this app/driver that used the built in virtual thermostat device but I did not like the limited control I had over it (originally to make it compatible with Homekit), but scrapped the project soon after, I will be merging the new logic code and some of the other new features/upgrades I had added to it and keep going on this setup. My other project is on hold for a while so I'll have some time to work on this one a bit before summer comes in full blast and the wife takes out her ToDo list
so its a problem for years just never been brave enough to remove the whole thermostat and re-add at winter time. now I have 2 weeks just myself so can improve stuff. Also planning to add one more sensor to the furthest point of the apartment as the aeotec multisensor seems not so reliable. Actually this code I think does not need any more overcomplication. its just works as is. no fancy stuff, clear code, easy to read, it can't luch rockets, just set the temperature and it works perfect in the last 2 winters for me. One thing I found problematic but that's a pebkac and not a code issue. if you change the temperature too quickly up and down it goes to emergency off. but its understandable thats the whole point of emergency off, to stop idiots. I had problems with the mentioned aeotec multisensor too, if it renders the thermostat to emergency off, no way to restore it. I've set the aeotec's driver to standard z-wave temperature sensor and that's it.
@IrisetH, ok so here is a quick and dirty way to get this working for you before wife comes back
Right after line 35 in the command section add on line 36 the setThermostatTreshold method to the commands as follows...
This will give you a place to change it in the commands section of the device...
When I have an update, this will work as it should and the setting of it will be brought back to the child app as it should be, but at least it will now work for you!
Great to hear that this is still being developed. If you are gathering ideas, I for one would like to be able to turn off the panic mode off setting when temp sensors are not reporting.
