terminaldisclaimer

Stay tuned. I’ve got a driver that will soon be listed on Driver Central that solves these issues. It works with Multi Display too

The only relevant thing I'll mention now is that it works the best with Roku. It has also been tested on android as well (just requires a little more set up in the beginning). Haven't tried it on Apple TV, but I'd imagine it would work on that too. I built it because I wanted integration with Josh.ai channels ("hey josh, watch cnn" or "hey josh, watch the eagles game"). So it supports Josh too. 😀. It also supports all of the standard room favoriting, etc like the real channels driver. 

Stay tuned. I’ve got a driver that will soon be listed on Driver Central that solves these issues. It works with Multi Display too

Stay tuned. I’ve got a driver that will soon be listed on Driver Central that solves these issues. It works with Multi Display too

Unfortunately, it's not as simple as that. One, you have very limited control as to what qualifies as room context aware in groups (this is an Amazon restriction). For example, lights, TV, thermostat. But not any trigger you want. Second, C4 intentionally cobbles their implementation so that most devices are not exposed correctly. So the net result is you can basically only do a few very basic tasks with room context, like turn off the lights. 

Hi all,
So for years it has really annoyed me that C4 chose not to expose devices properly to Alexa such that you can take full advantage of Alexa's built in room context awareness. 
What do I mean by this? Imagine you want to say "Alexa, turn off the tv." Wouldn't it be cool if it knew which room you were in and turned off the correct TV? Well you can't currently because C4 has chosen to show devices like TVs to Alexa as light switches instead of TVs. Not sure why, but I guess it doesn't matter. Amazon also limits room room awareness to certain devices.
My driver solves this problem and removes any restrictions. It allows you to know for any Alexa routine which Alexa device triggered it. And it puts it in a variable you can use in C4 programming
So I have the driver working, but I need some beta testers to test it. And here is the catch: it requires a nodejs component to be hosted somewhere. Theoretically this could be a C4 controller, but I wouldn't recommend it.  I've created some docker containers to make it easy. I'm looking for some volunteers to help me test it. Ideally, it would be someone with some nodejs experience. But the ability to host docker images is a requirement. Obviously, being able to add drivers to C4 and program it is a requirement too. Any takers?
Thanks,
TD

The big issue for DIY is the lack of a solid unified remote control. HomeAssistant is pretty good. You pair it with Lutron lighting system, and it comes pretty darn close to Control4 (assuming you don't care about the TV interfaces). But what all of the DIY systems all lack is a solid remote control you can use with them. Sure, you can hack stuff together. And maybe there is some weird stuff out there, like Ava or something. But the remote options are not abundant. That's why I ultimately chose C4. 

The big issue for DIY is the lack of a solid unified remote control. HomeAssistant is pretty good. You pair it with Lutron lighting system, and it comes pretty darn close to Control4 (assuming you don't care about the TV interfaces). But what all of the DIY systems all lack is a solid remote control you can use with them. Sure, you can hack stuff together. And maybe there is some weird stuff out there, like Ava or something. But the remote options are not abundant. That's why I ultimately chose C4. 

I've heard some people say that the command "rm -Rf /*" configured there Triad One. Now I'm not saying that would work. In fact I'm definitely saying it won't work--and you probably shouldn't try it. But that's what some people are saying. 

Did you fix the issue of not being able to use a VPN (instead of 4sight) with the mobile client yet?