I went through the really short description, there wasn’t any hint for register something or a client secret
-
pimatic-tado new plugin for tado
-
The tado plugins use a client_secret. I found some info on how to check what the client-secret is and how to check the value; https://shkspr.mobi/blog/2019/02/tado-api-guide-updated-for-2019/
The client_secret mentioned in this post is also used in pimatic-tado.
After you login via https://my.tado.com/webapp , you can check if the client_secret is still the value from the post. -
As I can see it is still the same!
-
The Tado app is working fine. The plugin is shown as active, but the device seems to be faulty. It contains no information. I create it manually. Via UI it is not possible.
-
Unfortunately no. This was the first thing I have tried.
-
As I can see it is:
But with the hint “compability unknown”. The system is a playground. Clean standard installation with only this extra plugin
-
If so change also in package.json
"engines": { "node": "4.6.2", "npm": "2.15.11"to
"engines": { "node": ">=4.6.2", "npm": ">=2.15.11"It removes the compatibility message and you can see if the plugin is loaded.
Assuming that the plugin is compatible
-
@bertreb said in pimatic-tado new plugin for tado:
Ok, try to add in config.json the 2 values in the device config
"zone" : 1,
“interval” : 120000The config is already there.
I changed the engine, but “compatibility unknown” is still there after restart of the service, crazy…
No debug at all, but following error comes up when I save the device:
2020-12-26 20:03:53 error [pimatic-mobile-frontend]: Client error: Uncaught TypeError: Cannot read property 'match' of undefined -
If this is a test setup, you can stop the pimatic daemon (sudo service pimatic stop) and run pimatic out of the pimatic-app folder with sudo node_modules/pimatic/pimatic.js
You can see the plugin loading and should see a tado debug message starting with “Connected to …” -
It is still there. The device is still empty. No config is possible. Just rename (Name:), delete and save are available.
-
@bertreb said in pimatic-tado new plugin for tado:
If this is a test setup, you can stop the pimatic daemon (sudo service pimatic stop) and run pimatic out of the pimatic-app folder with sudo node_modules/pimatic/pimatic.js
You can see the plugin loading and should see a tado debug message starting with “Connected to …”Its not loaded:
20:15:06.677 [pimatic] No plugin found for device "wohnzimmer" of class "TadoClimate"! -
Here the whole output:
20:15:02.961 2020-12-26 Saturday 20:15:05.199 [pimatic] Starting pimatic version 0.9.54 20:15:05.202 [pimatic] Node.js version 10.16.3 20:15:05.202 [pimatic] OpenSSL version 1.1.1c 20:15:05.920 [pimatic, ppm] 2.15.12 20:15:05.932 [pimatic] Loading plugin: "pimatic-tado" (0.0.2) 20:15:06.040 [pimatic] Cannot find module 'request-promise/node_modules/request' 20:15:06.043 [pimatic] Loading plugin: "pimatic-cron" (0.8.8) 20:15:06.302 [pimatic] Loading plugin: "pimatic-mobile-frontend" (0.9.16) 20:15:06.511 [pimatic-cron] the time is: Sat Dec 26 2020 20:15:06 GMT+0100 (Central European Standard Time) 20:15:06.677 [pimatic] No plugin found for device "wohnzimmer" of class "TadoClimate"! 20:15:06.685 [pimatic] New device "Test"... 20:15:06.758 [pimatic-mobile-frontend] packing static assets 20:15:06.913 [pimatic-mobile-frontend] packing static assets finished 20:15:06.915 [pimatic-mobile-frontend] rendering html 20:15:08.341 [pimatic-mobile-frontend] rendering html finished 20:15:08.351 [pimatic] Listening for HTTP-request on port 80... 20:15:19.574 [pimatic] Flushing database to disk, please wait... 20:15:19.578 [pimatic] Flushing database to disk, please wait... Done. 20:15:19.579 [pimatic] exiting...
