dutsnekcirf Posted September 25, 2019 Share Posted September 25, 2019 A few weeks ago I got the Epic-Systems Echo driver installed and working. And then I went on a business trip and as these things typically go, while I'm away, something breaks. This time it appears to be the Alexa integration. Whenever I ask Alexa to perform any task related to my system it says it's not responding. I've gone into the alexa.amazon.com account and told it to forget everything. I then told it to discover devices and at the same time sent discovery from the driver. Alexa rediscovered all of my devices but it's still stating that they're not responding. Not sure what to do at this point. Quote Link to comment Share on other sites More sharing options...
bk Posted September 25, 2019 Share Posted September 25, 2019 Check Epic Systems website, a recent Amazon update broke the driver. I'm still waiting on a response to my question as to when there will be a fix in place for pre OS3 systems. It is taking a while! Quote Link to comment Share on other sites More sharing options...
chopedogg88 Posted September 25, 2019 Share Posted September 25, 2019 Bryce, we are working on a fix, hopefully will have something within the week if all goes well. With technology, I'm sure you know that you can't always provide an answer on when something will be fixed until you actually fix it Quote Link to comment Share on other sites More sharing options...
dutsnekcirf Posted September 25, 2019 Author Share Posted September 25, 2019 Thanks for the heads up. I guess I could have checked the website first. My apologies. I'll standby for an update. Quote Link to comment Share on other sites More sharing options...
dutsnekcirf Posted September 25, 2019 Author Share Posted September 25, 2019 Just read the update on the website. One quick question. The update states that "this is due to a firmware update that Amazon is rolling out to older Echo Dot (Gen 2) devices." If I were to upgrade my Echo Dot to a newer generation would this be enough to get me up and running without the need to update my driver? Quote Link to comment Share on other sites More sharing options...
chopedogg88 Posted September 25, 2019 Share Posted September 25, 2019 No the Gen 2 Dots are now working the same as Gen3 Dots basically. Need the v2 driver regardless. You could try a Gen 1 Echo... Mine is still working okay wirh v180 but who knows if Amazon will update firmware on those as well at some point. They may have already and mine just hasn't updated. Not sure. Sent from my SM-G975U using Tapatalk Quote Link to comment Share on other sites More sharing options...
dutsnekcirf Posted September 25, 2019 Author Share Posted September 25, 2019 vOkay, So I've updated to the v2 driver and the documentation tab indicates that I have version 200. Now I'm trying to reprogram everything, but it won't allow me to recreate my triggers. The "delete Triggers" drop down is empty. Is there something I missed? The Lua tab is showing the following error: Adding new trigger named: Alexa Routines Error duplicate Trigger name: Alexa Routines Quote Link to comment Share on other sites More sharing options...
chopedogg88 Posted September 25, 2019 Share Posted September 25, 2019 Delete the driver from the project and add it back Sent from my SM-G975U using Tapatalk Quote Link to comment Share on other sites More sharing options...
chopedogg88 Posted September 26, 2019 Share Posted September 26, 2019 did that fix it for you? Quote Link to comment Share on other sites More sharing options...
shawkyns Posted September 26, 2019 Share Posted September 26, 2019 hi so v1 driver is no longer working. V2 driver works but requires os3? but you are coming out with a fix for the v2 ddriver for 2.0 OS? Quote Link to comment Share on other sites More sharing options...
prabeau Posted September 26, 2019 Share Posted September 26, 2019 V1 is working for me Quote Link to comment Share on other sites More sharing options...
ee999 Posted September 27, 2019 Share Posted September 27, 2019 I'm on 2.9.1 with the 110 epic driver and mine stopped working. OS3 not an option for me as my controllers are hc800 & 250s. Quote Link to comment Share on other sites More sharing options...
Gary Leeds UK Posted September 27, 2019 Share Posted September 27, 2019 hc800 on OS3 using V2 driver and stop working too Contacts my Echo every few hours (ad hoc) but unable to programme Quote Link to comment Share on other sites More sharing options...
chopedogg88 Posted September 27, 2019 Share Posted September 27, 2019 Please post a screen shot of the driver properties Sent from my SM-G975U using Tapatalk Quote Link to comment Share on other sites More sharing options...
prabeau Posted September 27, 2019 Share Posted September 27, 2019 I am on 2.9 with version 180 of the driver. So far so good. Planning on going to 3.1 and getting ready for this issue. On your site I read "be sure to copy over any trigger programming that you want to retain into Macros." I am a HE user and can't quite figure out how to go about this ? Is this a dealer only capability ? Thanks Quote Link to comment Share on other sites More sharing options...
chopedogg88 Posted September 27, 2019 Share Posted September 27, 2019 Just to be clear - OS 3 or 3.1 isn't what breaks the v180 driver - its the Amazon firmware update on the older Gen 2 Dots that does. Regarding Macros, you need to go to Agents-Macros (add that Agent if you don't already have it in your system by clicking the Add button at the top), then create a Macro for each bit of programming that you have, and copy the programming from the driver into the Macro's programming. Then in the v2 driver, just execute the macro in the driver programming, rather than programming it in the driver ON/OFF/UP/DOWN/SET events directly. Alternately, if you have a dealer you are working with, they can use Composer Pro's Virtual Director option to open up a backup of your project, and then just copy/paste the programming from the v180 driver into the v2 driver (you'll have to manually re-create the trigger names, but that shouldn't take long...usually less than 5 minutes). If you don't have a dealer, I am a dealer and can do it remotely for you (@ $75/hr) thanks, Ari Quote Link to comment Share on other sites More sharing options...
ee999 Posted September 27, 2019 Share Posted September 27, 2019 Here is a screen shot of driver properties and info [license key erased]. As I mentioned I'm on 2.9.1 and lost alexa control. Thx Quote Link to comment Share on other sites More sharing options...
chopedogg88 Posted September 27, 2019 Share Posted September 27, 2019 I was asking for screen shot from Gary Leeds actually. I know it won't work on v110 driver. You need v2 driver and must be on OS3+Sent from my SM-G975U using Tapatalk Quote Link to comment Share on other sites More sharing options...
ee999 Posted September 27, 2019 Share Posted September 27, 2019 well that's unfortunate, as OS3 isn't possible for me due to the controllers and touchscreens I currently have. Quote Link to comment Share on other sites More sharing options...
chopedogg88 Posted September 27, 2019 Share Posted September 27, 2019 Yeah hard to stay on top of the latest software with old hardware unfortunately. Especially when multiple companies/variables involved.Sent from my SM-G975U using Tapatalk msgreenf 1 Quote Link to comment Share on other sites More sharing options...
prabeau Posted September 28, 2019 Share Posted September 28, 2019 11 hours ago, chopedogg88 said: Just to be clear - OS 3 or 3.1 isn't what breaks the v180 driver - its the Amazon firmware update on the older Gen 2 Dots that does. Regarding Macros, you need to go to Agents-Macros (add that Agent if you don't already have it in your system by clicking the Add button at the top), then create a Macro for each bit of programming that you have, and copy the programming from the driver into the Macro's programming. Then in the v2 driver, just execute the macro in the driver programming, rather than programming it in the driver ON/OFF/UP/DOWN/SET events directly. Alternately, if you have a dealer you are working with, they can use Composer Pro's Virtual Director option to open up a backup of your project, and then just copy/paste the programming from the v180 driver into the v2 driver (you'll have to manually re-create the trigger names, but that shouldn't take long...usually less than 5 minutes). If you don't have a dealer, I am a dealer and can do it remotely for you (@ $75/hr) thanks, Ari Thank you, will probably go with my dealer, but as you pointed out seems like my echo' s have no issues . Thanks Quote Link to comment Share on other sites More sharing options...
samsong Posted October 6, 2019 Share Posted October 6, 2019 Hi, can we have an update on the driver progress for composer 2.10.6 ? thanks Quote Link to comment Share on other sites More sharing options...
Gary Leeds UK Posted October 6, 2019 Share Posted October 6, 2019 On 9/28/2019 at 12:09 AM, chopedogg88 said: Yeah hard to stay on top of the latest software with old hardware unfortunately. Especially when multiple companies/variables involved. Sent from my SM-G975U using Tapatalk Sorry did not see this will sort Quote Link to comment Share on other sites More sharing options...
dcovach Posted October 6, 2019 Share Posted October 6, 2019 Hopefully its announced here but you can also check the website. Quote Link to comment Share on other sites More sharing options...
samsong Posted October 6, 2019 Share Posted October 6, 2019 Yeah but the website isn’t clear about composer 2.10.6 compatibility with v2 driver Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.