Fibaro FGMS-001 not working correctly

[phant0m3]

So I got myself a new Fibaro multi-sensor FGMS-001 with firmware version 3.2

Unfortunately both HA and open-zwave does not seem to identify the device properly (says something about generic sensor and product id 001 or something of that sort).

I tried the fix from another thread where you update the xml (fgms-zw5.xml) and change productid 0801/1001 and 0801/2001 to those particular files but still no luck.

Anyone got any idea how to get the device recognized properly in HA or open-zwave?

(right now it says binary sensor in HA but no data gets picked up)

[sebk-666 (Sebastian)]

I also have the 3.2 version and it worked out of the box with HA, i.e. no changing of any xml file was needed.
It took a while for all the sensors to show up, but you should end up with about 9 individual sensors.
Here’s how I grouped them:

name: 'Fibaro FGMS-001'
entities:
  - binary_sensor.fibaro_system_fgms001_motion_sensor_sensor_8_0
  - sensor.fibaro_system_fgms001_motion_sensor_alarm_level_8_1
  - sensor.fibaro_system_fgms001_motion_sensor_alarm_type_8_0
  - sensor.fibaro_system_fgms001_motion_sensor_burglar_8_10
  - sensor.fibaro_system_fgms001_motion_sensor_general_8_0
  - sensor.fibaro_system_fgms001_motion_sensor_luminance_8_3
  - sensor.fibaro_system_fgms001_motion_sensor_seismic_intensity_8_25
  - sensor.fibaro_system_fgms001_motion_sensor_sourcenodeid_8_2
  - sensor.fibaro_system_fgms001_motion_sensor_temperature_8_1

It may speed up the process if you wake up the sensor via a short button press.

The temp/luminance/seismic should be self-explantory; the burglar sensor is “3” for tampering and “8” for motion detection.
I have no idea what the others do - the first one (binary_sensor…) is sometimes “on” (for hours/days) and “off” at other times.
I’ve never read anything from the remaining sensors.

Sebastian

[phant0m3]

Thanks sebk-666 for the feedback, good to see that someone has a working version.

What kind of z-wave controller are you using?

I have a feeling that it might be my controller that is causing this if the sensor should be working out of the box.

(FYI i am using the AIO version of HA)

[sebk-666 (Sebastian)]

I’m using the Aeon Labs Z-Stick Gen5 with HA running inside a Docker container.

Sebastian

[cpc1027]

Did you ever get this figured out? I’m having the same issue - the sensor shows up in openzwave, but nothing at all in HA at the moment.

[phant0m3]

Unfortunately I never got it working, does your sensor show up with product information (like fibaro) or just a generic sensor?

I added my sensor to HA by issuing the add device command directly in HA (under services - zwave - add node) but since its not recognized properly the sensor shows up in the HA dashboard but no data is ever collected.

[cpc1027]

No, mine doesn’t show up at all in HA - not even as a generic sensor. I added it in openzwave so I could use the “add secure node” feature. Openzwave is reading everything correctly, but it isn’t communicated to HA at all. Hopefully there will be a future update that gets HA on the same page with the new Fibaro firmware.

[sebk-666 (Sebastian)]

Did you check that the zwave options.xml is the same for both, hass and ozwcp?
If you added the sensor securely and the network keys do not match, you won’t be able to see it.

Sebastian

[Tyfoon]

I have this sensor working in HASS for some time.

did you check out this:

Unable to add Fibaro multi sensor [solved]

Thanks to some helpful advice I have taken the plunge and moved from a docker image to a Raspberry Pi 3. I used the all in one installer which seems to have worked perfectly so have now added a z-wave ZME_UZB1 stick this one and planned to use a Fibaro FGMS-001-ZW5 sensor. I can run the OZWCP and initialise the USB stick, and as far as I can see there are no errors in the log. However when I try to add the fibaro with either option (secure or normal), it seems to just sit there waiting - OZWCP …

[cpc1027]

I believe so. I have the same network key in options.xml in both “/srv/hass/src/python-openzwave/openzwave/config” and “/srv/hass/hass_venv/lib/python3.4/site-packages/libopenzwave-0.3.1-py3.4-linux-armv7l.egg/config”

[cpc1027]

I didn’t see that one, but I seem to have the same setup as described in that thread, and I’m not still getting anything. I saw the suggestion to switch to binary reporting from basic, but I don’t see any option for that in OZWCP.

[sebk-666 (Sebastian)]

The Fibaro doesn’t have the option to switch to binary reporting.
What kind of controller are you using? As I wrote earlier, I’m using the Aeon Labs G5 ZStick which worked out of the box.
Maybe someone with the same combo as you might weigh in.

Sebastian

[Tyfoon]

I think (but can’t check) that you need to add as non-secure device. I have tried secure for devices that support it but never had success with that.

If added non secure there is a field for reporting in OZWCP for that device under configuration. This needs to be set to basic.

[cpc1027]

I’m using the Aeon Labs G5 ZStick too

[phant0m3]

On a sidenote I am using the zwave.me UZB stick, not the AEON Labs stick.

cpc1027 what does the sensor look like in open-zwave web interface?

By any chance did you buy this sensor in the past 2 months or so?

[sebk-666 (Sebastian)]

@cpc1027

I’m using the Aeon Labs G5 ZStick too

Then it should definitely work. Maybe try including the sensor via the ZStick’s button.
If that doesn’t work, try a factory reset with the stick and the sensor as well.
The sensor can be added non-securely and securely - I tried both methods and both work.
Re-adding the sensor one way or the other increases the device number, though, so you’d need to update all the references in your hass config.

Sebastian

[cpc1027]

Yes, I bought it last week (I’m just getting started with HA). Here’s a screenshot of some of the OZWCP. If there is something specific that you wanted to see, let me know and I’ll get it in the frame. Right now, I have the manufacturer.xml files for both openzwave and hass pointed to the updated fibaro configuration xml file posted in the other thread, but neither the update or the original seem to have made a difference.

[Tyfoon]

This also looks good. Basic command class is set to Basic. So that is not it.

[cpc1027]

I ran into this problem the first time I tried to include the sensor and thought I screwed something up, so I factory reset everything and tried again, which is where I am now. I can’t say for sure that I tried all of the same steps the first time, but I’ve been trying every potential solution that I can find since the reset.

[cpc1027]

I was poking around the zwcfg_*****.xml file that seems to be generated by HA, and I noticed that the information for “node 2” (my fibaro sensor) is considerably shorter than my lightbulb. I don’t really have any idea what this means, but it seems like a more complex sensor like the fibaro would have much more information associated with it. Does this spark any ideas about what might be going on (note that I still don’t have a sensor listing for this in HA’s state listing)? This is what is I have for node 2:

</Node>
<Node id="2" name="" location="" basic="4" generic="7" specific="1" type="Notification Sensor" listening="false" frequentListening="false" beaming="true" routing="true" max_baud_rate="40000" version="4" query_stage="Dynamic">
	<Manufacturer id="0" name="">
		<Product type="0" id="0" name="" />
	</Manufacturer>
	<CommandClasses>
		<CommandClass id="32" name="COMMAND_CLASS_BASIC" version="1">
			<Instance index="1" />
			<Value type="byte" genre="basic" instance="1" index="0" label="Basic" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="0" />
		</CommandClass>
		<CommandClass id="132" name="COMMAND_CLASS_WAKE_UP" version="1" request_flags="2">
			<Instance index="1" />
			<Value type="int" genre="system" instance="1" index="0" label="Wake-up Interval" units="Seconds" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="3600" />
		</CommandClass>
	</CommandClasses>