The Vera Community forums have moved!

General => Lighting & Load Control => Topic started by: Auggie on October 29, 2014, 11:12:20 am

Title: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: Auggie on October 29, 2014, 11:12:20 am
In the market for a Z-Wave controller and after discovering a competing product (Indigo, FWIW) can't distinguish certain functions of these switches (and judging from the response of its forum moderator that it's just "stupid," I don't think there will be any updates to incorporate these functions), I'm looking at the Vera to determine if it can:

The Cooper Wiring Devices Aspire RF9540-N and RF9542-Z use a vertical column of blue LEDs to indicate the current brightness level "setting" and is always lit regardless of whether the switch is in an "on" or "off" state, allowing the "preset" brightness to be adjusted even when the switch is off.  There is a separate amber LED to indicate the actual on/off state of the switch.

So to my question: Can the Vera recognize (and thereby program) the distinct differences of "on,", "off," and "brightness level?"  The competitor's product always assumes the "brightness" level also corresponds to it's on/off state, meaning if the switch is "off" then it assumes (incorrectly for these switches) that the brightness level/setting is always "0".

Since the remote switch settings (On/Off/Brightness Level) are completely independent from the intended master (and other remote switches for a 3+ way setup), I must be able to synchronize all the settings with all the "associated" switches: if a remote's brightness level is adjusted, regardless of whether light circuit is actually on or not, I must be able to match all the other switches' brightness level "setting" to the source switch without changing the current on/off state.  Since the competing product assumes that all dimmer commands are basically a "brightness level" event, it maps a brightness level of "0" to "off", and any other brightness level to "on," preventing me from independently querying or setting the brightness level separate from the on/off state; it will always assume a "brightness level" event other than the lowest setting is also an "on" event resulting in turning the switch on even if you don't want that to happen.

Can I operate these 9540/9542 switches correctly with the Vera?
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: wholm on December 01, 2014, 10:42:59 pm
Your details of your question are not 100% clear, but I will answer since I have extensive use of Vera UI5 and 7 and have these dimmers and remotes.  There are major bugs with Vera.  I have tried to work with Vera for over a year and whenever I ask about zwave versions and issues that are happening with the Dimmers (both remotes and masters) it seems to go into a black hole, which is a shame.  Support for really technical issues are VERY slow.  Routine issues are now quite quick with Vera. 

Now to answer the basic question:  Will it work, yes but I do not recommend Vera.

Now we get into the weeds and oh-by-the-ways:

There is a scenario where if you use the controller to manage a master, the remote will not update unless you set a special variable.  I believe this is true probably for about any controller except their own.  This setting will not correct the setting of the dimmer level while still off.  I can ask about this with the Eaton contacts I have, there might be a solution, but not sure.  This might be doable with Vera's Lua code option.

Over time, the lights on the dimmers will fail.  That means they will go dark or be lit weird.  This is a interaction problem with Vera's zwave version, we know it but Vera will never confirm, so this is why I have to NOT recommend Vera... they will not answer that question.  What ZWave library versions are running per checkbox option that is set? (there are 3 options) There are known buggy ZWave versions out there and it is suspected that this is the problem causing issues with the dimmers.  But since Vera is jerking me around for about a year and I have worked everything else I could in the mean time, you will be stuck with the same problem I have now.  I will likely be moving to the HomeSeer Pro.  To reset a Master is easy, you can use the air gap switch, but this also happens to the remotes and only way to reset them is the breaker.  Eaton, btw, was very pleasant to work with in troubleshooting this problem.

I could not recommend Vera because of: The lack support and the core buggy zwave libraries they use that will cause problems with your dimmers.

-Walt
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: Auggie on December 01, 2014, 10:50:15 pm
I could not recommend Vera because of: The lack support and the core buggy zwave libraries they use that will cause problems with your dimmers.

-Walt

I wish you chimed in just a wee bit earlier, because I just pulled the trigger today on a Vera3 :-/

For the near term, I would be just happy using the Vera simply to "associate" the master/remotes to each other then not have the Vera process any commands between them.

I only need a Z-Wave controller because I didn't realize when purchasing the 9540's that such a controller is required until after I installed them; Cooper does not offer any other LED-compatible dimmer switches so I had no choice than to get the 9540's.

