Roller Shutter 3 Position Issues

[lharmon 0]

I am having an issue with the new Roller Shutter 3. Installation and inclusion into the HC2 was easy ans straight forward. Calibration also completed successfully with a time to 99% of 21.6 seconds and a time to 0% of 19.4 seconds. The up and down commands function via switch and app as they should. Problem being is that a position of other than 0 or 99 percent is not possible. The shutter does not stop on the selected position via the app or web interface. Any ideas as to what I may be doing wrong? 

[Krikroff 199]

Hello,

 

have you tried to position using a lua command for example at 50%

[petergebruers 1,265]

@Krikroff thank you for chiming in. I'd like to cross reference this post, no solution yet, but might be related.

 

 

[Krikroff 199]

@petergebruers, thank you I missed the discussion you are referring to.

[lharmon 0]

YES!! that worked. I should have tried that earlier. Thank you. So, what would hinder it from working in the app or web interface? One note: the shutter goes all the way down and then up to 50 percent.

Edited January 12, 2019 by lharmon

[Krikroff 199]

Good if it works with lua! BUT...

 

If you have tried many times calibration process with the same results, this behavior is very curious.

It's hard to know if it's a problem with your module or perhaps incompatibility between the RollerShutter and your VR (I suspect that rather).

I recommend you to send an email to Fibaro support team and open a ticket.

 

Best regards

[lharmon 0]

Thank you for the uick response. I have tried the support route already. Actually, both the European English speaking email and the German support channel. I received a copy and paste of the reset process for the module (had already tried that) from the English speaking support and nothing yet from the German side. I will try again on Monday. One quick question though; what is a VR? I am new to Z Wave (coming from Homematic).  

[Krikroff 199]

VR = Roller shutter = Rollladen 

Yes it is one of the things to try to do a reset of the module... But I'm thinking of one thing, did you try to fix yourself the opening and closing times? for example: 10 seconds to go down and 12 seconds to go up

 

[lharmon 0]

No difference. The rollladen still goes to either 0 or 99 percent. Why would it be an incompatibility issue with the rollladen? They endpoints are recognized by the switch otherwise it would not set the time up and down during the calibration process correct? 

[Krikroff 199]

yes you are right, but the module may take too long to detect the stop of the VR and thus the calibration would be incorrect. This is only a suposition, of course.

[lharmon 0]

I thought the same also. I timed it with a stopwatch and the time was close to what was annotated in the controller. The time was also very close to the numbers that were used with the Homematic device that it replaced.

[petergebruers 1,265]

But using Lua to set it to 50% always works, right? And the physical buttons work too, right? It's the slider on the browser and app that don't seem to get you an intermediate position? Then I would say this is a "User Interface bug".

 

@Krikroff and I cannot test this for you for a weird reason: our fw version as different and we do not have exactly the same UI...

 

Does your browser show multiple slaves? And does one of them work?

[lharmon 0]

Lua works, but not well. If the Rollladen is in the up position, I can run the script and the Rollladen will initially go to compleely closed. If I push it again, it goes to the desired posiion. If the initial position is completely down, the rollladen will go to completely open on the first script run, then completely closed on the second script run and then to the desired position on the third run. I personally believe it has something to do with the firmware of the HC2. Is there some sort of tracelog or tool that can be used to capture the traffic sent to the device from the HC2 controller?

[petergebruers 1,265]

Indeed, what you describe is not normal and should not happen.

 

It sounds as if the direction of movement does not match the 0-99 slider.

 

Have you toyed with the parameters to swap input, output, or both?

 

The HC2 stores a detailed log but it is not user accessible. Only support can access them.

[lharmon 0]

Yes, I have attempted to swap the direction in the parameters and with the physical wires. I was able to find the logsdump.php. Unfortunately it seems that you are correct. Fibaro has removed any of the logs that would assist in something like this.

[petergebruers 1,265]

Yes, that is why I did not mention that script.

 

I am running out of ideas. Maybe try mode 5 "roller blind with built-in driver".

[lharmon 0]

I have set the parameter to mode 5. It now works with the app, lua and the web interface. The momentary switches are no longer working properly. I have to hold the switch in order for the blinds to move. I believe there is really something wrong with the current Home Center firmware.

[petergebruers 1,265]

While still in mode 5...

• Does a very short click (< 250) ms fully engage the module in up or down direction?
• Is the center of the up/down switch really center? Can you check with a multimeter?

Switching back to operating mode 1, can you try to double or halve Parameter 155. Motor operation detection. Settings: 0 - reaching a limit switch will not be detected; 1-255 = 1-255W. Default is 10.

[lharmon 0]

In mode 5 a vey short click does send the blind into a fully up or down position. I am using a double momentary switch one is up and one is down. The setting in parameters has been set to match. Tested with a volt meter, they are spring loaded in a normally off position. No voltage when off.

 

Back to mode one, i have tried 5, 10, 15, 20, 5, 30, 50 and 135 watts. No differance. The correct up and down times are always recorded in 156 and 157.

[petergebruers 1,265]

Ok, thank you for trying that. @Krikroff and I are trying to get in touch with Fibaro but no answer yet. Busy time of the year... CES, new app, people upgrading to 4.530 because of the new app.

[lharmon 0]

Thank you!! For reference, I do have a support request in to Fibaro. The Case ID is 156275.