Closed seydx closed 3 years ago
A wish, after opening and closing again, timer for delayed switching on of the heating. In the event that you go in and out of the patio door several times. That the heating doesn't always go on and off. Thanks
@det-box
Wouldn't it be better to have a simpler solution for this that is easily accessible to all? With config.json you could solve this with a "delay" option, so a thermostat would only switch if the "new" state is different, even after X seconds. This would also solve the problem where you open windows only for a short time, or`?
Yes, it would work that way.
Correction: Just to clarify again. ... so that a thermostat only switches on if the window detection is NO different when the window is closed, even after X seconds.
@det-box
Yesi understood you.
But we don't have to limit that to windows. We can use the "logic" generally on EVERYTHING.
If e.g. delay = 10s and thermostat is switched to OFF by an automation (e.g. because of window open), then the plugin should check if the thermostat is also OFF AFTER 10 seconds. If yes, then the thermostat is also switched.
Sorry, That's not what I mean, if the window is closed, wait 2 minutes before the thermostat turns on. If the window is opened again, the timer is reset and the 2min starts again.
Thx for your great plugin! Im really looking forward testing the new version! When will it be released?
@beatpaul
I think later this week I will publish it
@beatpaul
The beta version has been released. Check the issue =)
Hi! Im tested it, by deleting my old config, installing the Plugin, but i get this errorlog:
[3/11/2021, 8:48:19 AM] [TadoPlatform] TypeError: Cannot read property 'includes' of undefined
at /usr/local/lib/node_modules/homebridge-tado-platform/src/helper/deviceHandler.js:537:137
at Array.filter (<anonymous>)
at /usr/local/lib/node_modules/homebridge-tado-platform/src/helper/deviceHandler.js:537:62
at Array.forEach (<anonymous>)
at updateZones (/usr/local/lib/node_modules/homebridge-tado-platform/src/helper/deviceHandler.js:534:18)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at getStates (/usr/local/lib/node_modules/homebridge-tado-platform/src/helper/deviceHandler.js:415:9)
It seems it doesn't include my Tado device (i have Tado v1 and an external sensor that i dont use)
in my former config i hade to activate the device
thx for your help
Paul
@beatpaul
it seems the problem occurs while the plugin looks for a batteryState but your v1 doesnt support it?
@beatpaul
New beta version is online
H!
in the beginning i still had an error message:
[3/11/2021, 12:02:12 PM] [TadoPlatform] TypeError: Cannot read property 'includes' of undefined
at /usr/local/lib/node_modules/homebridge-tado-platform/src/helper/deviceHandler.js:540:86
at Array.filter (<anonymous>)
at /usr/local/lib/node_modules/homebridge-tado-platform/src/helper/deviceHandler.js:540:38
at Array.forEach (<anonymous>)
at updateZones (/usr/local/lib/node_modules/homebridge-tado-platform/src/helper/deviceHandler.js:535:18)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at getStates (/usr/local/lib/node_modules/homebridge-tado-platform/src/helper/deviceHandler.js:416:9)
but after activating "no Battery" it works great now !
thx
@beatpaul
ah, the error will be fixed in the next beta version, thx! =)
HI! After Installing Beta.3 i cannot enter the Settings in Config UI (although ist still works fine :)
@beatpaul
should be fixed in beta v4
There was several improvements in Beta v4:
If you use Open Window switches, Child Lock Switches, Central/Boost/Shedule/TurnOff Switches or Precene Lock, please turn them off after updating to Beta v4. After restarting Homebridge, you can turn them on again
If you have time, please take a look at the forum. Thank you!
@Nastras
~v6.0.0-beta.9 released~ v6.0.0-beta.10 released
v6.0.0-beta.10 works great for me 👍 kudos for the great new configuration-possibilities
one question about the Mode: Timer
:
In the TadoApp I can set up the timer-mode after "manual" changing the temperature. Am I correct in assuming that the timer mode replicates this functionality internally? So I can use the settings form TadoApp (and config as manual
) or use the timer-setting in the plugin-config? Are there any advantages/disadvantages depending on which variant I'll use?
Hey guys,
v6.0.0-beta.15 is online with some major changes in the background. Therefore, if u use "Central Switch", please disable it after restart so it should be removed from HomeKit. Afterwars, you can enable it again
@Somberland
The plugin can handle severeal modes.
Hey guys,
thx all for testing the beta version. It is officially released now. Have fun with version 6!
If you have time, please take a look at the forum again. Thank you!
Hello people,
as some of you may know, I am currently working on version 6 of the Tado plugin. Here in the thread I will inform all interested about the progress. Version 6 will have a lot of new stuff, config ui x support and even a custom UI. I have picked out many ideas from you here and made a note of them.
If you still have wishes or suggestions for improvement, you can share them here
Beta
All who would like to participate in the beta are welcome. To install the beta version, simply do the following:
sudo npm i -g homebridge-tado-platform@beta
And on the following page you can find details about the new config and its description
https://github.com/SeydX/homebridge-tado-platform/tree/beta
If you encounter any bugs during the testing phase, please report them here. Please remember to enable debug in config.json (
"debug": true
).To fix the errors as soon as possible, please include the log and config.json
First Look (Custom UI)
2021-03-06
TODO
Thanks to all for the support, suggestion, ideas etc.
Seyd