Going forward, I will certainly be taking advantage of having a Z-Wave controller because I will also be getting a Schlage Camelot Touchscreen handleset which is Z-Wave compatible and expand from there.
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: wholm on December 02, 2014, 09:10:15 am
Eaton sells a handheld unit that can do the associations for you.

I am sure you could always return the Vera unit, if you just purchased it.
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: Auggie on December 02, 2014, 09:25:19 am
Eaton sells a handheld unit that can do the associations for you.

I am sure you could always return the Vera unit, if you just purchased it.

Are you referring to the Aspire RF RFHDCSG Handheld Controller?  I already looked at that but at the lowest price of $213 shipped, it was way more expensive than the $159 Vera3 I just bought off Amazon.  I actually found the RFTDCSG Tabletop Controller to be a little cheaper and seemingly more powerful but still ~$200 shipped.

But the Vera3 should give me more flexibility in the future as I add new Z-Wave devices but don't anticipate adding any more Cooper Aspire Z-Wave switches (which are in the kitchen and family room only).
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: Auggie on December 02, 2014, 09:36:23 am
Over time, the lights on the dimmers will fail.  That means they will go dark or be lit weird.  This is a interaction problem with Vera's zwave version, we know it but Vera will never confirm, so this is why I have to NOT recommend Vera... they will not answer that question.  What ZWave library versions are running per checkbox option that is set? (there are 3 options) There are known buggy ZWave versions out there and it is suspected that this is the problem causing issues with the dimmers.  But since Vera is jerking me around for about a year and I have worked everything else I could in the mean time, you will be stuck with the same problem I have now.  I will likely be moving to the HomeSeer Pro.  To reset a Master is easy, you can use the air gap switch, but this also happens to the remotes and only way to reset them is the breaker.  Eaton, btw, was very pleasant to work with in troubleshooting this problem.

This issue does concern me.  Are you referring to the "lights on the dimmers" as the light fixtures themselves, or the status LEDs on the fronts of the Aspire dimmer switches?  And if its the status LEDs, how did you determine that it was the Vera itself that caused the Aspire LED status lights to "go dark or be lit weird?"  I would assume that external controllers can only send commands that the device itself needs to interpret and internally adjust its LED status lights accordingly, unless the Vera is directly manipulating the LEDs.

If it's the light fixtures themselves that becomes unpredictable, again, I assume that any controller simply sends the commands that the Master 9540 switch intercepts, which in turn physically adjusts the light fixtures (on/off/brightness).  So is it that the Vera was sending incorrect commands to the master dimmer that was determined to be the culprit?

Under which Vera UI (5, 6, and/or 7) have you experienced these issues (and "library" version, since you mentioned it)?

Have you tried simply "associating" the switches and have them run independent of any controller to see if the issue presents itself under that setup?

I can certainly relate to your frustration with support: I was testing out a trial version of Indigo and inquiring about Aspire RF support but got pretty rude, then dismissive responses which the final retort was basically submit a feature request though they may not get to it (if ever) due to their "backlog" of requests.  Hence my selection of the Vera, even though I, too, heard some grumblings of support as the company appears to be focusing on UI7 release verses device compatibility and issues.
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: wholm on February 12, 2015, 08:22:33 pm
The remotes can fail to operate as expected.  This is due to the fact the controller is likely trying to reprogram the switch and fails and leaves out the group 1 associations.  Masters will work fine usually and they have a disconnect that can locally power cycle the device.

I am still working with Vera, trying to downgrade to 2.78 so this bug doesn't cause a problem.  3.2 uses the latest Zwave 4.52 they say which is known to be buggy.  There are service packs they can apply to fix this problem.  But since there is no way to confirm what they are actually running without them telling us, then you will not know when the problem is fixed.

The lights themselves will not become unpredictable just the switches.  They should more than likely function if they are a master device.  The remotes on the other hand may not because they lose their group 1 due to the Vera.

