localtuya VS zigbee2mqtt

Tuya devices, and the Tuya-based Monster, Greeni, etc stuff can be connected to HA using the Tuya Integration, or converted to local-only using Tuya Cloudcutter and connected to HA using Local Tuya, or even flashed with Tasmota, ESPHome/Libre Tiny, or OpenBeken.

It's still on my list of things to try so I don't have personal experience, but I think https://github.com/rospogrigio/localtuya can help you. Maybe start with reading the readme to see what limitations exist for Tuya devices.

localtuya

You can control them locally with this integration for Home Assistant: https://github.com/rospogrigio/localtuya

We got some cheap Tuya bulbs from Kogan. Unfortunately they were too new to flash with tuya-convert, but they can still be controlled locally through Home Assistant with localtuya.

There is the [Local Tuya](https://github.com/rospogrigio/localtuya) integration for Home Assistant. This will eliminate the cloud dependency of the Tuya devices you have. Once you have them in Home Assistant you can expose them to HomeKit just like HomeBridge does.

Don't the Treatlife devices just use the Tuya backend? If so, you can add them directly to HA using the cloud based official Tuya Integration, or the local-only Local Tuya via HACS.

Have you considered Zigbee2mqtt[0]? You'd be running an extra program, but the docs are really good, it's pretty lightweight, and MQTT is incredibly easy to talk to from python or basically anything else.

[0] - https://www.zigbee2mqtt.io/

For Zigbee, I can recommend using the Zigbee2MQTT (https://www.zigbee2mqtt.io/) integration instead of HomeAssistant's built-in ZHA system. It might be a bit more complex to set up, but it's very powerful and works fantastically. (User "simon42" on YouTube has some good videos about the topic, but they're in German.)

This is definitely better than many of the alternatives but still not perfect. With Zigbee etc you end up locked into one or more of the ecosystems, not to mention some manufacturers implementing it in a way that has weird quirks (see [1]). With esphome you have a limited choice of devices (would love to see more), but you also usually end up locked into keeping a 2.4GHz WPA2 AP for your devices (and you miss out on mesh, but also the problems when it doesn't work...)

1: https://github.com/Koenkk/zigbee2mqtt/issues/16717

I can recommend this: https://www.zigbee2mqtt.io/

You can keep your Hue bulbs and devices but threw away the app, hub, and need to work with hue as an institution at all.

I got a $30 USB zigbee stick to replace the hub. works great!

It looks like it uses zigbee? If you have a server you could run zigbee2mqtt. You'd also need a zigbee dongle / adapter.

\also posted on the z2m* github device discussion board

If you want to use HA on your phone, you would need to install it on the pi, along with either ZHA or Zigbee2MQTT for the Zigbee network interface. Debian alone won't be able to interface with most of your smart devices.

I still haven't understood if the devices will change the path using the better route or not (since I've just tested a bTicino switch K4003C and it keeps using the worst path with 1 or 0 signal quality over a near Ikea repeater with a signal quality of 50).