-defunct-

False senses of security end up leading to breaches.

Anything has risk, but generally new models a manufacturer sells don't go backwards in security.

I think you're smart enough to understand that I switched it to indicate the entire market. As 'secure' as Savant is, 5 years down the road is a VERY long time in technology.

That shouldn't be a fantasy. And we wonder why IoT hits the news all the time with hacks and botnets... Hanging on to old devices is risky.

No one should have any IoT product beyond 5 years. NAS, DVRs, NVRs, Cameras, remotes, matrix switches, smart devices, etc. The exception to that would be commercial networking as those are usually designed and supported for a decade after creation.

How about changing every 3-5 years because hardware peripherals and hardware security changes? It's not secure to be using a device built a decade ago, even if it was built to modern standards during that decade.

Maybe its not clear, but the IOextender got updated to be OS3 compatible, the version revision just didn't change. Also simpler system architecture, less time to implement.

I know it seems minimal changes are made to the OS, but that's because we're good at making the presentation of features similar. The guts of the system have updates every major release and minor release.

OS3 had major zigbee updates. OS3 had security enhancements to IR and serial. OS3 had audio changes. OS3 has a newer, more secure linux kernel. New controllers support IPv6. HC250 barely supports TLS1.2 HC250 had flash nav and audio code was tied into navigator code. The HC250 code-base had a lot of dependencies. The experience with the half functional HC200/300/500 was bad enough to not consider major limitations on a fully featured controller. The time to update all of the above was longer than the time it took to remove the driver from the OS.

There are many reasons the hc250 was not brought up that outweighed the prevalence of use. It's a unique architecture, and has a lot of specific oddities that made it very time consuming to ensure integrated properly.

ZBIO? Never heard that before. We have been evolving the OS and needed to make concessions for the timelines. HCs, minus the HC800, didn't make the priority cut.

The IOextender is not on OS3, but was updated to support the changes. Those changes and audio changes were determined to not be worth the time for the hc250s. It's not as simple as add a driver to the ecosystem and go.

HC-800 and EAs share a lot of code-base. I would expect them to stick together. Older HCs have older hardware and aren't up to modern standards.

Also, the HC250 cannot support the current OS without very heavy lifting. Even IR/RS232.

Clarification: They needed to be EOS. The messaging around disallowing them and not supporting them could have been clearer, but they needed to be left behind for a list of reasons.

The HC250? HC200/300/500? They needed EOL'd. Maybe the reasoning could have been clearer why.

With the state of the cyber world right now, I honestly wouldn't keep any devices that haven't had an update, even just a security patch, within the last 6 months.

Every manufacturer stops supporting their legacy devices at some point. The burden of keeping them in the ecosystem sometimes outweighs the benefits. Like deprecating sslv3.

There is no kb article, but go to port 60000 on a controller.

You can actually. The OvrC web UI on the controller allows deleting scanned devices from OvrC, just like the pro hub.

OvrC Pro-hub provides no added benefit over a Control4 controller on 3.2.2+ and the functionality is tailored to dealers rather than homeowners/end users.

The adblocker and family filter are fantastic though. Obviously not perfect (I was able to bypass a few), but nothing that a few more rules could prevent.

@Control4Savant I have had zero issues so far. No hiccup with Control4, OvrC, or personal things. It's alerting on gaming and streaming is fantastic, although it doesn't provide the urls in friendly means. It shows the url rather than noting which service it is and many streaming services use very random urls and domains to host their content.

Firewalla Purple in passthrough mode between your RK-1 and your core switch would do the trick. I've seen some UniFi software out there, but I haven't seen anything close to the firewalla for the consumer market. Everything else is either commercial grade (like Palo Alto), or it is limited (like Disney Circle).

I use an RK-1, but I purchased a Purple Firewalla for that functionality since the RK-1 never had everything I wanted.