It really aggrevates me that a product designed to monitor and control and they can’t keep their database up to date. This was sept 2023, it’s now march 2025 and still no action?
They’re out playing with voice as if it’s critical functionality, but the purpose of Home Assistant is not a toy it’s supposed to keep up with devices and controls sold - especially in ZigBee and TCP as they’re probably what’s in use…
Really how much time or effort is it for the development team to keep the devices references up to date. Certainly not months or years after reporting?
I know device updates aren’t as much fun as voice, but really why isn’t the device list kept up to date?
Your device and the one in the original post could be quite different. Though they share a general module ID (TS0001) and manufacturer prefix (TZ3000), they have different product IDs.
As I understand it, if Tuya followed the ZCL specifications there wouldn’t be nearly as many issue with products using their firmware. Maybe you should point your ire at the source of the problem instead of the, mostly volunteer, group of people who have made it so these devices work with HA.
Do you really believe that the 2-3 Nabu Casa devs devoted full-time to voice, who have specialist knowledge in the field, would be better placed updating device handlers for random Tuya products?
Also, while they may not be the majority, there are users for whom voice is critical functionality for someone in their household.
Intrigued by your screenshot I just checked it on my side and seems like only SWITCH can be changed to other entity type. Normaly you can do it here (as your screenshot shows) or in helpers (switch type device change) - something like that. But as name suggest I think it only applies to switches. So you can’t change light to switch but can change switch to whatever you want.
I kinda understand the logic behind but still such limitation is dumb. Who cares what type of device you want to convert to different type - should be allowed.
However, you can work around this by creating a template switch that mirrors the behavior of your light entity. This involves defining a new switch entity that controls the existing light entity, effectively allowing you to treat the light as a switch in your automations and interfaces.
Or if you don’t want to play with templates just create switch helper and make automations to sync state between this light and your helper switch.
Maybe my reply is disappointing but that’s the only sollutions that comes to my mind.
I forgot this limitation, sorry.
But you can simply use this : Zigbee Home Automation - Home Assistant ( modifying device type)
Just replace ieee with yours
Done and restarted, no difference, what is supposed to have happened?
Correction light switch is now a general switch but still no power monitoring… As before it shows the 4 entities but there is no value not even from Voltage that always shows mains voltage level.
Three years or more this device has been out, it was reported here years ago, how is it their fault if a product doesn’t keep up with years between product deployment and still no support?
I keep being told don’t rely on Home Assistant, don’t expect this or that. But software is used to carry out a task, if it doesn’t what’s the point of it?
How long does it take to update a device database? There doesn’t seem to be a facility enabling us to do it or information in which files need editing. So they bare the burden of maintenance.
