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 …”

It is still there. The device is still empty. No config is possible. Just rename (Name:), delete and save are available.

Don’t use the gui, just stop pimatic daemon, edit config.json and start pimatic in commandline.
This give better control and info

@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"!

The reason its not loaded is interesting. Use the steps in the former post and see what the messages are when the plugin tries to load

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...

can you check if the folder pimatic-app/node_modules/request is present?

Its there

Then change the following line in the file TadoClient.coffee

   request = env.require('request-promise/node_modules/request')

to

   request = env.require('request')

and restart to see if the plugin is now loading

We are on the way…

Are you able to implement conrtols (temp +/-, on off)?

It seems like its working and I probably can add functionality.
But i’m not the owner of the plugin.

TH1485 wasn’t online since a year. I think he will not update it… Maybe a fency fresh name… Would be nice if you could lift it somehow up. When you start with something then it gets to a new level . But can understand if you don’t like! Thx for your support!

Something fency like pimatic-tadotwo

Yes, why not

Also nice:
pimatic-tado-reloaded
pimatic-tado-heating
pimatic-tado-web-client
pimatic-tado-relay

But its up to you…

pimatic-tado-reloaded seems a good name, but pimatic-tados is also nice?
I’m not owning a Tado device and because your tado is in a test setup, it would help if you allow me access to your Tado (with temporary credentials)

Sure, we can do so. Give me a PM an we can share details.

Hi,
Nice to someone is using the plugin , I got notified by mail, I will update this line. Thanks for the research all!

Hey, cool that u r still here. Thanks for updating. The plugin is not in the plugin list will you make it available there in the updated version? Other user could get better to it when it will be listed there.

Nice, some action on this plugin
To get rid of the unknown compatibility message you also need to add in the package.json

  "peerDependencies": {
    "pimatic": ">=0.9.0"
  },

@TH1485 are you also adding the extra funtionality?

Will make it controllable as a thermostat or will it stay as a temp/hum sensor?