becnel51

Thanks @rea I didn't even consider IFTTT, I may use that as a temporary solution. And Thanks @alanchow, really looking forward to the driver. I'm sure you won't..., but let me know if want / need anyone to test it. Appreciate the feedback everyone.

@zaphodYes the Govee lights are connected via wi-fi (this I'm certain of). I believe they can also connect via Bluetooth. And yes, Govee has and Android and IOS app, called Govee Home (basically to control all their products). @alanchowIf you have a Govee product, after you set it up in their app, you can submit a request for the API. I believe it's under the profile settings. They literally email you everything you need within an hour or so. Here is a link to their latest API Guide (also attached). I can also DM you the API key they provided me, if that will help you in anyway. Just let me know. As for possible current solutions...(until @alanchow makes a driver)... I'm up for any suggestions? I was thinking possibly Amazon Alexa. The device is compatible with Alexa and Google. I know the LG C1 is compatible with both also. Maybe an Alexa routine? Ultimately I would prefer not to have to issue a verbal command via Alexa or Google, and just have the automation controlled via C4. Hence, simple programming where the Govee lights follow the power state of the TV..., but I don't think that is something I can personally accomplish at this time. Unless anyone has some clever ideas??? Thanks for the replies, and @alanchow let me know if their is anyway I can assist, with that potential / future driver. GoveeAPIReference.pdf

I have the following LED light strip on back of a TV: Govee Immersion. The company also provided me with an API key and API code reference guide upon request. I'm looking for the best / suggested methods to integrate this product into my C4 system. Honestly I would be completely satisfied with "On / OFF" and "Brightness" control. Ideally I would like the lights to follow / mimic the TV's power state, and some brightness control would be nice. The TV is already integrated into my C4 system (LG C1). Should I get a dealer / someone to make a custom driver? Or would I be better off with Chowmain's TCP Command Driver? Honestly I'm not certain if either method would work, but hoping someone here would have some ideas. I'm pretty good with setting things up / programming / & automation within the Composer software, but I have almost no knowledge when it comes to custom drivers and actual coding. @Matt Lowe@msgreenf@alanchow@chopedogg88 or anyone else, any advice / suggestions is appreciated. Thanks.

@jsimon77@chopedogg88 I have a very similar issue. We (my dealer and myself) migrated my system to a new EA5 controller. After the migration we then reached out to Epic Systems, so we could reactivate the driver. After the reactivation and upon testing the system, none of the Triggers / Commands we were working. Also, we could not add new Triggers / devices and have them discovered by Alexa (via website or app). Nothing would work on the discovery side. At this time we we were using Epic Systems driver version 210. After a couple of emails with Epic Systems, they suggested updating the driver via their website, to driver version 300. We did this, and unfortunately the results were / are still the same. No matter what I do, in terms of adding any Triggers / Devices, the "Discovery" will not work via Alexa. I tried updating the driver two different ways. Initially, just updating over the existing driver and making sure the sync the "Local & Controller" to the newest version. Rebooting the EA5 numerous times. When this did not work, I deleted the driver from my project.... rebooted controller, manually added driver version 300 to the project,... then reactivated it...., rebooted controller... and still no luck. I sent several emails to Ari @chopedogg88 on this issue... with hopes his team can figure / sort it out. So currently I'm in a very similar situation as you @jsimon77, where I can not add any Triggers / Devices, and have Alexa properly discover them. Ari and his team are really good at sorting these things out..., so just hoping to hear back from them with a fix. Other random FYI, I / we are also running the latest versions Composer (on the EA5 and programming software)

Major thanks to @jackstiffer, I can confirm the following for all (*** Specifically for those running C4 OS 3.0, very important ***) - Upgrading to the V2 Driver does work.... and yes you must completely remove the old driver, and upload the new one. - You do lose all programming and triggers as @chopedogg88 has stated, so save / backup all your info elsewhere before removing the old driver and uploading the new one (makes reprogramming easier also). At least for me it made things much easier, as I have over 100 triggers / verbal commands. - As a precaution I would also backup C4 before doing any of this, and copy the Activation key for the Epic Systems Echo Driver (you'll need this to activate the V2 Driver) - Lastly, I did set the IP of my Echo device to a newer model (not Gen 1), not sure if this was necessary... But I can 100% confirm all Gen 1 / Legacy devices will / do work. I'm able to give all voice commands to a Gen 1 Echo Dot, and everything functions as it should. - Might also be a good idea to reboot the C4 controller, after all updating / programming / testing. Old habit, I guess. Hope this helps someone...time to sleep.

Can you further explain...., I have driver version 110. I also have multiple Echo Devices, 1st, 2nd, 3rd... Gen and so on. In C4 the driver is set to an original Gen 1 Echo dot. Could we / one not just change the IP in the driver settings to a newer Gen model? Would that work @chopedogg88? If not...do we have to change / update the IP of the Echo device to a non Gen 1 model....then reprogram and rediscover all triggers? Any advice is appreciated. Also @jackstiffer what was your original Echo model, and what model did you upgrade to? Thanks.

@dcovach I now understand, I'll need to get my deal involved to address this. I'm 100% sure, he'll do this quickly (he's a great dealer to work with). Like, I said before, I just like to learn / understand things. There are a lot of experienced people on this forum, and a lot of useful knowledge / help can be gained, by reading / discussing things with each of you. That's all that is going on here. Hopefully with more time and experience programming my setup, I'll be able to provide assistance / advice to other users, one day. Thanks for the advice.

I know. I have remote access to Pro via my dealer...if / when I run into these issues. I rarely use it, as that's more of a thing for my dealer to use. And of course, I always backup my project before making any changes.

I'm not, my dealer did the initial build / setup. I'm doing the majority of the customization / programming via Composer HE. But from time to time, I run into issues where I need to you use Composer Pro. My dealer generally addresses these items, but he's on vacation for the next week. Don't think, I'll be able to access the dealer site. I"m more of a hands on person, so I like to learn / understand these things.

Sorry, C4 novice here, trying to learn. "SShed in to the controller" could you explain?

Having some problems removing, then reloading a driver in Composer. I was advised to do this, via support for this driver. I was having some issues with it's functionality. Trying to properly remove the "Local" and "Controller" version of a driver in my C4 build. When I do this, I always "Refresh Navigators" and Reboot the Controller. Afterwards I attempt to add the driver back to the project. I continue to receive the following message: "Update Failed. Reasons: Versions are equal. Do you want to overwrite the exiting driver?" This is making me think the driver is not completely removed....but when I check / manage drivers, and even look in the local driver folder via the PC with composer... I do not see this driver. Has anyone run across this before? Any advice? Thanks.