It doesnt, Scott. Itlnnfact it wipes outnwhats there and associates the hubs endpoint… For central scene control, I guess.
Thats why im looking to see if ths stuff is all local if so. It would be good enough for me. If not then rebuilding your DTH inside the framework of this DTH is the answer. (if we go that path, there will uabe to be at least one custom capability/presentation to call the configure button or figure out a way to force configuration save on update)
Thats what I was afraid of. So it sounds like what you are saying is that we may be able to add some code give additional capabilites to the official DH. I hope we can sort it out.
You should be able to do that with the Z wave Tweaker. Community members have reported that is still working with the new app.
Yeah it seems easy enough… At least we have a starting place that definitely works in NewApp…
I’m tracing how they’re setting up associations now… i think its possible to let it setup what its going to do to allow central scene control AND add whatever additional associations you want but…
@JDRoberts you are correct you can use tweaker, but just be sure not to switch to this Eaton DTH after doing so. It slams the configuration just by being set as the device handler. 
I don’t think you can get it done in Tweaker. It is very useful for looking to see what is set up for associations and scenes. However, setting the scenes and associations in the RFWC5 requires the commands be sent a specific order. That was big Ahah moment when I was trying to figure out the DH in the first place. The order needed was published by Eaton but there was not much instruction with it. I was trying to this and that but no success. When I sent all the commands in the correct order, shazam! it worked. I’m thinking we will need to take that section of the DH and duplicate it in the new.
Its likely they have assigned scene numbers to each of the buttons and assigned the hub to each scene. That’s how I was able to detect button pushes in ST. We would just have to make sure that all still works if the user assigns another scene number.
The following is coped from Cooper Aspire Advanced Tech Info V2 pdf from Eaton.
Scene Transfer Protocol for the RFWDC Wall Mount Scene Controller The following protocol is used when transferring scenes from a PC based Z-Wave controller. It allows the use of devices that are scene capable as well as non-scene capable devices.
Association Remove All (for a new scene) Association_Remove, Grouping Identifier (1, 2, 3, 4, or 5 for Button 1 - 5), empty node ID list
For non scene capable devices:
Association Command Class, Association Set (with group ID and node IDs)
Association_Set, Grouping Identifier (1, 2, 3, 4, or 5 for Button 1 - 5), Node ID list (for all nodes that have the SAME level value in the scene. The levels can be 0x00, 0x01 - 0x63, or 0xFF)
Configuration Command Class, Configuration Set (the value is applied to the list of node IDs in the previous association set)
Configuration_Set, Parameter Number (1, 2, 3, 4, or 5 for Button 1 - 5), Configuration Value 1 (this value, 0x00, 0x01 - 0x63, or 0xFF, is the level value for all the nodes listed in the previous Association_Set command)
Repeat sending association/configuration sets as required for nodes of different level values. The first Association_Set command is for all devices with some given level. The second Association_Set command is for all devices with another level. The third Association_Set command is for all devices with yet another level. And so on. There will be as many Association/Configuration pairs as there are different levels in the scene.
The above is followed by this for scene capable devices:
Scene Controller Configuration Command Class Set (with Group ID and Scene ID)
Scene_Controller_Conf_Set, Group ID (1, 2, 3, 4, or 5 for Button 1 - 5), Scene ID, Dimming Duration
Association Set
Association_Set, Grouping Identifier (1, 2, 3, 4, or 5 for Button 1 - 5), Node ID list for all scene-capable nodes in the scene.
Correct - worst case may just be able to append whatever associations we want in addition to whatever the code sets up it looks like…
Also - it didn’t wipe out the custom attributes created for your DTH stored in the Device’s attributes - They’re still there.
The Eaton DTH runs cloud - so no local automations at least until they pull it into the hub’s FW. So worth looking at still setting up direct associations.
Ive gone a couple weeks with the builtin Eaton DTH. The only problem is it works exactly as I expected - replacing the on board associations with reference the hub to support central scenes. Unfortunately that means no hub, or no Internet - no operations.
Looking at the code and how Central Scene support is implemented, (remapping direct associations to the hub) it should be fairly easy to add specific devices to the list (meaning, in addition to the hub associations) to allow the end user to select which mode to operate in.