PIR sensors that HA insists are lights

DifferentComputers · January 29, 2026, 7:11pm

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?

DifferentComputers · January 30, 2026, 4:00pm

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.

tmjpugh · January 30, 2026, 5:06pm

Are you using zwavejs or zwavejsui?
How did you transition them to HA?

Did you add this device with security enabled?

DifferentComputers · January 30, 2026, 5:35pm

I’m actually a bit confused about which I’m using. I THOUGHT I installed the “simple” zwave integration not zwavejsui, but I have a network visualizer that I thought only came with the more complex one.

This is what I see in integrations, and I don’t see any way to identify which integration it is.

The transition was as follows, including a mistake on my part at step 1:

Did not use Indigo to purge removed/dead z-wave nodes prior to the transition.
Shut down Indigo’s z-wave interface.
Removed the Aeon Labs ZW090
Plugged the ZW090 into my HAOS rPi
Started up the Z-wave integration.

Security was not enabled on any device in Indigo, so I didn’t start it when I moved it.

Thanks for the help!

tmjpugh · January 30, 2026, 6:15pm

the “Zwave” integration connects to your hub/controller

zwavejs or zwavejsui + aeon lab controller are needed to control the devices

you can only use zwavejs or zwavejsui, not both
zwavejs is pretty much installed by default and likely you did this and did not realize

zwavejsui is same as zwavejs. zwavejsui simply adds a ui that makes managing devices easier.

HA >> settings >> zwave
if you go there it will get you to zwavejs or zwavejsui.

no security is fine for switches and non security related devices.
motiion detectors and locks will need security. for this you can individually exclude then reinclude the device with security enabled.

you can also try to reinterview device and maybe that will work but I think you need to remove and readd that device. you can do that from HA. You do not need to do from indigo

DifferentComputers · January 30, 2026, 6:22pm

The reinterview process is problematic because almost entirely, the problematic devices are battery powered. But it has been a couple days now and I think every device has reported in at some point, but still I have motion sensors that think they are lights.

I just experimented and pulled an OLD multi sensor out of mothballs to see if it would work, and with new batteries it included and started reporting, but like my other PIRs, HA seems to think it is a light:

Even though it also reports Luminance, temp, humidity.

This is an Aeon Labs DS805-ZWUS.

freshcoast · January 30, 2026, 6:25pm

Please review the pinned post in the Z-Wave category.

After reviewing that topic you believe a Basic sensor should not be exposed by the device, you may need to report the issue to Z-Wave JS.

DifferentComputers · January 30, 2026, 6:29pm

Mind explaining what the CC in “Basic CC” means?

freshcoast · January 30, 2026, 6:30pm

Command Class

DifferentComputers · January 30, 2026, 6:35pm

I don’t particularly care that the Basic CC is exposed. I care that this motion sensor (and others that may have other problems as well) are considered lights by HA and don’t report motion.

Time to exclude an reinclude one to see if that fixes it.

freshcoast · January 30, 2026, 6:37pm

If you posted the device diagnostic file then it might be possible to gain more insight about these devices. There’s not enough information provided in the topic to really understand anything specific.

DifferentComputers · January 30, 2026, 6:51pm

Well. I wanted to but the diagnostic file is 55k lines long. Is there some subsection of that that you need?

DifferentComputers · January 30, 2026, 6:53pm

Maybe this?

 "entities": [
      {
        "domain": "binary_sensor",
        "entity_id": "binary_sensor.old_multi_sensor_sensor_state_any",
        "original_name": "Sensor state (Any)",
        "original_device_class": null,
        "disabled": false,
        "disabled_by": null,
        "hidden_by": null,
        "original_icon": null,
        "entity_category": null,
        "supported_features": 0,
        "unit_of_measurement": null,
        "value_id": "31-48-0-Any",
        "primary_value": {
          "command_class": 48,
          "command_class_name": "Binary Sensor",
          "endpoint": 0,
          "property": "Any",
          "property_name": "Any",
          "property_key": null,
          "property_key_name": null
        }
      },
      {
        "domain": "binary_sensor",
        "entity_id": "binary_sensor.old_multi_sensor_sensor_state_door_window",
        "original_name": "Sensor state (Door/Window)",
        "original_device_class": null,
        "disabled": false,
        "disabled_by": null,
        "hidden_by": null,
        "original_icon": null,
        "entity_category": null,
        "supported_features": 0,
        "unit_of_measurement": null,
        "value_id": "31-48-0-Door/Window",
        "primary_value": {
          "command_class": 48,
          "command_class_name": "Binary Sensor",
          "endpoint": 0,
          "property": "Door/Window",
          "property_name": "Door/Window",
          "property_key": null,
          "property_key_name": null
        }
      },
      {
        "domain": "binary_sensor",
        "entity_id": "binary_sensor.old_multi_sensor_sensor_state_unknown_0x22",
        "original_name": "Sensor state (unknown (0x22))",
        "original_device_class": null,
        "disabled": false,
        "disabled_by": null,
        "hidden_by": null,
        "original_icon": null,
        "entity_category": null,
        "supported_features": 0,
        "unit_of_measurement": null,
        "value_id": "31-48-0-unknown (0x22)",
        "primary_value": {
          "command_class": 48,
          "command_class_name": "Binary Sensor",
          "endpoint": 0,
          "property": "unknown (0x22)",
          "property_name": "unknown (0x22)",
          "property_key": null,
          "property_key_name": null
        }

freshcoast · January 30, 2026, 7:02pm

Well, that’s something I guess. Not the full picture. The Any sensor doesn’t do what you need?

55k lines for a single device!? (My entire configuration diagnostic for 33 nodes is only 100K lines). Generally large files are better off posted to a pastebin site.

The Basic entity just exists when Z-Wave JS doesn’t map the Basic CC support it to something else like Binary CC or Notification CC. If any of those sensors work you can just disable the light entity. Or report an issue to Z-Wave JS so it gets fixed permanently.

DifferentComputers · January 30, 2026, 7:06pm

I downloaded the diagnostic for the device, and it included the entire diagnostic for all of HA.

The Any sensor MIGHT do what I need, if I knew what triggered or didn’t trigger it. Will a change in temp trigger it? I’ve yet to see Any turned off since I spun that sensor back up.

freshcoast · January 30, 2026, 7:19pm

After re-reading the original post, I should have probably started with this question:

Is there something that is not working with these devices? Or is your concern only the existence of the (Basic) light entity?