Fibaro FGMS-001 still not working on R090

[Gaz]

Has anyone managed to get a Fibaro FGMS-001 multisensor (Zwave plus version) working?

R090 update notes mentions adding support, but i have so far failed to get my devices working fully with it (i still don't get motion sense from the sensor- although lux and temperature work).

The sensors i have use firmware V3.2, I have confirmed correct operation of the devices on anouther Z wave controller.

[Ashok]

@ Gaz,

Has anyone managed to get a Fibaro FGMS-001 multisensor (Zwave plus version) working?

R090 update notes mentions adding support, but i have so far failed to get my devices working fully with it (i still don't get motion sense from the sensor- although lux and temperature work).

The sensors i have use firmware V3.2, I have confirmed correct operation of the devices on anouther Z wave controller.

Remove the sensor and add it back, wait for 1 minute and then press the pairing button 3 times and then wait for at least 2 minutes, check the performance.

[andersos]

I'm planning to get this multisensor, but I wonder how it can be used in Almond+ rules. Can I set a light to be on when ambient light goes down to a certain level?

[mparadis]

Remove the sensor and add it back,

For this part make sure you put the almond into remove mode (not remove all) and then put the Fibaro into exclusion mode (which is sometimes the same as inclusion mode) and then follow the pairing procedure.

[andersos]

I got this same multi sensor today. I paired it with the Almond+ and it shows the three supported measurements.
But I think there's something strange with the lux measurement. It takes almost one hour until the lux value changes
when I test by changing between completely dark and full light in the room. Or is that normal behavior?

[andersos]

Ok I noticed the device history list. After removing and re-adding the sensor, last couple of tests the time for registering
change in lux have been 30 and 35 minutes. Doesn't seem normal to me. 

[Ashok]

@ andersos,

Ok I noticed the device history list. After removing and re-adding the sensor, last couple of tests the time for registering
change in lux have been 30 and 35 minutes. Doesn't seem normal to me. 

Please do send the logs with the description "Logs for Ashok".

[andersos]

I'll send the logs when I get home. Just want to mention that last night when I was going to sleep I noticed that a change to 0 lux was apparently registered
immediately. This seems to happen really intermittently. Motion is always registered  immediately in the device history though.

By the way, is it possible with a rule to have the Almond+ turn on a light when motion is detected and lux is below a certain value, and then if motion isn't detected
within a certain time period have it turn off the light?

Also Ashok, if you could answer in this thread too https://forum.securifi.com/index.php/topic,5367.0.html

[mparadis]

By the way, is it possible with a rule to have the Almond+ turn on a light when motion is detected and lux is below a certain value, and then if motion isn't detected
within a certain time period have it turn off the light?

Not with one rule, this would require multiple, unfortunately it doesn't work perfectly.

[andersos]

Too bad. This was one thing I imagined to do when I bought the sensor.

[andersos]

@ andersos,

Please do send the logs with the description "Logs for Ashok".

I sent the logs and described them as you requested. There was a lux entry in the device history at 06:33 this morning. The light was turned on by an Almond+ rule at 06:00.
So this time it took 33 minutes to register.

[Ashok]

@ andersos,

We are updating the Lux value for every one hour, if the value is less than 200 and if the value is more than 200 then, it will be done immediately.

[andersos]

@ Ashok

I see. That is not really optimal for my use here in the north. We have winter now, so the days are more often pretty dark.  For example today the highest lux value was 142
when it was middle of daylight time of today (no lamp was on).  And as we get closer to summer the daylight interval will get longer every day and lux values will get higher as we get more sunlight. I want to control lighting based on the lux value, so with the daylight conditions we have here I would want more frequent updates of the lux value. The higher the update frequency is, the better for me. With the time of sunrise and sunset moving all the time and faster the closer we are to summer, I would want lux updates at least every minute for precise control. I don't know what's practical for you though.  Can it be done?

Also see my previous post about Almond+ rules. Can the rules system be developed further so something like that can be accomplished? 

[Ashok]

@ andersos,

I would have to check, once we upload the file which would give the ability to change the parameters, it could be possible. Yes, we would keep working on adding more support for Rules and other Home Automation system features.

[andersos]

@ Ashok,

That would be even better, if we could set those parameters ourselves.  I hope that the file is uploaded as soon as possible. And it's great to hear that the Rules will be enhanced further.

Also, I saw on some other forum that Fibaro apparently publish firmware updates for their newer sensors. Would it be possible with some changes in the Almond+ to have it update Fibaro sensor firmware?