Domoticz

manjh wrote: ↑Saturday 26 October 2024 11:51 I have been using TUYA plugin version 1.0.13 for quite some time now, it used to work OK but recently I find it non-responding. No apparent error code, just "not working".
I have tried to disable and then enable the plugin, but that sometimes fails and locksup Domoticz.
The solution that works OK is to log in to the Pi, and restart the Domoticz service.

Any clues?

I have thought about migrating to another plugin (tinyTuya??), but am a bit worried about the migration path. Would I lose all devices, and then manually have to re-install?

manjh wrote: ↑Tuesday 29 October 2024 7:58 Am I looking in the wrong place to find a device ID?

Xenomes wrote: ↑Tuesday 29 October 2024 21:55

manjh wrote: ↑Tuesday 29 October 2024 7:58 Am I looking in the wrong place to find a device ID?

Go to iot.tuya.com => Cloud => open Project => Devices
Device ID are listed there, you need only one.

manjh wrote: ↑Wednesday 30 October 2024 7:32

Xenomes wrote: ↑Tuesday 29 October 2024 21:55

manjh wrote: ↑Tuesday 29 October 2024 7:58 Am I looking in the wrong place to find a device ID?

Go to iot.tuya.com => Cloud => open Project => Devices
Device ID are listed there, you need only one.

I get an empty list. "no data found"...

manjh wrote: ↑Wednesday 30 October 2024 19:45 So I went back and installed TinyTuya as per instructions.
Installation shows on Pi:

Code: Select all

  error: subprocess-exited-with-error

  × Preparing metadata (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [6 lines of output]

      Cargo, the Rust package manager, is not installed or is not on PATH.
      This package requires Rust and Cargo to compile extensions. Install it through
      the system's package manager or via https://rustup.rs/

      Checking for Rust toolchain....
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

sudo pip3 install tinytuya

heggink wrote: ↑Friday 01 November 2024 10:21 Off topic but I thought I would sollicit anyway: I saw the author (xeno..) work on a plugin using the local api. There is a node red implementation for the local api which I am now using. Together with a little logic (with help from @gizmocuz) that creates the HA-autodiscovery devices, it works really well. I use it to control both a heater and an IR panel. Using the local api, I am no longer dependent on a cloud service.
Happy to share if anyone is interested.

manjh wrote: ↑Friday 01 November 2024 18:24

heggink wrote: ↑Friday 01 November 2024 10:21 Off topic but I thought I would sollicit anyway: I saw the author (xeno..) work on a plugin using the local api. There is a node red implementation for the local api which I am now using. Together with a little logic (with help from @gizmocuz) that creates the HA-autodiscovery devices, it works really well. I use it to control both a heater and an IR panel. Using the local api, I am no longer dependent on a cloud service.
Happy to share if anyone is interested.

Yes, interested!

heggink wrote: ↑Saturday 02 November 2024 7:56 I'll write a topic about this under the mqtt-ad section

manjh wrote: ↑Saturday 02 November 2024 13:37 I now own about 15 smart-switches and I can switch them on/off from Domoticz.
But most of these switches also have power-monitoring on board, and I have been unable to access the stored information from Domoticz.
When I access them via the Tuya app, there is quite a lot of useful info.

Is there a way to pull that info into Domoticz?

Xenomes wrote: ↑Saturday 02 November 2024 16:53

manjh wrote: ↑Saturday 02 November 2024 13:37 I now own about 15 smart-switches and I can switch them on/off from Domoticz.
But most of these switches also have power-monitoring on board, and I have been unable to access the stored information from Domoticz.
When I access them via the Tuya app, there is quite a lot of useful info.

Is there a way to pull that info into Domoticz?

That data isn’t shared by the tinytuya module, and I don’t think it’s shared from Tuya to tinytuya either. You could update the device in Domoticz, and it should refresh, but due to a calculation in place, there will be some drift over time.