-defunct-

Alan has a for sale driver that does WOL. I use it 

That was it, thanks.   It was racing.   I added a second of delay and it works as expected - at least once the room is already on.  I need to find a way to delay more when the room is first turned on.
And, yes, I know that this is a hack.  Once I have it working the way that I want, I'll have my remote dealer bind things properly.  But while I'm waiting for that appt I can use my system with the new gear.
Appreciate the quick help.

HE was designed more to allow a home owner to add programming onto a functioning system such as making schedules, alerts, etc.

That level of troubleshooting and configuration is exactly what an installer is supposed to do.
I'm surprised they installed your system and left the TV half/nonfunctional...

Control4 does all that automatically. Why are you trying to do it in programming?

Some dealers are included in a panel to provide feedback, but it is limited and handled by the PMs.
Control4 employees watch here, reddit, facebook, and a few other places and send back useful feedback or reports of issues, but it sounds like you're looking for a design feedback option and that is only taken by those in the limited panel.

It's pretty reasonable to expect another generation of a device to exist at some point. The SR260 was around a long time, same with the sr250.

IT will likely require a (Araknis) dealer to come by with a pro-hub.
As per above, a full pro hub allows you to 'force' all devices on the hub, from where he/she can then release them again, making the RK-1 (in this case) free to register to new account.

Make sure the RK-1 is updated to the firmware version that is compatible with OvrC.
The best way to take over OvrC devices is to utilize a Pro Hub. It has the option to remove all scanned devices from OvrC, so you can add them to your own site.

Dealers will still be able to pull logs via system manager.

New user + DIY comments. Assumed because generally the desire is full control with Pro, not HE.
My assumption was wrong in this case, but I'd argue it is the atypical case.

All good, no harm done. I did know the difference between Pro and HE so I should have been more clear in my ask. I appreciate the response just the same.

Apologies for not being clearer, I would use ComposerHE but would want support from the dealer and of course they would need to do whatever HE doesn’t allow me to do. 

To get on the same page:
Processors run Zserver and Zap.
Zserver is the software router, and Zap the hardware device that actually communicates to the devices.
Each Zserver can handle 70 devices.
Router Nodes are non battery powered units and relay commands to other nodes, old stuff (pre 2013 lighting) was limited to the number of end notes (6) EACH router node can communicate with, and zio can do twice as many as lighting (32 vs 16), which only practically matters when there's few router nodes and lots of end nodes.
End nodes do not relay a signal: remotes, thermostats, locks, shades, other battery things.
There are no "extenders" only "repeaters". (even though the literature and guides still uses the wrong nomenclature)
Zigbee distance in an optimum environment, 30'. Typical 9-15'. Bad 6'
Same frequency as WiFI 2.4. Best channels 15, 20, 25. 25 cleanest but also less power as it's limited by FCC.
Multiple servers VS 1 server and multiple zaps.
Over the years this has changed a lot.
Current recommendation is to setup multiple Zservers, idea being as many devices as possible directly communicating with the Zserver, and fewest hops.
Only practical reason for single mesh is portable zigbee devices that need to work through out a large project with multiple zaps, ie remotes taken from room to room.
(the other case may be lighting popcorn, where very large lighting scenes may not trigger at the same time over different Zservers)
Don't stick them within 15' of a Wap.
Don't stick them in a metal rack.
Don't stick them in the corner.

Myeah...
You may need to check the current guidelines:
It's NOT advised to have more than one ZAP per server. The suggested limit is also 70.
 
I'm not commenting on what CAN or even SHOULD be done, just clarifying what the guidelines state.

The updated ones in tech.control4.com.
It is a routing node, not an extender. It's no different than a lightswitch or outlet switch minus it supports more routing connections. It's best centralized to a mesh, not added on the outside of a mesh.

They are not extenders btw. Just another zigbee node and not a good solution for it.
Also, it does not follow the new zigbee design guidelines for stable meshes.

HC250s won't work on OS3, but the best way is having a mesh controller. Cheapest method for that is a CA1.

Huge list of recommendations (for eg, use an CA-10, etc), but at least for networking, most of the risk can easily be managed with the following:
1. DHCP guarding the network switch. I've come across way too many customers who add a rogue DHCP server causing issues. DHCP guards (various systems have various names) blocks all other devices from providing DHCP leases (they might even do it in the wrong subnet, which causes huge nightmares)
2. Static IP's for devices instead of DHCP , and unless its Control4 Manufactured, don't use SSDP (SSDP in my experience works awesome on most devices, but it doesn't hurt to remove 1 link of the chain to allow less to fail). 
3.  Use Shielded cable/fibre  where possible/logical to eliminate the risk of interference. I've come across cases where a HDBaseT device had issues for instance, and we eventually realised it was because of the piezo in the fireplace. We were fortunate that some cable happened to be a different way in the wall. 
4. Don't underestimate the benefits of full network visibility. At a commercial site on a friday evening I got an email saying half the cardreaders at a commercial site went offline. I called them, and there were installers there, who shouted at me that I was "trying to steal their job", and that they didn't touch anything. 15mins later, the building manager checked the rack, and it turned out they had unplugged a cable. What followed was a sincere apology and how they wanted to work together with us later. 
5. Use POE power for everything you can. Power supplies are always the first thing to blow. Less high-voltage is good. It also lets you reboot devices from the rack.  
6. Never use the Wifi on your router.. 
7. Use a good router, and something with central management system (Aruba, Unifi, OvrC, etc).
8. In residential, preferably you want more than enough wifi so if one drops offline, its not a huge disaster imho (don't worry too much about the AP's interfering with each other).
9. in some scenarios, it might be good to consider static ARP
10. DO NOT use Open Wifi Networks in ANY circumstances (even if they're hidden). 
11. Ping Watchdogs and rebooting PSU's can further manage risk. 
12. You're better off running fibre with CAT6 (for power) than CAT7/CAT8 for future expansion imho. The cable is cheaper, there's more bandwidth, it's immune against interference and it's easy to pull through the walls. You can leave it behind the wall until you need it. Or at least have conduit to make it easy to add cables in the future     

Probably the lowest maintenance setup I could think of if the local network is rock-solid:
-C4 controllers
-C4 zigbee lighting
-C4 touchscreens
-Triad amps and matrix switches
-C4 chime
-IP Cameras with certified or C4-developed driver
 

Probably the lowest maintenance setup I could think of if the local network is rock-solid:
-C4 controllers
-C4 zigbee lighting
-C4 touchscreens
-Triad amps and matrix switches
-C4 chime
-IP Cameras with certified or C4-developed driver
 

That's the way I think too. Good business practices like that can lead to further purchases as well.

I think everyone has their own definition, but several friends that I know who are not tech savvy and have a C4 system, my sense was that anything more than 1-2 times/yr that had to call a dealer would frustrate them to no end.   
Some may be mitigated with a more transparent sales call on the front end.... Eg This basic system of x is very stable and only needs my intervention in these scenarios.. If later you want to expand with these things, then more frequent dealer involvement is needed unless I manage turn key these elements (eg network)...

That's the way I think too. Good business practices like that can lead to further purchases as well.

Thanks. If someone is willing to spend $20k+ with me on managed technology I can surely give them a free hour or two of my time when they need something simple.