-Walt
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: wholm on May 20, 2016, 08:11:54 pm
I would like to update this, I went through a long process to get this working.  I switched to HomeSeer since Cooper OEMs their controller and there was an issue with Zwave builds on the Vera (possibly) at the time.  Well I switched to HomeSeer and same problem happened.  I had to reprogram all the dimmers with the latest code and all the problems stopped.  The issue was with Cooper and it had to do with the software build.  If you purchases the dimmers by the time of my last post in 2015, it would have been fine since the firmwares on the dimmers were up to date by then.
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: Wekurtz74 on May 21, 2016, 06:45:03 am
I would like to update this, I went through a long process to get this working.  I switched to HomeSeer since Cooper OEMs their controller and there was an issue with Zwave builds on the Vera (possibly) at the time.  Well I switched to HomeSeer and same problem happened.  I had to reprogram all the dimmers with the latest code and all the problems stopped.  The issue was with Cooper and it had to do with the software build.  If you purchases the dimmers by the time of my last post in 2015, it would have been fine since the firmwares on the dimmers were up to date by then.

I have Cooper products that are older than 2015.  Can you explain how you reprogrammed the dimmers with the latest code, or point me to a resource concerning this?

Thank you for your anticipated advice.

Sent from my GT-N5110 using Tapatalk

Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: wholm on May 21, 2016, 08:05:44 am
I would rather chat privately as some information they might consider not for public.
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: Wekurtz74 on May 21, 2016, 12:07:14 pm
Understandable.   

Sent from my VS986 using Tapatalk

Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: shallowearth on May 21, 2016, 12:18:06 pm
I have the Cooper switches in question.  If you want to go the cheap, cheap route to associate them you can use an Aeon mini-mote (essentially controller-less), I was using that before I even had a Vera to associate them.  As I was just doing basic things like turn on the floor lamp in sync with the light switch.  Or adding additional switches in a virtual 3 way by adding the Cooper battery powered dimmer.

Later I moved to the Vera Edge and have not had any problems (I am on firmware 1.7.1248 which was the last good firmware before they went to the buggy z-wave+ self healing firmware on the Z-wave chip)

I did have to write a little bit a LUA code to keep the dimmer LED light on the aux switch in sync with the master, since direct association doesn't work if you manipulate master via a scene.  You can muck with both LEDs on the aux switch using the advanced scene editor functions or LUA code (with out turning the master on or off), you cannot muck with the LED dimmer settings on the master with out turning on the light however as Auggie described (aka you cannot preset the dimmer level to something else while the light is off on the master).

Wholm, can you send me private info on these switches.  I have been running them this way for almost  2 years, if the Vera is going to burn them out, I definitely want to know about it, most of my switches are older.  I have never found a way to get in touch with Cooper or Eaton support, that knows anything about these switches, I would love to talk to them about a different problem I am having
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: wholm on May 21, 2016, 05:26:26 pm
I have the Cooper switches in question.  If you want to go the cheap, cheap route to associate them you can use an Aeon mini-mote (essentially controller-less), I was using that before I even had a Vera to associate them.  As I was just doing basic things like turn on the floor lamp in sync with the light switch.  Or adding additional switches in a virtual 3 way by adding the Cooper battery powered dimmer.

Later I moved to the Vera Edge and have not had any problems (I am on firmware 1.7.1248 which was the last good firmware before they went to the buggy z-wave+ self healing firmware on the Z-wave chip)

I did have to write a little bit a LUA code to keep the dimmer LED light on the aux switch in sync with the master, since direct association doesn't work if you manipulate master via a scene.  You can muck with both LEDs on the aux switch using the advanced scene editor functions or LUA code (with out turning the master on or off), you cannot muck with the LED dimmer settings on the master with out turning on the light however as Auggie described (aka you cannot preset the dimmer level to something else while the light is off on the master).

Wholm, can you send me private info on these switches.  I have been running them this way for almost  2 years, if the Vera is going to burn them out, I definitely want to know about it, most of my switches are older.  I have never found a way to get in touch with Cooper or Eaton support, that knows anything about these switches, I would love to talk to them about a different problem I am having

I think I know what you are referring to.  Are you talking about how the remote dimming levels do not show in Vera and you cannot control them with a scene?  There is a solution to this that is not documented, well it is but finding that document is impossible.  On the master, you have to go into the advanced settings and set parameter number 10 to a value of 1.  I have to find those exact instructions again.  What this does is it sets off a function in the master to tell the remote to set itself.  Now, this is only the case when the automation controls the master, you never have to do this when you press the master or remote physically.  Also this is only set in the master, not in the remote.

