-
-
Notifications
You must be signed in to change notification settings - Fork 914
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fibaro FGMS001 ZW5 - no sensor binary report #2300
Comments
I switching actually to Zwave2MQTT too and faced excatly the same issue as you on my FGMS-001. That device is working properly for Motion Detection (in Jeedom so with Openzwave 1.4), but seems that on OZW1.6 (or Zwave2mqtt), the 'sensor' value 48-1-0 is not updated when a motion is present (while the 'home security' 113-1-7 value is changing its states (but in string, not in boolean) |
You should investigate the config options of the device to see if it can be set to send a SENSOR_BINARY (but note - that SENSOR_BINARY is depreciated by the specifications and isn't used on newer devices - So its possible that this device wont support it) |
For your information I noutice also the same issue on the Aeotec Multisensotr 6, but this one has the "Sensor Binary" option selectable. By using that parameter the issue dispaear and PIR status updated properly. Fibaro FGMS-001 doesn"t have unfortunately that setting available |
If you want the "older" sensor reports... Add your controller to the 4th association group. This group is used for "backwards compatibility" as @Fishwaldo said. The ZW5 by default uses the newer "notification CC". |
I recently started using zwave2mqtt and was migrating my devices from another controller (Homey) to my ZME_UZB1 USB Stick. All is looking good except for one issue which I have been unable to tackle. I noticed that the sensor state (48-1-0) of my Fibaro FGMS001 ZW5 sensor is not updating in zwave2mqtt even though I can see motion detection and cancellation events are coming in as expected (113-1-7).
I initially reported the issue in the zwave2mqtt repo here: OpenZWave/Zwave2Mqtt#621 but after further investigation it looks more related to OZW. After looking into the logs it turns out there are no COMMAND_CLASS_SENSOR_BINARY reports for this sensor registered. Below is the corresponding log. Node 7 is the Fibaro FGMS001. Node 4 is a Neo Coolcam PIR which is working as intended as does send COMMAND_CLASS_SENSOR_BINARY reports.
I hope this can be looked into and fixed if it's actually a bug. If not, please let me know what I'm doing wrong. If extra information is needed, please let me know as well.
The text was updated successfully, but these errors were encountered: