A polling of 2000 means that your system will be polling the state of your devices every 2 seconds. In a relatively large network this could generate some severe bottlenecks and render the whole system useless.
Is your installation working OK after applying these changes? How many zwave devices do you have?
I was afraid about it…
Yes, by reducing the value I checked the stability
Only 12 (few with battery) but the target will be max. 20 z-wave.
In addition, more than 30 other non z-wave devices.
This is a temporary solution. I don’t know how it affects devices with a battery (no changes visible after 24 hours).
Without tests there is no answer. 
edit:
There are few queries to other devices in the OZW_Log.txt. There are many to those with Polling Intensity setting = 1
Files home-assistant_v2.db and OZW_Log.txt still growing. 
This thread on the OpenZWave community forum provides some hints about this issue.
According to “Fishwaldo” on one of the last replies, there is something that needs to be done on HA side in order to make the FGR-223 report the shutter position correctly:
https://github.com/OpenZWave/open-zwave/issues/1705#issuecomment-473753978
Some solutions here and on Github suggest to poll the device to get an update on its position. But this is not working on my end. Polling only helps to update the position when the blinds are either fully closed or fully open. When I move the blinds to halfway closed (either by using the cover.set_cover_position service or manually by usind the physical switches) it never updates to position 50. It always stays at 100. Any help how I can get this fixed using polling would be highly appreciated.
So no news for this problem? Is this Fibaro problem or HA?
I need to buy some roller shutters, but do not want to buy an old version…
Hi all,
i’m a noob in home assistant and even more a noob in zwave.
I bougth myself a gen 5 usb stick on amazon and this fibaro roller.
I modified my electricity installation to include the node and adapted the configuration of HA to include zwave
I know that I need to pair both devices ^^
and I somehow manage to do that at least once, and then i could put up the roller but then the device is displaied as dead 
So i tried to remove it from it association (either in HA, either with a very long press on the stick and the 3 fast click on the B button of the fibaro)
I added a secure key in the option.xml file
and tried again to add my fibaro
when i add the device the log dispaly following information
https://pastebin.com/1gHwDxXg
as you can see I have some bullshit like
ERROR: Dropping command because node is presumed dead
I also copied/paste the the config settings bobsilesia gave but no more luck
Any idea ?
ps : I also tried a factory reset, the manual says long press on B until it change color to white, green, violet, yellow then release and click fast it should start blinking red after a time to tell it was reseted…
but mine goes white, green, violet, green and nothing happens …
The same manual said the calibration is done when release and fast click on white, … didn’t saw any calibration
just for info I bought a qubino model and manadged to make it work like expected. So it is this FGR 223 that is buggy, therefore I send it back to amazon…
Has anyone been successful to get the Fibaro Roller Shutter 3 with the newest firmware 5.11 running in Home Assistant? Incl. a correct position feedback? I have three of them with an old firmware and I’m wondering if it is worth it going through all the hazzle of sending it to the dealer to get a firmware update.
Hello,
I tested the same automation as mentioned by majstermod
Here are my findings:
I’m testing this second case, because I want to be able to change the position with my Google Home (via Hass.io)…
So now my current ‘working’ setup is without the suggested automation, but is polling the “cover.fibaro_system_fgrm223_roller_shutter_controller_3_level” with a ‘Polling intensity’ setting of 10s. I know this is a sub-optimal ‘solution’…
Note that I got a quite thorough status update on the fibaro site:
But this forum is probably the better place to discuss this…
Best regards,
Bart
Hi,
Same issue here. Seems to be a known and reported issue in HA:
I created my own work-around based on the work-around mentioned by LooSik on the open Zwave Github page. It consist of 3 automations. Firstly an automation that starts a polling automation as soon as the cover starts drawing power:
- id: '1558164709864'
alias: cover_study_start_sampling
trigger:
- above: '0'
entity_id: sensor.cover_study_power
platform: numeric_state
condition: []
action:
- alias: ''
data:
entity_id: automation.cover_study_sample_status
service: automation.turn_on
Secondly an automation (enabled by the first automation) that polls the cover every 2 seconds:
- id: '1558123485015'
alias: cover_study_sample_status
trigger:
- platform: time_pattern
seconds: /2
condition: []
action:
- data:
entity_id: cover.study
service: zwave.refresh_entity
And finally an automation that stops polling automation 5 seconds after the cover stops drawing power:
- id: '1558165456495'
alias: cover_study_stop_sampling
trigger:
- below: '1'
entity_id: sensor.cover_study_power
for: 00:00:05
platform: numeric_state
condition: []
action:
- data:
entity_id: automation.cover_study_sample_status
service: automation.turn_off
So far this seems to work for me. The slider moves (in 2 second steps) while de cover is moving and is at it’s final position maximum 2 seconds after the cover has stopped moving. I’m (so far) not experiencing any (zwave) network issues, but that network at this momoment is only a z-wave stick and this one fibaro module. I’ll soon add 3 more same modules with the same automation. I’ll see if it then still works well.
Which firmware version is installed on your Fibaro Roller Shutters?
@ffm777, not sure if that question is for me or not.
I do not know what firmware version is installed in the Roller Shutters. I do not have a Fibaro hub. I run Hass.io (on a rpi obviously) with a Aeotec Z-stick gen5. I do not know how to retrieve the firmware version from of the roller shutters with that. I’ve looked at several places like the OZW log, the entity attributes, zwcfg_0xxxxxxxxx.xml, but cannot find it. Any hint were to find it would be appreciated.
When I ordered the Roller Shutters online, the supplier called me and asked if I owned a Fibaro hub. If not they would update the roller shutters to the latest FW version for me before shipment. That would mean that they would have to open the box and they also wanted to know if I had no objections to that. Great service! That was on 1st of May. So, I assume that have a FW version as per 1st of May.
Then you are on the latest firmware version 5.11. That probably explains why a refresh entity call does give you the proper position of the shutter. I bought my Roller Shutters back in January and they have a very old firmware. In order to get them updated I have to uninstall them and send them to the dealer. Which is a pain. But most likely this is the only way to get them working properly…
Well, ‘working properly’… I think it’s still somewhat of an ugly work-around. But at least it works indeed. I still have hope that the last bit is HA issue that can be solved with a roller shutter update.
If your dealer is willing to perform the updates for you, is he not willing to lend you a Fibaro hub so that you can do the upgrades yourself in your own home without having to unmount them? Probably easier/faster for you and for him.
I don’t think so. In general, it is completely annoying that most manufacturers provide firmware updates only through their own hubs/gateways. Therefore, from now on I will only buy devices which can be updated without a proprietary hub. Like the Shelly devices which can simply be updated over the Internet. I should have waited for the Shelly 2.5 modules instead of buying the overpriced and not supported Fibaro Roller Shutters. Maybe I will simply replace them with Shellys and sell them on Ebay. Not worth the hazzle.
I agree. It’s something I didn’t consider this when buying the fibaro modules, but I will next time I buy new home-automation hardware. I didn’t know the shelly modules, but they look very good at a very nice price. However, in general I prefer Z-wave or Zigbee above Wifi for these type of applications.
I never considered that as well. Well now I will.
Those Shelly 2.5 look nice. I’m with Plevuus though Wifi is not the technology of choice for me. But I’ll buy one of those and give it a run for its money. Well, if I can use them in Switzerland.
Why? Many experts claim that Wifi is the future for IoT devices. For me, Wifi is definitely much much more reliable than Zigbee. Z-Wave also works nicely, but devices are expensive. I see no real downside with Wifi devices. And Wifi is for sure future proof. Who knows what will happen to the other standards…
I just replaced one of my Fibaro Roller Shutter 3 with a Shelly 2.5. Works like a charm. Positioning works flawlessly and the correct position is shown on the slider. Couldn’t be happier. I think, I will replace all of my Fibaros with Shellys and sell the Fibaros.
(it goes a bit off-topic, but anyhow…)
I’m not an expert on the topic. I’m not sure which experts you are referring to, but keep in mind that many of these expert opinions you read on the internet are from people who have a certain business interest in a certain technology. To be open and honest with you, I do work for Hue/Philips/Signify. Here I’m expressing my personal view and experience as a consumer. Another thing to keep in mind when reading the expert opinions is that they often trying to predict (or influence, as mentioned above) where the market is moving towards. That does not necessarily have to be the best technical solution.
On the future proofness, I think it’s wise to assume that the protocol/product/service of your choice at some point will cease to exists. No-one knows what the future of IoT looks like and I personally wouldn’t trust anyone who claims he/she does. I also feel confident that widely adopted non proprietary ones (Wifi, Zigbee, Z-wave) are here to stay for at least quite some years. That is also why Home assistant is so great. It ties it all together regardless of protocol or vendor.
There are 2 main reasons why at this moment I prefer Zigbee or Z-wave above wifi for home automation applications. Zigbee and wifi are mesh-networks while wifi is not. That should make them more robust and reliable. That is also my own personal experience at home. The second reason is the power consumption. Zigbee and Z-wave nodes consume significantly less energy than wifi nodes. That is especially interesting for battery operated devices, but I think also for mains operated devices. They are on 24 hours/day 365 days a year. It all adds up. In my home I have ~38 connected devices (mostly Hue of course) and that number will grow. (They use Z-wave, Zigbee, Wifi, Somfy IO (ugh) and Arlo proprietary low energy wifi. Really like HASS :-)) I also like the idea that there is an extra layer of security between my modem/wifi-router and my lights, roller shutters, etc. (although that could also be achieved by have separate modem and wifi-router or having multiple wifi-routers)