I actually think this worked better with Vera than with HomeSeer.  HomeSeer exposes the device as a dimmable device and the expectation is that when you set the master to a level, that you should do the same with the remote(s).  Pros and Cons to all of this.

The update will not affect this setting in any way.  The update is only needed if you see odd behavior like multiple lights staying lit on the dimmer or weird functionality in that the dimmer ramps up and then turns off even those it's on 100%.  Like I said, odd behavior and this only started showing with a larger set up really.

You want to avoid needing this update, btw.  It takes some expertise and there is no warranty.  And it costs money for the programming tool.  There is risk of blowing out the tool too if you do it wrong and make a mistake of leaving the power on to the device.

If I understood your problem correctly, then if you can wait, I ordered the new Vera and I am planning to switch back to Vera... maybe... so much to reprogram!  Once I do get the device, I will get the exact settings you need to do to make that work.
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: wholm on May 21, 2016, 11:18:27 pm
Here are the notes I used to set this setting on the Master dimmers:

configuration setting index 10, hex byte with a value of 1

It's an advanced setting for the device, you have to set variable 10, its not something you pick from a pull down or anything like that.  I cannot find my screen shots I had from UI 5.
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: shallowearth on May 23, 2016, 03:23:58 pm
Interesting, I have never seen any documentation on parameter 10 before, I might have to try it out.

As far as the problem with Cooper switches, It sounds like what you are saying is that recent firmwares on Vera have a tendancy to wipe out the Group 1 associations on the switch correct?  And that if that is the case than you need to update the firmware on the switch, or Vera needs to fix their bug.

Glad I stuck on the firmware I am on!

Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: wholm on May 23, 2016, 04:35:53 pm
Can you take out one of your master dimmers and one of your remote dimmers and tell me what version sticker is on there?

