Jump to content
C4 Forums | Control4

DRP

c4Forums Member
  • Posts

    12
  • Joined

  • Last visited

  • Days Won

    1

DRP last won the day on June 26 2022

DRP had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

DRP's Achievements

  1. Thank you msgreenf. C4 seems to be controlling the Integra AVR, but not the Pioneer Kuro TV. Checked to see that the RF emitter is in place. Everything operates correctly with the discrete remotes. Not experiencing any problems with lighting, etc. I can't tell if there was an automatic update that may have affected this. We're on the current OS, and on reasonably up-to-date hardware.
  2. Hmm, remotes, C4 app, and voice control has suddenly failed on AV only (Sep 2022). All other 50+ devices working. Any ideas? HC800, OS 3.3.0, no other changes.
  3. For some reason, the original "fix" for the Alexa driver, v114, was working better for us than v115, v116, and v117. We are now running the latest C4 OS on relatively recent hardware, so that isn't it. C4 times out is set to return an error code to Alexa just a second too quickly before the Alexa command is executed, about 3/4 of the time, requiring the voice command to be executed twice. As near as I can tell, Alexa requires 2,000ms, but C4 times out after 1,000ms.
  4. Success! Alexa driver v113 seems to have fixed the problem with C4 OS 2.9 that v112 broke. And so far, it's even better--C4 is no longer requiring the Alexa command to be repeated for each action, as it has for the past year or so! Many thanks to Darin, the development team, and the C4 community for rallying around this issue. DRP
  5. Thank you Darin. Will you post to this thread when driver v113 is pushed out?
  6. Almost all of my devices needed to be told twice to turn on or off, starting about a year ago. But even that was better than nothing...
  7. Thank you Darin. I don't know if my system running 2.9.1 received the v112 driver update, but it was working for several years prior to this week.
  8. Thanks all for the additional insights. Sorry to hear that so many people are having a similar problem. In my case, it was not due to a C4 OS upgrade (as my controller is too old to run 3.X). BTW, I see all of my C4-controlled devices, enabled, under "Voice Control" on customer.control4.com.
  9. Yes, I went through a similar process. I'm still running OS 2.91, and auto-upgrades are not enabled. One small clue may be that when I try to activate one of the "unavailable" C4 devices, Alexa flashes an error message that says "Server is unresponsive." This sort of suggests an Amazon problem, but all of the 14 (!) other smarthome platforms are working perfectly with Alexa.
  10. Thank you South Africa. I did log in to my.control4.com this morning, and all of the devices have the "enabled" box checked. C4 is working from the wall switches and the app, so the problem seems to be in the interaction between Alexa and the system. DRP
  11. Yesterday, C4 suddenly stopped responding to Alexa commands, either through the echo devices or the app. It had been working for several years, although most commands needed to be repeated at least twice. But that was better than nothing. I read Derrick's very helpful troubleshooting tips from the 2017 thread on this topic, but the site suggested I start a new thread since the previous one is so old. (Derrick has saved the day for me more than once). In addition to unlinking and re-linking, I have rebooted all of the controllers. Also verified that my 4Sight account is active. Upon re-linking the C4 skill, Alexa is unable to find any C4 devices. (Alexa is working perfectly with my Next, Ring, Sonos, myQ, TP-Link, and other devices. Any suggestions? My dealer is unfortunately unable to help.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.