RAV

Here's my guess.
The tech couldn't get the new ISP router to function with the Araknis, double NAT, or just wasn't experienced enough. Possibly the previous ISP was just a modem, not a gateway. So he decided to remove the Araknis router. Your processor was probably setup with a static IP, so he mistakenly factory reset the processor rather than just reset the network. So he loaded an old saved copy of the program that didn't include the keypad programming.

Writing this as if it was a light that you want to turn on for as long as it was off. Has an error range upto the length of the timer, could complicate if needed with another timer.
When light turns off, set still off to true and set counter to 0. Start countup timer (length 10min). When countup timer expires increase counter +1, if still off is true, run countup timer 10min. else if still off is false, stop.
When light turns on, stop countup timer 10min and set still off to false. (Count now equals how many 10 min cycles happened while light was off). Start timer countdown (also 10 min), when countdown timer expires if count <2 then turn light off and stop (as count would be equal to 1 and this is last needed cycle), else count equals count-1 and restart timer countdown.

"Dumpster Fire" is a term coined by another developer for a driver that doesn't follow an official API. Their point being that sooner or later, it's going to have an issue, one side or the other will update and break the driver's control. The trouble is for dealers it's not always apparent if it's official API, snooped, or a hack, and the client just knows they paid for and it isn't working so it's the dealers fault. (Snooped referring to watching the communications by another app that's controlling it; as oppose to a hack which might mimic another device to fool a cloud server, ie pretending to be an iPad).
Control4 will always take the API road. Got to protect their brand, right thing to do.
Now, many dealers are also campaigning to always only use API drivers. For the good of the brand, industry and reliability for your customers.
But automation is still the wild west. What is the developer's responsibility to disclose, update, support? Is it a one time purchase with the expectation it will work and be supported through all updates? Is it a one time at this moment use at your own risk, it works today, and we can't control the future? 
I'd like to at least see a disclosure of: its from their official API, or there is no API and we reversed engineered it. And appropriate related pricing. If it's an API and you're going to support it, than that's worth much more than here use at your own risk works today.
And kudos to the brands that are paying developers for creating complimentary drivers.

Cause stuff changes.

For instance, AppleTV pre and post 4K.
Or legacy Roku controllers no longer being updated. (Or Sonos, or HC controllers, or.....)
Built in will just create a headache in 2 years, and it's only $100 or less for a Roku.

Anything you want. Consider them a 5 button wireless keypad, but with one way communications.
Spotify presets, sure, volume yup. Garage lights, deck scene, house off, done all that.
You set them up in Caseta Pro first, it assigns them an ID#.
You put that ID# into the Control4 driver (in the online database) and program away.

Curious, what do you want, is missing, from the EA controllers?
I'll grant you 4K resolution output. But besides that, what features, hardware options, inputs/outputs do you think would be needed that aren't today?
From a processor standpoint, seems there's plenty of horsepower, so other than chip supplier life cycle availability necessitating a board redesign...?
 

Depends on is there Zigbee? Just wired keypads to a 30 zone panel, sure.
But I agree with if you add in some zigbee switches, thermostats, remotes, advanced programming, net drivers; then you'll end up underpowered, then you're into a EA3 or EA5 depending on complexities.
CA1 was designed for centralized lighting where there was no entertainment (HDMI, Audio Services) needed.

Pretty clear 3.0 is to help dealers sell more touchscreens.
Touchscreens are cool, but their 'need' and usefulness had been waning and the old GUI handicapping.
The virtual D-tab, the media bar with icons below so you can adjust lights and stuff while watching/listening, view a camera, answer the door, will make for a better user experience.
Maybe it'll be like a pacifier to get people's heads out of their tablets when the family's watching a movie, here you drive, but down facebook.

Control4 supported those touchscreens for 9 years of system enhancements!
No, they're not cheap, but they lasted, and they didn't loose functionality, and they still function just fine if you don't have to have the latest GUI.

Control4 supported those touchscreens for 9 years of system enhancements!
No, they're not cheap, but they lasted, and they didn't loose functionality, and they still function just fine if you don't have to have the latest GUI.

Control4 supported those touchscreens for 9 years of system enhancements!
No, they're not cheap, but they lasted, and they didn't loose functionality, and they still function just fine if you don't have to have the latest GUI.

I heard it was going to include dragons.

Over populating with dealers is THE fear. Follow up email states not to be concerned with dilution, time will tell.
And it's been done to other brands and doesn't work at this level (Savant comes to mind, Phast before them). I'll trust they know industry history.
Don't loose site that Control4 is much more than a control system, it's has great people and tech in Pakedge, Leaf, ihiji, that will improve existing products. Also a premier custom speaker maker in Triad. And talent from Neeo to Amazon.
Some of the best talent in the industry, just got together with a bunch of money and infrastructure. Also, attention can return to innovation rather than bureaucracy of being a public company.
Here's to being optimistic, with great tools to work with against the mass that is IoT.

" HC800 does not support IPv6 among a few other thing "

Roll Dog,
For client IP Control - use the IP address of the Genie 2 (make a router reservation, DirecTVs are known to be forgetful of static settings) and input the EXACT room name of the client box.
Caveats - no IP power control of clients, and no client side 'setup menu' navigation, for that you would still need IR.

It's a control SYSTEM, not a remote control.
"Well, in this room you have to point, and no the app can't turn off the TV because, and"... yeah no thanks.
Run a wire, use a z2ir or IP control. Don't want no line of sight stuff.