We have just recently installed around 15 of the Micro Open/Close Modules at a Clients home. The Modules have been set up using the Calibration Assistant in the IOS App ( iPad Mini)
The Modules are controlling curtains and Blinds via either the App or from various 4 Scene Mini Remotes
Eg
Mini Remote 1 controls
Button A = Curtain 1 (up arrow for open, down arrow for close)
Button B = Curtain 2
Button C = Curtain 3
Button D = All of the above
And so on for the other curtains and Blinds. The scene for the Mini Remotes was created using the IOS App.
The existing Hub is a 2245 Hub 2
Our problem is...
When testing the individual scenes on the Mini Remotes all works fine including the All scene as in button D, however, the next day the blinds seem to have changed where the want to stop in relation to a open or close command. Some blinds will go to approx 50 %, and stop consistently at this point. Others will go to approx 5 % and consistently stop at this point. When using Button D (All blinds command), usually 2 blinds will start immediately and the 3rd will lag by a few seconds. We put this down to traffic on the network?
If we open the Device Properties ( for the module), it is difficult to get an exact picture of what was calibrated, as the calibration time can vary each time we open the device properties. Generally we either get the App spinning it's wheels on this, or it quits the App entirely and has to be restarted.
Opening the Scene properties, we notice each button has been set similar to that of a Dimmer, whereby the Value = On at 0.1 Secs
The App version is 1.10.1 which is supposedly the latest version and I notice this was to fix a bug which sent erronious vales.
Has anyone come across a similar problem? We have sent a request to Insteon Support but not had a reply and wondering if anyone has had real world experience with similar.
The Modules are controlling curtains and Blinds via either the App or from various 4 Scene Mini Remotes
Eg
Mini Remote 1 controls
Button A = Curtain 1 (up arrow for open, down arrow for close)
Button B = Curtain 2
Button C = Curtain 3
Button D = All of the above
And so on for the other curtains and Blinds. The scene for the Mini Remotes was created using the IOS App.
The existing Hub is a 2245 Hub 2
Our problem is...
When testing the individual scenes on the Mini Remotes all works fine including the All scene as in button D, however, the next day the blinds seem to have changed where the want to stop in relation to a open or close command. Some blinds will go to approx 50 %, and stop consistently at this point. Others will go to approx 5 % and consistently stop at this point. When using Button D (All blinds command), usually 2 blinds will start immediately and the 3rd will lag by a few seconds. We put this down to traffic on the network?
If we open the Device Properties ( for the module), it is difficult to get an exact picture of what was calibrated, as the calibration time can vary each time we open the device properties. Generally we either get the App spinning it's wheels on this, or it quits the App entirely and has to be restarted.
Opening the Scene properties, we notice each button has been set similar to that of a Dimmer, whereby the Value = On at 0.1 Secs
The App version is 1.10.1 which is supposedly the latest version and I notice this was to fix a bug which sent erronious vales.
Has anyone come across a similar problem? We have sent a request to Insteon Support but not had a reply and wondering if anyone has had real world experience with similar.
Comment