I've been troubleshooting some general weirdness and I noticed that my NYCE motion sensors were sending temperature, humidity, and battery with every Motion Active report even though humidity and temperature were disabled using the NYCE driver. So I changed them to the Generic Zigbee Motion (no temp) Driver and now they are only reporting motion activity like I wanted.
My question is, did this actually stop them from sending that information or could they still be sending it and I'm just no longer seeing it in the logs using this driver?
Enable debug logging and you'll see, but my guess is that the data is still coming in and the driver is just not logging the events. However, a reset and re-pair of the device using this driver will probably stop them if that is what you're after (it's just that switching to a driver that cared about these attributes is generally not going to un-configure the ones it doesn't care about).
That being said, changing the settings on the previous driver should have worked, too. Running "Configure" yourself if changing the settings alone didn't work might help, as could again a re-pair (in both cases, I mean without deleting the device first). It's possible this is one of those odd devices that doesn't listen when it's asleep, only at certain times, and may have missed the configuration commands from the driver, which a re-pair would help with since it would send them again and you'd know it would be listening. It's also possible this device just doesn't respond to them for some reason -- but one of these should help if it does.
1 Like
I turned on information logging and debug logging and im only seeing motion events still. So it must have worked?
The NCYE driver only has 2 option, reporting humidity and reporting temperature. I can set them to various time lengths, percent changes, or disabled. I had them disabled. So that part worked. But they were still being sent on every motion active event. There wasn't an option specifically for sending on Motion events, they just did it.
But you see Zigbee messages in Logs with motion, right? Did verify that their data contains no temperature information, or are you just basing this on the fact that no events were generated? There isn't going to be an event regardless of this logging setting; that was just to see what the data contained. If you aren't sure, share it here, and someone can take a look.
Here's a screen shot of the NYCE driver. Below that is the log file of a single active/inactive. If I change the drive to generic I don't see all that extra stuff.
I don't see any actual debug logging there, which is unusual if the setting is enabled (maybe hit "Save" just to make sure?). In any case, it does look like the device (driver) said it responded to the configuration, so if the data is still coming in, that leaves at least my one guess above as unlikely.
You may want to reset the baseline. Here's a scenario I read seems to happen often enough:
User adds a device to HE - and HE attempts to use a driver it deems is a close match.
The driver puts temp/humidity/illumination and or motion methods for a device that may not actually have 4 sensors.
Later, you switch the driver - lets say to 'Generic Zigbee Motion'. In your device screen you still see attributes for all four - even tho the new driver is just doing motion now.
The solve is to blow all attributes. By changing the driver to 'Device' 
then save it.
Go back into the device and now there are a number of buttons:
Mash all the buttons - one at a time.
Now click save once again.
Repeat the process and set the driver back to 'Generic Zigbee Motion (notemp)' or whatever it was. The attributes left are only the attributes of the active driver - no 'ghost' attributes remain. The HE community has been using this 'trick' for years to clear up some of these types of issues.
Regarding what is reported by the device - all I can say is 'read the box'. I don't know any way to get an actual report of what sensors a device has in reality. An example comes to mind - Third Reality Outlets. The driver that comes up initially has a power consumption attribute - even tho the model I had didn't provide a power value. I used the 'Driver' technique I just described, then used the 'Generic Zigbee Outlet' and I was clean.
Another reason this is important - drop downs. If a device driver reports that a driver supports a method - say 'Illumination' - the device will show up when an App has drop downs that sort for that attribute - even if the device doesn't actually do it. It's a PITA.
In some cases you need to have a custom driver - I always relied on giants like @kkossev for stuff - he for example is a low level driver guy for a lot of Tuya/Chinese type stuff and his work is amazing! GL.
3 Likes
