Regaring Callibration - that is done within the Fibaro itself - just refer to the manual of fibaro after the installation:
For the Fibaro Shutter 3 FGT-223 @SW 5.1 is already the parameter 151 set.
A great thank for your time @phil2000 . I haven’t done any calibration for now maybe that why I have problems ( I really hope it’s that ).
I’ve discovered in HA the 151 parameters but it’s not coming with numbers but with blind type.
Another things is in the calibration setup they talk about momentary switches which is not my case. I will try to put my switch down for 3 seconds then stop and so on … (Sorry for my English , I’m French with poor vocabulary)
Hey there - Parameter 151 is not coming for me in HA either. But if you have recently bought the shutters this should be set with SW Version 5.1
Another things is in the calibration setup they talk about momentary switches which is not my case. I will try to put my switch down for 3 seconds then stop and so on … (Sorry for my English , I’m French with poor vocabulary)
Hmm I don’t 100% get it. You need to go to your physical wall switches and press it for 3 seconds, release, press again for 3 seconds, release, press again for 3 seconds. Be very precise about the 3 seconds - as first I was pressing it not long enough - I used a stop watch to be 100% sure - that worked. As soon as the Shutter gets into calibration mode the shutter stops shortly, then fully opens, then fully closes and then fully opens again - and boom you are calibrated.
You could also set it via value - but I guess for setting this you would need a fibaro base station:
I’m encountering the position problem. I think home assistant is updating the position too early, without waiting for the engine to stop. It is not possible to fix this other than by an automation?
Whats exactly your issue? In the latest release I do not have any issue with it.
Are you talking about the firmware of the module or the home assistant version or the hassOS version?
~ $ ha os info
board: rpi3
boot: A
version: "3.13"
version_latest: "4.8"
~ $ ha core info
arch: armv7
audio_input: null
audio_output: null
boot: true
image: homeassistant/raspberrypi3-homeassistant
ip_address: 172.30.32.1
last_version: 0.110.4
machine: raspberrypi3
port: 8123
ssl: false
version: 0.110.4
version_latest: 0.110.4
wait_boot: 600
watchdog: true
I can’t switch to HassOS 4.8 because of a problem with the Razpberry.
I was talking about the hass.io version. Nevertheless I run version 5.1 in the fibaro device and latest stable hass.io & hass os.
My fibaro module’s also in 5.1. I’m using the latest version of hassio, but the open/closed status doesn’t come up correctly.
I had to set this automatism (sorry for the french):
- id: '1591286478123'
alias: 'FIX : volet roulant'
description: ''
trigger:
- entity_id: sensor.volet_garderobe_power
platform: state
to: '0.0'
condition: []
action:
- data:
node_id: 47
value_id: '72057594831273985'
service: zwave.refresh_node_value
1 Like
Thank a lot @phil2000 for pointing at me the calibration sequence. Now I can set a position without any problem. I only have like everyone the problem that the final position is not correctly updated in ha.
I will try an automation to solve that.
Hello @pulsar and thanks for sharing. Where did you find the ‘value_id’ in the ‘action’ part of your automation ? Is it always the same for all node ?
Hello,
I don’t know if value_id is the same of all node, but I think it is. I haven’t motorized my second shutter yet.
In the developer panel, like that :
In addition, I don’t have a physical switch. I have done the calibration by forcing it via parameter 150.
I don’t have a key in the zwave section of configuration.yml.
All my zwave modules were added in secure mode.
It seems that I don’t have any ‘level’ entity, but only ‘alarm_level’ entity. What is that ? Does I have to redo something to have it ?
And also, where do you check the firmware version of your module ?
Good evening
Hope I am right here, I have included my Fibaro Roller Shutter 3 to hassio. All works fine. But now I would like to make some automations with my weather station. Now I have the problem that I cannot write, ore chose, something at the point “action” of the automation. See also the attached picture.
I cannot choose something at the “position”. How I can give there a target like 100 % or 0 % or close / open?
Thanks for your help
You need to use the call a service function as used in my post above:
Thereby you need to use the basic service for cover close / position from HASS.IO
You see firmware version if you go to the z-wave menu in preferences in HASS.IO, then select a node and click on node information.
You can also use a Fibaro Hub to check FW version.
I do not have one, but I read that there are issues if you do not have Firmware 5.1.
Nevertheless there is also a workaround available:
I contacted my store and asked which version they sell and got the 5.1 confirmed.
Regarding the alarm Level - I have this in the entity list as well. And some more:
Hey Phil thank you very much for these information
About the firmware. Before I changed to hassio, I had a homee. There, the automation had works fine. And I remember that the firmware was higher than 5.0. If I look in hassio, I also have the 5.01 firmware.
The test with your script has worked. Now I am very tense if it works also with the real trigger. The integration of my weather station was one point to change from homee to hassio. Now, if I done this automation, it is open a second question. Do you know if I can also choose this setting with the call service to definite the conditions trigger? I mean, in moment I have definite these with the device and the condition open or close. But over the call service it would work also for roller shutters which are not full closed or opened. Hope you understand it. If not, I am come from the German Swiss.
Best regards and thanks a lot.
You can edit as yaml and add position: 90 to activate the position bar in UI mode. I think is a graphical bug on the UI.
Do you know if I can also choose this setting with the call service to definite the conditions trigger? I mean, in moment I have definite these with the device and the condition open or close. But over the call service it would work also for roller shutters which are not full closed or opened. Hope you understand it. If not, I am come from the German Swiss.
Best regards and thanks a lot.
Not really sure what you mean. You don’t need to set any condition. When you call a service it will either set open, close or position no matter what current state the shutter is.
Thanks again and again Phil. I’ve seen in your screenshot that the number is 5.01 (it’s the same for me) but you told about 5.1 firmware version. Is that the same thing ?
I’ve tried the automation you provide from this thread to update the progression. But there is something weird in the module, I can hear it push it the power on and off multiple times after the correct level is reached… With this I can see the level bar on the UI moving till the right position but I’m worried with the module so I desactived it for now.