Epic Driver for Alexa stopped discovering new devices

[jsimon77]

Hi All,

I'm looking for some help.  I have the epic drive both in my main house and my vacation house.

My main house is working fine and let's me add new devices.  This version of the driver has a button I press called "Send Discovery"

I my vacation house, this version of the driver does not have the send discovery button under actions but when I tried adding triggers via telling Alex to discover new devices it worked fine and added the triggers as normal.  But now I'm trying to add a few more triggers and no matter what I do I can't get it to discover the new devices that I've added in composer.  I can see in Lau when I tell Alexa to discover new devices it's connected but not finding anything.

I've reached out to Epic.  They asked for my driver version which I provided but I never heard back.  

Any help would be much appreciated!

[becnel51]

@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)

[jsimon77]

On 4/16/2021 at 7:08 AM, becnel51 said:

@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)

Thanks for this information.  I'm stilling having issuues.

On main house system the triggers that I had are working but having a very difficult time adding new triggers.  I was able to successfully add new triggers last week but when trying today it will not work.

The vacation house system still having the same issues as before.  I hope that Ari and team can get it figured out as his system is so much better than the native C4 version.

[me23]

Any update on this?  I can add triggers but Alexa will not discover them. 

[jsimon77]

3 hours ago, me23 said:

Any update on this?  I can add triggers but Alexa will not discover them. 

No update. I stopped hearing back from Ari the developer. I continue to have the same problem. Not sure what to do at this point…

Keep me posted as well please if you hear anything. 

[me23]

Did you see this on their front page?

NOTE:  If you are using version 110 or 180 of our driver and your triggers have recently stopped working - this is due to a firmware update that Amazon is rolling out to older Echo Dot (Gen 2) devices.  You will need to install our V200 driver, which can be found HERE. v200 REQUIRES OS3. You will also have to remove the old driver from the project and then add the new driver, so please be sure to copy over any trigger programming that you want to retain into Macros, or backup your project file, and then you can copy/paste the programming from the backup using Virtual Director.

 

Not sure if this would help or not.   I'm still on OS 2.10.3  Guess I need to upgrade. 

[GusSafadi]

Unable to activate driver V200 on OS 3.2.1; Send support emails but have not heard back yet. Driver stuck on "Activating license". Uninstall, reboot, reinstall has no effect

 

Update: Ari was very helpful. Fixed. License had to be reset

[eddy.trochez]

On 4/30/2021 at 12:40 PM, jsimon77 said:

Thanks for this information.  I'm stilling having issuues.

On main house system the triggers that I had are working but having a very difficult time adding new triggers.  I was able to successfully add new triggers last week but when trying today it will not work.

The vacation house system still having the same issues as before.  I hope that Ari and team can get it figured out as his system is so much better than the native C4 version.

Just out of curiosity. Why aren’t you using the native C4 driver?

[zaphod]

I think it is faster for one thing as I don't think it is as dependent on the cloud.

 

[msgreenf]

please explain how something alexa is not dependent on the cloud

[zaphod]

That's why I said "as" dependent rather than not dependent. 

Not 100% sure but it appears to me that the native C4 driver hits the cloud twice - first it hits Alexa to interpret the command and then hits the C4 cloud to execute on the command.  I think the Epic driver does the second part, command execution, locally.  But you or Ari can confirm.  If this is correct that is one reason why the Epic driver would be a bit faster.

[msgreenf]

I'll let Ari comment on his driver - but my understanding is that it emulates a wemo device and doesn't use a secondary service like Control4 does

[chopedogg88]

1 minute ago, zaphod said:

That's why I said "as" dependent rather than not dependent. 

Not 100% sure but it appears to me that the native C4 driver hits the cloud twice - first it hits Alexa to interpret the command and then hits the C4 cloud to execute on the command.  I think the Epic driver does the second part, command execution, locally.  But you or Ari can confirm.  If this is correct that is one reason why the Epic driver would be a bit faster.

That's correct - its not reliant on the Control4 cloud services to communicate to the controller - it makes a direct IP connection from the Echo device to the controller.

Unfortunately due to some changes that Amazon has made to their newer devices, the device discovery is currently broken unless you are using a Gen 1 Echo or Dot for the device discovery/communication with the driver.  Any model of Echo device can be used to issue the commands, but at least one Gen 1 Echo is required.

[chopedogg88]

2 minutes ago, msgreenf said:

I'll let Ari comment on his driver - but my understanding is that it emulates a wemo device and doesn't use a secondary service like Control4 does

It emulates a Hue device (not Wemo), but same idea.

[zaphod]

Which is why I have a Gen 1 Echo sitting on my desk!

[msgreenf]

1 minute ago, chopedogg88 said:

It emulates a Hue device (not Wemo), but same idea.

