After one experience, I actively avoid Tuya devices.

Damn that’s an ugly box of a car.

Maybe github.com/juliuswms/hass-to-json is the place to start?

Wildly unhelpful. And yes, the integration INSISTS that my device is a light. Yes, I can change how they report, but there’s still some dumb ass slider for dimming associated with my PIRs.

Expecting new adopters to be editing YAML (or whatever) in order to make a newly added but years old device to HASS is one hell of a bar to entry.

I get that, but being new to HASS (but not to home automation) I can’t help but be surprised that z-wave devices are so oddly partially supported. Sure, most people go with zigbee because of cost. I can’t help but think that if every single zigbee motion sensor showed up in HASS as a light, there’s be a big stink about it.

I went this route a while ago using old cellphones and ultimately found them not worth the “savings” over even thirty dollar IP cams. There are just too many fiddly things that interfere with their reliable operation:

• updates
• app crashes
• awkward placement and power delivery
• overheating

I’m new to HA so let me make sure I understand. Are you saying that setting up zones in the UI isn’t enough to get them to work?

Sorry, I don’t really understand your question. They’re just simply is no MQTT involved in Z wave.

From my perspective, the “solution” would be for Home Assistant to properly recognize the device type.

Thanks. I did finally figure it out. But it’s still pretty weird to have to hide these “basic” “Lights” from the rest of the UI.

FYI to my knowledge there’s no MQTT involved either directly or optionally with z-wave.