What’s a PR9501?
Also, in my testing, I have found that if the switch does not know what a numbered parameter is (e.g., trying to set parameter #20), Vera will tell you it does not recognize that parameter number. So if the switch takes the value you set, then the switch would appear to support that parameter.
PR9501 is a typo… sorry called it two different things (so modified my post). It is the RF9501 The on/off (non-dimmer) version of the RF9540
OOPS…we x-posted. See my reply above (I edited it after your post).
Also, in my testing, I have found that if the switch does not know what a numbered parameter is (e.g., trying to set parameter #20), Vera will tell you it does not recognize that parameter number. So if the switch takes the value you set, then the switch would appear to support that parameter.I should say more about this......
If you attempt to set a non-existent 9540-N parameter with Vera, it doesn’t flag an error exactly; rather, on the main screen for that device, the phrase “Setting user configuration” is displayed in blue. Unlike when setting a valid parameter this phrase does not disappear until you delete the invalid parameter (sometimes you have to issue some valid command to the device first before it disappears…something like that anyway). This phrase will turn red eventually if you leave the main device page and then come back to it. Also, if you leave and then return to the “Device options” page, you will not see a “Current value” for that invalid parameter like one does for a valid parameter.
Is that clear as mud?? :-\
I am pretty sure it is a valid parameter, I “watched” the parameter first, before attempting to set it, and didn’t get any errors or blue notifications, (the default was 0), then I set it to 1, and again don’t see any ribbon pending actions or errors on the device and shows the set value as 1. Just doesn’t seem to be doing anything, I played around with it a bit and wasn’t causing the Aux switch to stay in sync. But when I left the house and ran my away scene I noticed it magically did sync, but didn’t have time to investigate it more. So maybe it started working after a few commands, or I was just seeing things. Will check more on it tonight.
shallowearth,
Let me know how this goes.
So far I have only tested the use of the 9540-N/9542-Z smart dimmer combinations for 3-way circuits; however, there are some circuits in the new house for which I don’t need dimming, but for which I want Z-wave “smart” functionality (I am using 9501 and 9503 switches for the “dumb” circuits). I presume I would use the RF9501/RF9517 combination for these smart circuits with the RF9501 as a master that is connected to the load, and the RF9517 as the slave in a 3-way circuit (with additional RF9517s if I need 4-way or 5-way circuits). Is that right?
[quote=“sgm, post:26, topic:183813”]shallowearth,
Let me know how this goes.
So far I have only tested the use of the 9540-N/9542-Z smart dimmer combinations for 3-way circuits; however, there are some circuits in the new house for which I don’t need dimming, but for which I want Z-wave “smart” functionality (I am using 9501 and 9503 switches for the “dumb” circuits). I presume I would use the RF9501/RF9517 combination for these smart circuits with the RF9501 as a master that is connected to the load, and the RF9517 as the slave in a 3-way circuit (with additional RF9517s if I need 4-way or 5-way circuits). Is that right?[/quote]
There is a max on the data store of IDs it can collect to Group 1. I think the max is 5, but 1 is used by the controller typically, so you have 4 others.
As for the single pole switches, I don’t have any in 3 way so I cannot comment on the parameter. I used to have a guide or email or something with all documented parameters most of which are already used by the controllers. I don’t recall any other useful “hidden” parameters.
OK, so here is the result of my investigation (I only tried one pair of 9501/9517’s).
If you put parameter 10 to 1 on the 9501 it will sync the Off command tot he 9517 but will not sync the On command. This is both if you send an Off to the 9501 from the Vera or if you send a Toggle to the 9501 and it going to off. On doesn’t work, I have no idea why,
So ultimately I removed parameter 10 from my 9501 and fell back to my current method of keeping my 9501/9517 in sync. You can do this by adding two simple scenes to your Vera. The first triggers off of the 9501 being turned on, you then use the advanced editor to also turn the 9517 on (you can’t do this in the basic editor but the advanced edit will let you send the z-wave On command to the 9517. I have noticed that this command does not appear right away when you add the 9517 to your network, after joining it to the network, let it sit for few minutes and then the command will appear in the available list in the advance editor). Then create another scene to trigger when 9501 is turned off, again add an advance action to turn the 9517 off. Since the 9501 support instant status, this will trigger the LED on the 9517 to be in sync usually in 1/2-1 second of controlling the 9501 form Vera or a Vera Scene.
By adding these two scenes you don’t have to remember to keep putting the 9517 in all your scenes to set it on or off, everything works as you would expect.
I suppose if you wanted to eliminate the need for the Off scene, you could add Parameter 10 to 1 on the 9501 and then you would only need the On scene since that one doesn’t seem to work.
All the 9501 that have have are version 3.3.52.3.15 so I don’t know if it is a firmware issue that only Off works, it could be that the Vera is sending the switch a different version of the On command than it is expecting to sync the On. My 9517 that I ran the test on was version 3.3.52.3.13 which is what most of my house has except for two which are on older firmware 3.2.40.1.13, didn’t try the test with those.
I will try out parameter 10 on my dimmer combo next. I have 3 dimmers but only one of them is paired with a second switch and of course the one that is paired is on an older firmware than the other two, so I am hoping it works!
For folks investing in Coopers they also make a matching battery powered switch which works great with both the dimmers and on/off switch, and doesn’t have a light that needs to stay in sync, which is awesome!
OK, tried Parameter 10 to 1 byte Hex 1 on my dimmer.
Worked great. No longer have to have any scenes or lua code to keep the auxiliary switch in sync, including on, off, and dimmer level.
Excellent!
Note my dimmer was version 3.3.52.1.0
shallowearth ,
I presume when you say parameter 10 works with your dimmers, you mean RF9540-Ns and RF9542-Zs, right? If so, then you are experiencing the same as I.
Have you had a chance to verify that parameter 10 works or doesn’t work with the RF9501/RF9517 non-dimmer combo? I would think if it works for the dimmers, it would work for the more simple on/off versions of the switches (I say “more simple” because the RF9501/RF9517 combo does not need to worry about sync-ing the dimmer level).
BTW, I have noticed in all these 1 byte parameters that setting them with a decimal number works just as well as with a hex number. The decimal numbers are a bit easier to monitor (i.e., seeing the number “11” instead of seeing “B”).
Finally, like wholm, I too have found some documentation on Cooper switch parameters, but everything I’ve found does not include parameter 10. The standard spec sheet that comes with Cooper switches, covers parametes 1 thru 7. I have found some HTML code that further documents parameters 8, 11, and 12. I have summaried all I have found into a text file. I will start a new thread posting all this information once I finish testing.
SGM from my previous post 9540/9542 combo works great with parameter 10.
9501/9517 does not quite work, it will only sync the “off” command, probably because the Vera is sending a SetTarget command instead of a SetLoadLevelTarget or some such.
However it is OK, you can just create a basic scene to keep the LEDs in sync on these. See my full post above or look for my post with Cooper Solved in it for the full instructions for creating the scene to keep the switches in sync.
[quote=“sgm, post:30, topic:183813”]shallowearth ,
I presume when you say parameter 10 works with your dimmers, you mean RF9540-Ns and RF9542-Zs, right? If so, then you are experiencing the same as I.
Have you had a chance to verify that parameter 10 works or doesn’t work with the RF9501/RF9517 non-dimmer combo? I would think if it works for the dimmers, it would work for the more simple on/off versions of the switches (I say “more simple” because the RF9501/RF9517 combo does not need to worry about sync-ing the dimmer level).
BTW, I have noticed in all these 1 byte parameters that setting them with a decimal number works just as well as with a hex number. The decimal numbers are a bit easier to monitor (i.e., seeing the number “11” instead of seeing “B”).
Finally, like wholm, I too have found some documentation on Cooper switch parameters, but everything I’ve found does not include parameter 10. The standard spec sheet that comes with Cooper switches, covers parametes 1 thru 7. I have found some HTML code that further documents parameters 8, 11, and 12. I have summaried all I have found into a text file. I will start a new thread posting all this information once I finish testing.[/quote]
Any value 1-9 should be the same for both Decimal and Hex.
[quote=“sgm, post:30, topic:183813”]shallowearth ,
I presume when you say parameter 10 works with your dimmers, you mean RF9540-Ns and RF9542-Zs, right? If so, then you are experiencing the same as I.
Have you had a chance to verify that parameter 10 works or doesn’t work with the RF9501/RF9517 non-dimmer combo? I would think if it works for the dimmers, it would work for the more simple on/off versions of the switches (I say “more simple” because the RF9501/RF9517 combo does not need to worry about sync-ing the dimmer level).
BTW, I have noticed in all these 1 byte parameters that setting them with a decimal number works just as well as with a hex number. The decimal numbers are a bit easier to monitor (i.e., seeing the number “11” instead of seeing “B”).
Finally, like wholm, I too have found some documentation on Cooper switch parameters, but everything I’ve found does not include parameter 10. The standard spec sheet that comes with Cooper switches, covers parametes 1 thru 7. I have found some HTML code that further documents parameters 8, 11, and 12. I have summaried all I have found into a text file. I will start a new thread posting all this information once I finish testing.[/quote]
Here are the documents I have found, one was sent to me by Cooper, the other I just looked up:
Can anyone help me find Parameter 10? When I go to the Devices Option menu on my RF940 master dimmer, I only see:
Update Neighbor Nodes
Add Configuration Settings
Associations (that’s where the association with the remote lives)
If I click add configuration setting, I need to fill in:
Variable (default is 1)
Data size (default is monitor only)
Desired value (default is nothing)
Current value (default is nothing)
Tks for your help!
Variable = Parameter
See attached for how to fill it out correctly
Looking for some assistance … I?ve read through this thread, and 2 other threads I found on how to keep Cooper Aspire Master and Accessory switches in sync (?Cooper Aspire RF Master/Accessory Association?, which links to ?Solved! – How to Keep your Cooper RF Master/Accessory Switch always in Sync?). I have a 9501 Master switch and 9517 Accessory switch installed and running, including setting Group ID to 1 on both devices, and setting (undocumented) parameter 10 on the 9501 Master Switch. The good news is that my 2 devices stay in sync 95% of the time. The bad news is that the Accessory switch loses sync about 5% of the time, mostly not syncing when the Master is turned off, and on rare occasion when the Master is turned on.
Seems like the next step for me is to create a scene using the Advanced Scene editor ? but that?s where I?m stuck. I’ve waited for several days for the option to appear to ?Set the Target to True (1) to match the Master switch? (Feb 28, 2015 message from ShallowEarth, concept repeated in this thread). I?m not familiar with LUUP ? and thus don?t know what to do with the suggested LUUP code (April 12, 2015 message from ShallowEarth) - specifically, what to replace so the target devices are named in the code. Or how to ?toggle commands? after setting the Category ID from 14 to 3 temporarily on the Accessory switch (April 15 message) to ?trick Vera into offering the Get/SetTarget Commands for the device?.
Suggestions? Thanks in advance. James
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules