Why is it not as easy to add a WiFi device as a Zigbee device?

Month of "What the heck?!"
1

We have Local Tuya but it requires a lot of manual fiddling to move a device from Smart Life or similar. Why can’t we just recognise WiFi devices that are in pairing mode directly and then configure them in the same way as Zigbee devices?

2

Because there is no common communication standards between Wi-Fi IoT devices unless they are matter certified wifi devices.

3

Well, ZigBee is also not entrely standard but HA seems to recognise most – many more than Alexa Echo 4th Gen for example. Maybe a guaranteed universal solution for WiFi devices is not possible, but the Tuya / Smart Life system seems to be a de facto standard for many smart home devices and eWeLink is very similar; so that would be good start. It would end up lıke Local Tuya but be much easier to set up. One would revert to an integration for more exotic devices (like with Zigbee).

4

Those phrases don’t belong in the same sentence. If you knew the history behind Tuya, you’d understand how bad they are at following any standard. They can’t even get their own devices to behave the same way.

2 Likes
5

And the local tuya protocol is a reverse engineered protocol, which still requires the id generated by the tuya-cloud

6

So the key is id generation. Is there any reason not to reverse engineer further and emulate id generation as well?

7

Because it would be near impossible without knowing how it’s hashed

8

This proposal is also related to the possibility of adding BleBox devices. Currently, we have to add devices one by one. It will be nice to see the possibility of adding BleBox devices in one integration step. In the system with the letter “D”, such a possibility exists. BleBox devices are added by entering the device’s IP:

1 Like