23
PIR sensors that HA insists are lights (lemmy.world)
submitted 9 months ago by to c/homeassistant@lemmy.world
8 comments fedilink hide all child comments
 

I’ve just moved my z-wave installation over from Indigo and to a happily surprising extent, the transition has gone very well.

However, several different PIR sensors from different brands (homeseer, Ecolink, VisionPro) are detected as lights by HA, even if they have, in some cases, configuration options that are related to a PIR. HA assigns them a bulb icon, and the only control shows as a switch with the name “Basic.”

Is this a known bug, and is there any way to get HA to reassign the correct sensor type to these devices short of un-including and re-including them? Is that likely to get them working?

I’m also seeing a ZP3102 PIR sensor by Vision Security that’s showing only as a “basic” sensor.

Any advice? These sensors showed up fine in Indigo.

Screenshot of a PIR device that hasn't got proper device info in HA
you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 9 months ago (5 children)

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.

  • permalink
  • fedilink
  • source
  • hideshow 5 child comments
    •
  • [–] [S] 1 point 9 months ago (4 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 9 months ago (3 children)

    @Mpeach45 What is the solution in zwave world?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] [S] 1 point 9 months ago (2 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 9 months ago (1 child)

    @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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] [S] 1 point 9 months ago

    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.

  • permalink
  • fedilink
  • source
  • parent