![]() ![]() See what commands you get logged, if any, and report back.Ĭan you install This beta of my Scene Controller plugin - purely as a place to put the testing code for now! To pause or stop the logging of these commands, just disable or delete the ZWave Watcher device and leave the plugin installed - you can use it for other zwave debugging in future. Now play about with your blinds and remote - the log will show the raw zwave command for any command received from those two nodes, rather than (with normal debug on) absolutely every zwave command. You can then turn off Zwave Debugging as it fills the log with tonnes of data. Unless you already know exactly where the blind is positioned, and you can time accurately how long the button was held down for, you're not going to accurately set the position of the blind.Ĭan you install my new ZWave Watcher plugin from here, then create two ZWave Watcher devices and select nodes 2 and 3 (Blinds and Remote). This is the same commands as say a Zwave dimmer lightswitch where you hold the up/down button for as long as you want the light to dim for, then let go when it's at the right brightness. ![]() The two commands you've shown are, in English, "The down button was held down" then "The down button was released" (or the Up button they're labelled buttons 1 and 2 in the command, but not sure which is which for your remotes). Ok, so the zwave debug log you've provided isn't going to help us achieve what you want at this point. Z-Wave received "Primary Remote Office Blinds " scene 259 sceneActivateCmd2: node 003, type: 1, scene: 3 Z-Wave received "Primary Remote Office Blinds " scene 515 sceneActivateCmd2: node 003, type: 2, scene: 3 Z-Wave Indigo Device "Primary Remote Office Blinds " Z-Wave Properties:Ĭommand Versions: 20v1 80v1 84v2 85v1 86v1 72v1 73v1 59v1 5Av1 5Bv1 5Ev1 I just assume they are up if not sensed down.Z-Wave Indigo Device "Blind Office Entrance" Z-Wave Properties:Ĭommand Versions: 20v1 80v1 25v1 26v4 72v1 73v1 5Ev1 59v1 5Av1 7Av1 86v1 85v1įeatures: routing, battery, beaming, frequentWaking I have considered adding sensors for "up" but even for my crazy overkill, that would really be overkill. It all works really well-I now at least know when shades are down, which is very useful. So, I then purchased some clear polycarbonate tubing ( ), cut it into small cylindrical segments, and then cut some of those in half long-ways to make small semi-cylindrical "dome-like" covers for the magnets-a smooth curved covering to make the magnets stand off from the wall a little. The magnets are so strong though, that they will pull the shade bar against the wall when it's raising/lowering, because there are metal "corner bead" pieces behind the drywall (standard means for protecting drywall corners from damage). For the doors, the shade would sometimes float away from the sensors and not trigger the sensors, so for those I installed some larger, very strong, Neodymium magnets ( ). For my windows, the magnets that shipped w/ the sensors worked fine. I mounted them so that they could be slid sideways a little to remove them from the mounting plate for recharging. ![]() I attached the magnets to the back side of the trim bar at the bottom of the shade, and mounted the sensor units at the point where the bar stops, e.g., on the window sill (window shades) or on the door frame (door shades). I was hoping to live with the RTS-I will.įWIW, I installed Aeotec Z-Wave "Door / Window Sensor 6" sensors ( ) on each shade, to detect when it is down. Somfy does make at leasts one motor model that supports a Z-Wave interfaces, status messages, etc., but the rollers are larger than mine at the moment, etc. I'm a little bummed that I did not see that earlier, but more bummed that it doesn't receive Somfy RTS commands. ![]()
0 Comments
Leave a Reply. |