Also the removal of Group one is 1, I cannot comment on that because although that may have happened (I don't have that documented specifically), my issues were much more obvious.  For example, on the master dimmer, the orange led would be on but also about 3-4 other blue LEDs at the same time.  The airgap switch was used to power cycle the dimmer to return function.  In some cases the dimmer would actually still operate in the background but the feedback was odd, even sometimes all LEDs were out.

My issues with HomeSeer are due to poor coding releases and poor design choices.  For example, they do have a Linux based approach but only support it in a specific debian Linux.  I target enterprise solutions and their ZNet device is a great fit for that, I need this running on CentOS 7.  I had it working but turned out I was using too new of a mono version and it was corrupting the serialized objects being written to their DB.

And then lets talk about the DB, their choice is SQL Lite which is notorious for consistency problems (say a system crash or power outage).

On top of that, even though I managed to get the owner on the phone when I demanded an answer one time, later when I asked about their serialized data structure, they acted like it was something proprietary.  It's just a serialized object for crying out loud.  The problem was they were not delivering enough information via JSON interface that I was used to with Vera.  So again stuck.  The "event" builder they have is workable but primitive based on the stuff I have worked on.  I gave them input on design and they have completely ignored it.  They finally stated that they were not really designed to work in a commercial environment... oh yeah, their supported environment Windows, it doesn't even run as a service and if you know the tricks to do that, don't.  That DB thing I told you about, one of the reboots you will cook your DB and have to restore, I hope you have a back up before that reboot :).

I am just stuck with no perfect solution.  I need to run ZWave hardware separate from the controller (HomeSeer does this) but I need the more solid/simple design of Vera... and the superior interface!

Wow, that was a tangent.
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: shallowearth on May 23, 2016, 05:16:15 pm
Hmm, I have about 20 Cooper switches in my mesh (combination of Switches, Dimmers, Aux Switches, and Battery Switches) and haven't really had any problems, but I am guessing in a commercial setting you are talking way more than.  However one thing I have noticed is that they seem to be a little more sensitive than most switches to malfunctioning/bad neighbor switches.  Twice I have had problems with my Coopers when there was a bad node in the network that seemed to freak them out (causing them to lose association, fall off the network, or other bad stuff, like you were describing).  In both cases it was a bad z-wave outlet that was near the Cooper Switches (but not even associated to them) that was causing the problem. Got rid of the offending device and the Cooper's went back to stable.  But you can only figure stuff like that out if you are going slow and start seeing something destabilize after you installed something bad.  I have no idea why the Coopers are so sensitive to such things. 

Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: wholm on May 23, 2016, 06:33:18 pm
In my home I have about 80 switches, dimmers and remote dimmers of Cooper, other vendors include Aeon, Linear, Evolve, Pella and Trane.  I am currently having an issue all of a sudden with the Thermostat locking up but that seems to be something with my ZNet device.  Just last night the ZNet device decided it was time to take a break, a reboot didn't work, no, I had to go to it and power cycle it of course at midnight.

I haven't had any other issues where the Cooper devices failed because of another device and unlike Leviton, I never had a Cooper device go bad.  2/30 over 6 years for Leviton, 0/80 for Cooper over about 3 years now.
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: sgm on May 25, 2016, 06:23:28 pm
Quote from: wholm
Here are the notes I used to set this setting on the Master dimmers:

configuration setting index 10, hex byte with a value of 1

THANKS.....

This information was incredibly useful to me.  I am building a house and decided to make the lighting smart.  I settled on Cooper 9540/9542 switches.  I was aware of the "sync problem" using these switches for 3-way circuits, but I figured I'd just have to do a lot of work (as others have done) to make it all work.  The electrician is starting to install fixtures, so altho I had 9540-Ns (and tested them -- which had their own problems); I had no 9542-Zs until the other day.  The 2 switches worked together fine manually once they were associated, but when used with the Vera, the 2 switches would not sync.  Indeed, if I turned on the test light with Vera, and then turned off the light manually with the 9342-Z, Vera continued to think the 9540-N was still on.  I was resigned to a bunch of research and "programming" before I purchased the remaining 9542-Zs I need, when I found this thread......my lucky day!

I set the 9540-N parameter 10 to 1 (under "device options"), and VOILA, everything syncs just fine.  Later I did a thorough search of the internet looking for any documentation or other reference to this "trick".  Apparently, Cooper is keeping this parameter 10 a secret!!
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: shallowearth on May 26, 2016, 02:22:32 pm
Hmm, is parameter also suppose to work with the RF9501/RF9517 switches  as well?
I tried it putting the parameter on the RF9501 and it allowed to me add the parameter, but I don't see it keeping the RF9517 LED in-sync if you control the RF9501 from the Vera.

Maybe that parameter only works with the Dimmers and not the on off switch version?  I will play around with it a little more tonight to make sure I just didn't make a mistake or didn't give it enough time to change behavior.  Good news is that it is super easy to just have a scene that triggers from the master to set the aux when using it from the Vera, the dimmer is the more tricky one to make work right anyway.
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: sgm on May 26, 2016, 02:53:26 pm
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.
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: shallowearth on May 26, 2016, 02:58:20 pm
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
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: sgm on May 26, 2016, 03:02:14 pm
OOPS....we x-posted.  See my reply above (I edited it after your post).
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: sgm on May 26, 2016, 03:14:44 pm
Quote
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?? :-\
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: shallowearth on May 26, 2016, 04:19:32 pm
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.
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: sgm on May 26, 2016, 05:18:48 pm
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?

Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: wholm on May 26, 2016, 10:01:47 pm
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?

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.
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: shallowearth on May 27, 2016, 04:23:33 pm
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!
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: shallowearth on May 28, 2016, 12:41:38 am
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
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: sgm on May 28, 2016, 05:11:21 pm
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.
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: shallowearth on May 28, 2016, 07:00:02 pm
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.
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: wholm on July 17, 2016, 12:20:53 am
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.

Any value 1-9 should be the same for both Decimal and Hex.
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: wholm on July 21, 2016, 12:15:42 am
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.

Here are the documents I have found, one was sent to me by Cooper, the other I just looked up:

http://www.cooperindustries.com/content/dam/public/wiringdevices/products/documents/technical_specifications/advancedtechinfo_V2.pdf

http://www.cooperindustries.com/content/dam/public/wiringdevices/products/documents/spec_sheets2/AspireRFSmartDimmerSystemMasterSpecSheet.pdf

Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: ssubo on March 27, 2017, 02:24:03 pm
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!
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: shallowearth on March 27, 2017, 02:36:10 pm
Variable = Parameter

See attached for how to fill it out correctly
Title: Re: Cooper Aspire RF9540-N/RF9542-Z Dimmer Switch Programming
Post by: tchen001 on June 10, 2018, 11:24:53 am
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