Convict45Jan 30

PIR sensors that HA insists are lights

https://lemmy.world/post/42411110

Show threadSayCyberOnceMoreJan 31

You can definitely change a sensor’s type, but my recommendation is to change it as close to the sensor as possible.

I use zigbee2mqtt (so I don’t know if this applies to z-wave), but to change the 1 or 2 devices that were wrongly detected on my system, I changed them in zigbee2mqtt first and then HA will use the corrected data.

If I corrected HA, then corrected zigbee2mqtt I’d have to do this twice, plus I presume HA wouldn’t automatically pick up any other changes I made to that sensor because it had been overridden.

Show threadConvict45

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.

Jan 31 at 4:09pmWeb
Show threadClaude FlammangJan 31
@Mpeach45
What is the solution in zwave world?
Show threadConvict45Feb 3

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.

Show threadClaude FlammangFeb 3

@Mpeach45

My question was how you did manage to adjust the entity type. (As I don’t have zwave)

By the way:
Homeassistant simply works with the entities provided by the various integrations. So in this case the Zwave integration (Happens to be also maintained by the Homeassistant project) has to learn to report your device correctly to Homeassistant.

Show threadConvict45Feb 5
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.