Closed steckenpferd closed 4 years ago
Kann die Hardware bzw. es reicht ein gekoppelter Account aus, zur Verfügung stellen.
Homebridge modules exist: ckuburlis/homebridge-tado, homebridge-tado-thermostat-plugin, homebridge-tado-ac as example.
Please check if the new ioBroker.ham Adapter can help here: see https://forum.iobroker.net/viewtopic.php?f=36&t=14972
With homebridge (ham) and a plugin for this it is a bridge for the bridge ... not so cool.
Not really!
Home bridge can act in iObroker like an adapter, so using homebridge with the related plugin in iObroker is basically the same as an adapter.
Only functionality is limited to what homebridge cab so and that's much less iObroker could do
Yes of course ... But I can wish me a adapter too :)
I checked the API and existing NPM modules it looks quite simple to implement.
It all runs by the tado Web API, will need an demo account or hardware to continue. Needed. Logic looks equal to my as my just released discovery adapter so doesn't look very comes to build
So I have an account. But unfortunately I can not provide my hardware ... because she has to work.
Would it be an option to have a teamspeak/Teamviewer Session together ?
Lets See what data The npm packages can Provide If we manage to make an Connection we get the data needed to build the adapter.
I see on the forum that more people are interested in this one
Yes of course, many peoples "need" this :)
We can write in the forum about a team viewer date
What would be interesting to know is if an adapter would provide more capabilities than the current HAM binding, of not I would suggest to keep it by HAM binding.
Otherwise it makes sense to spend time in an adapter but from my understanding only if there is a benefit :-)
I get the readings via fhem, however not being able to overwrite - set put command - via JavaScript / blocky.
The API documentation I read, says I should use curl. If I can't combine window sensors to switch off the thermometer. The bridge and adaptors available are useless. Therefore, a real tado adapter for io would be great.
We are investigating the possibilities for Q1 2019
Looking forward to your investigations. Really appreciate to get the adapter. :)
Yes ... But I think we have to wait :(
I expect being able to start within the next 2 weeks
that's a great news ... das wäre ja wirklich wunderbar :)
I just wanted to inform you about my recent contact request to TaDo concerning their announced, official API. https://support.tado.com/hc/de/articles/205505299-Welche-neuen-Funktionen-sind-geplant-Was-ist-auf-der-Roadmap-f%C3%BCr-die-Entwicklung- I will keep you informed, if there is any feedback.
Much appreciated.
I did some efforts over the turn of the year with Homebridge Adapter and Tado Plugin. Anyhow, I am facing some issues resulting in overheating and some other inconsistencies. Official API and an dedicated adapter would be very needed. Otherwise in mid-term, I would even consider changing to Homematic.
Regs!
I just wanted to inform you about my recent contact request to TaDo concerning their announced, official API. https://support.tado.com/hc/de/articles/205505299-Welche-neuen-Funktionen-sind-geplant-Was-ist-auf-der-Roadmap-f%C3%BCr-die-Entwicklung- I will keep you informed, if there is any feedback.
I moreover believe that Tado intentionally prevents such an official API, since they are following that approach to charge 2.99€/m or 29.90€/yr for this auto-assist service. That would provide auto switch-off if window open or if away via geo-fencing.
Providing the API would mean then, people would bypass this and automate everything via iobroker/fhem etc.
That would be another reason to sell the Tado devices and switch to Homematic. I am kinda pissed off.
Honestly speaking I would be willing to pay a charge to use the API as well to use it for integration in iobroker.
@DutchmanNL Can I vote for this adapter too? Is TS/Teamviever enough or would hardware speed up things?
I moreover believe that Tado intentionally prevents such an official API, since they are following that approach to charge 2.99€/m or 29.90€/yr for this auto-assist service. That would provide auto switch-off if window open or if away via geo-fencing.
Providing the API would mean then, people would bypass this and automate everything via iobroker/fhem etc.
That would be another reason to sell the Tado devices and switch to Homematic. I am kinda pissed off.
True, on the other hand the window open function and the auto away feature is available (and per announcement will stay available) for all v3 users. It pauses the heating if window is detected and publishes in the App and webservices as well as it should lower the temp if all users are away (I never use the feature). To me this seems to be pretty much the same as the new "Auto assist" for new customers and the v3+ version.
Any news?
In the meantime I installted the HAM.adapter and integrated tado that way. Works like a charm.
I know it works and works that way. But that is not the solution. There should be an adapter for such a big system like Tado. Everything else is just a crutch or interim solution. All others have a Tado adapter, only ioBroker not :-(
didn't find time yet and trying to get an device from local supplier for integration purpose
I just wanted to inform you about my recent contact request to TaDo concerning their announced, official API. https://support.tado.com/hc/de/articles/205505299-Welche-neuen-Funktionen-sind-geplant-Was-ist-auf-der-Roadmap-f%C3%BCr-die-Entwicklung- I will keep you informed, if there is any feedback.
The public API is on tados developer roadmap for more than 4 years .... they announced it at CeBit 2015 .....
I mentioned that in my request. TaDo's answer was .... NOTHING.
Hi Dutch,
we talked also in iobroker forum. For Summertime you could have one of my thermostats and a bridge or we try it by teamviewer / VPN
could be a nice try, let me investigate the backend part end api availabilities and than look further
Is anyone still working on the Tado Adapter? It would be great if there was a stand-alone adapter for Tado.
I know some friends (and me ofc) who would absolutely appreciate a comfortable Tado adapter for ioBroker. I think Tado is one of the largest players for smart thermostats. It would be awesome if one could just fill username and password in the adapter settings and then the adapter pulls automatically the Home ID, zone IDs, room names and all thermostats.
Link to pull home ID: https://my.tado.com/api/v2/me?username=XXX&password=YYY
Link to pull zone ID and other: https://my.tado.com/api/v2/homes/ZZZ/zones?password=YYY&username=XXX
die documentation zu dieser API is wirklich eine Katastrophe da gib es überhaupt garnix.
Da ich die Geräte nicht habe (auch nicht kaufen werde) wirds immer noch schwer und ja hab die Sommer periode bissl verpasst nur waren auch noch andere prios.
Es wierde helfen wen ich mal mit jemand seinem account einloggen und schaue dürfte und ein par queres ausprobieren die ich reverse engineering gefunden habe.
Ohne gerate/zugang und docu wirds wirklich schwer leute aber bin bereit zu helfen
Kann man die API documention nicht vom Macher des Homebridge Plug-ins erfragen? haha😅 Ansonsten helfen evtl die Links von der Threadproblembeschreibung... Ich bekomme morgen ein zweites Set fuer eine andere Wohnung - muss das aber nicht sofort dort installieren und kanns erstmal an einem Heizkörper bei mir mit separatem Account laufen lassen. Dann kannst du damit erstmal bisschen spielen.
Vielleicht gibt es hier auch hilfe:
http://www.peterdebruin.net/tado.html Die Seite läuft super
Ansonsten ist die API hier dokumentiert: http://blog.scphillips.com/posts/2017/01/the-tado-api-v2/
Falls das nicht hilft Dutch kannst du gern mein Account oder via VPN/Teamviewer Zugang zu meinen System haben... hatte ich ja schon mal angeboten
via node-red gehts übrigens auch super
na sieste kaum spuckt man bekommt man auch was mit. data cool jetzt kann weiter gehen.
brauche aber immer noch nen account bzw gerate um entwickeln zu koennen.
du hättest nur fragen müssen ;p hattest damals gesagt du musst erst noch andere Sachen machen und wolltest dich im Januar melden...
schick mir ne mail mit deiner bevorzugten email dann füge ich dich zu meinem Zuhause hinzu: vertrieb.ditosama@gmail.com
hab dir ne. mail geschikt :)
sehr cool!! Sobald es eine Github page für den Adapter gibt, wäre es super die hier zu verlinken
Sehr geil, wäre echt super wenn du das machen würdest, Dutchman. Ich würde gerne unterstützen aber mein System kommt erst im November..Dann hab ich 9 Ventile
sehr cool!! Sobald es eine Github page für den Adapter gibt, wäre es super die hier zu verlinken
sobald ich Zugangsdaten und die erste JSON hab kommt mal schnell ne ALPHA zum schnuppern und dan können wir den adapter zusammen fertig machen. Glaube da hatte sich ach jemand gemeldet mit script Kenntnisse das fließt hier dan zusammen.
also wird schon :)
ich habe die NPM library gefunden, es kan losgehen :
Hab dich eingeladen, die Npm läuft ebenfalls bei mir via Node-red. Hatte ich im post vorher erwähnt.. wenn das hilft kannst dort auch reinschauen.. aktuell hole ich die Werte wie Temp. Hum, online, Heating Power und Anwesenheit von dort und und schreibe sie in States für den iobroker
Hab dich eingeladen, die Npm läuft ebenfalls bei mir via Node-red. Hatte ich im post vorher erwähnt.. wenn das hilft kannst dort auch reinschauen.. aktuell hole ich die Werte wie Temp. Hum, online, Heating Power und Anwesenheit von dort und und schreibe sie in States für den iobroker
danke ! Ich habe die Einladung angenommen und fange mal an :)
ktuell hole ich die Werte wie Temp. Hum, online,
wen du Beispiele hasty immer gerne
ich scheitere im moment hier
Moin Dutch,
hast du die HomeID & ZonenID verwendet? Es muss mehrstufig ablaufen. Esrt get HomeID dann getZoneID und aus der Zone dann Unit Devices (Handys etc.) bekommst du mit der HomeID
Ich schick dir meine Daten per Mail
Hi,
there are many unoffical API documentenations maybe some good developer can create with that an adapter:
I can send my hardware for test purpose.
http://libtado.readthedocs.io/ http://blog.scphillips.com/posts/2017/01/the-tado-api-v2/ http://wirres.net/article/articleview/10326/1/6/