Either the entities weren’t correctly created when the integration read the Z Wave JS devices or it is not supported for the FGR-222 (I have the FGR-223 actually). Sorry, can’t test that…
Well I am desperate … I am trying to change to home assistant from domoticz but in ha it is impossible for my fibaro fgr223 to work well. At domoticz, both scenes and level bars were working to perfection. After all the work of integrating all my blinds (9) I will have to go back to domoticz since everything worked great there. My problem here is that the devices do not update their status and I have tried some of the automations that are in the forum but they do not work in some nodes … I have the latest version of ha, zwave js and a razberry2 card as a driver. There is still no solution, right?
Not sure what you mean - I have the FGR223 (Roller Shutter 3) with Z-Wave JS and it works just fine, including correct info on current position of blinds and slats.
I was underestimating the FGR223 - you actually don’t have to wait for the blind to reach the desired position and then set slats, it does work if both positions are being set at the same time. The controller appears to adhere to the desired slat position and does not revert to the previous position before setting the new one.
zw_setcover:
alias: Z-Wave Set Cover
icon: mdi:window-shutter
description: 'Z-Wave Set Cover with Slats'
mode: parallel
sequence:
- service: cover.set_cover_position
data:
entity_id: "{{ zw_setcover_coverent }}"
position: "{{ zw_setcover_coverpos }}"
- service: cover.set_cover_position
data:
entity_id: "{{ zw_setcover_coverent }}_2"
position: "{{ zw_setcover_slatpos }}"
This only works when the entity name for the Slot is the same as the primary shutter with a trailing _2.
I have written a script that is valid for me because where I use the FGR 223 I only act through scenes and we rarely act on the switch. The first day I despaired because I thought it would be easier after a week with HA I am loving it. Everything works fine now.
Hey Daniel,
I‘m currently setting up the FGR223 and are really happy with your suggestions here in the forum.
So far, everything works fine except the tilting of the slates.
I configured it as you stated - chose Operation mode„Venetian blind“, then did a calibration.
However, I don‘t see a new entity for the slates.
When I save your script, I get the error „Message malformed: extra keys not allowed @ data[zw_setcover].
Any hint would be greatly appreciated 
Can you post a screen shot from the device page under settings, showing all entities?
In the meantime I noticed, that two switches for every fibaro controller appeared on my iPhone in the Home App. (I have the Homekit Integration installed HomeKit - Home Assistant).
The one labeled with (2) actually controls the slate position:
However, when I add the Entity “cover.jalousie_badezimmer_fenster_2” to my Home Assistant Dashboard, I only get the following control:
(Sorry for the three posts, new users can only upload one image per post) 
Looks good to me: The first cover. entity controls the up and down position, the cover.xxx_2 controls the tilt position.
If manually setting those works you can use the script targeting the two entities to set the position and tilt with one service call with the corresponding parameters.
For the UI I use two sliders:
…but there might be more elegant ways to do it in one line / element.
Thanks for the explanation. I think I understand now how the tilting works 
Do I understand correctly that these two sliders in your card control the numbers inserted in the variables of your script?
Can you paste the code of that card so I can use it?
I never created a custom card and don’t quite get how to build one to trigger your script.
Sure, here’s the coe for the card:
title: Beschattung EG
type: entities
state_color: true
entities:
- entity: cover.raff_kuche_fenster
- type: custom:slider-entity-row
entity: cover.raff_kuche_fenster
hide_state: true
name: Position
icon: mdi:empty
- type: custom:slider-entity-row
entity: cover.raff_kuche_fenster_2
hide_state: true
name: Lamellen
icon: mdi:empty
- type: divider
You only need the custom slider which you can install via HACS. You can of course use any other UI element to set a number to the target entity.
When you then use the slider the cover entity gets set directly, you don’t need the script for this. So if you want to set the blind you simply frist set the position slider (blind begings to move), then the tilt slider (info gets sent to the module and will be adhered to once target position is reached), and everything shoud work.
The script you need to call from automations / other scripts like this:
action:
- service: script.turn_on
target:
entity_id: script.zw_setcover
data:
variables:
zw_setcover_coverent: cover.raff_kuche_fenster
zw_setcover_coverpos: 0
zw_setcover_slatpos: 0
As stated above:
This only works when the entity name for the Slot is the same as the primary shutter with a trailing
_2.
…but that seems to be the case given the entities you’ve shown below.
1 Like
Wow, Works exactly how I expected 
Thanks so much for your help
1 Like
Well, I stopped having this problem several months ago, but with some of the latest zwavejs2mqtt updates I’m back to square one where the current level of my FGR-223 is not updated as it should.
me too … hoped the problem was gone forever
Hi there!
Is there any requirement to add the Fibaro RS to HA via Z-Wave JS and Aeotec 5?
I just unpair it successfully from smartthings but i cannot pair it with HA…tryied 20 times and nothing.
Even reset the fibaro to default and nothing.
Is there any advice or trick?
Thanks!
No - set controller to pairing mode (if you have problems try without S2), then click UP or button of module 3x quickly. Full reset via internal button if your not sure about the state of the device.
Have you tried a full re-interview?
I have the fibaro 8 meters away from my HA.
I tried all the 3 different strategy’s (secure if possible, insecure and legacy secure) to pair it and nothing.
It pairs with ST without any problem, even after the reset (yellow light) i cannot pair it to HA. Its driving me crazy!!