ahh - ok! thanks for the correction

[jsimon77]

5 hours ago, chopedogg88 said:

That's correct - its not reliant on the Control4 cloud services to communicate to the controller - it makes a direct IP connection from the Echo device to the controller.

Unfortunately due to some changes that Amazon has made to their newer devices, the device discovery is currently broken unless you are using a Gen 1 Echo or Dot for the device discovery/communication with the driver.  Any model of Echo device can be used to issue the commands, but at least one Gen 1 Echo is required.

Still need some help.

1) Upgraded to v200

2) I'm using a gen 1 alexa

3) I was able to add a test trigger and Alexa discovered it.  But that trigger is not showing up under programing?

4) I tried to add a second trigger and Alexa would not discover that one?

5) I tried to delete both triggers (choose trigger and hit set) but the trigger will no delete?

Please help.

[chopedogg88]

does the driver show as "Activated" under the license key?  sounds like the driver became de-activated (did you change controllers?)

[jsimon77]

2 minutes ago, chopedogg88 said:

does the driver show as "Activated" under the license key?  sounds like the driver became de-activated (did you change controllers?)

Still shows activated.  Screen shot here - https://www.dropbox.com/s/0cd8j86ylf2q91n/Screen Shot 2021-05-25 at 5.35.23 PM.jpg?dl=0

 

This is the error I got when I tried to add the 2nd trigger. - LUA_ERROR [id: 644][name: Amazon Echo][file: amazon_echo.c4z][method: OnPropertyChanged]: [string "local j10f={[1]="\102\97\108\115\101",[2]=1..."]:1: attempt to index local 'cjbGws' (a nil value)

[jsimon77]

15 minutes ago, chopedogg88 said:

does the driver show as "Activated" under the license key?  sounds like the driver became de-activated (did you change controllers?)

Added a video as well to see if it helps you see what's happening? - https://www.dropbox.com/s/lku42rzc0vcqvet/Screen Recording 2021-05-25 at 5.42.30 PM.mov?dl=0

I was also updated to Director Version 3.2.2.598005-res

[jsimon77]

I had my dealer uninstall and reinstall and now it is working at home location.

For the other location I'll bring up a Gen 1 Alexa with me and try that.

[jfh]

On 5/22/2021 at 10:59 AM, eddy.trochez said:

Just out of curiosity. Why aren’t you using the native C4 driver?

And another key reason the Epic Systems driver is better than the C4 one is that it supports levels (SET) which provides *significantly* more programming flexibility than just off/on.  If I had to implement my Alexa code using the C4 drivers it would be ridiculously complicated and require a massive number of dummy devices to be created.  

[RyanE]

2 hours ago, jfh said:

And another key reason the Epic Systems driver is better than the C4 one is that it supports levels (SET) which provides *significantly* more programming flexibility than just off/on.  If I had to implement my Alexa code using the C4 drivers it would be ridiculously complicated and require a massive number of dummy devices to be created.  

To clarify, I assume you mean you have the option to create SET LEVEL commands as a part of the 'voice scenes' themselves, not for actual light control, since Control4 already does support setting discovered lights to specific levels through Alexa (Set Office Light to 20, Office Light up 10, etc.).

RyanE

 

[jfh]

7 hours ago, RyanE said:

To clarify, I assume you mean you have the option to create SET LEVEL commands as a part of the 'voice scenes' themselves, not for actual light control, since Control4 already does support setting discovered lights to specific levels through Alexa (Set Office Light to 20, Office Light up 10, etc.).

RyanE

 

Not sure I understand.  With the Epic driver I can have an Alexa routine set a light level to x and the driver will have the light level available as a variable I can program off of.  For example, I have a device/light called “Routine” so I can have an Alexa routine “The cleaners are here” that sets light level on “Routine” to 27.  When the Epic driver sees Routine set to level 27 it runs the code to do whatever is needed when the cleaners are here.  Unless something has changed I don’t think I could do the same with the C4 driver.

[RyanE]

1 hour ago, jfh said:

Not sure I understand.  With the Epic driver I can have an Alexa routine set a light level to x and the driver will have the light level available as a variable I can program off of.  For example, I have a device/light called “Routine” so I can have an Alexa routine “The cleaners are here” that sets light level on “Routine” to 27.  When the Epic driver sees Routine set to level 27 it runs the code to do whatever is needed when the cleaners are here.  Unless something has changed I don’t think I could do the same with the C4 driver.

With the Control4 "Voice Scenes" driver, your voice scenes themselves can only be on/off, but I don't think there's anything that would keep you from using a dummy light that gets set to a value in an Alexa routine, and then checking that light's value.

That said, I've never used the Epic driver, and haven't setup any Alexa routines.  If the Epic driver is working for you, I'd say the best thing is of course to keep using it.

RyanE