Don Cohen

At work we jokingly call it the triple corndog menu

Just to wrap this up, I went ahead and used the IR Driver, and everything seems fine. I haven't used it a lot, but it seems fine.
Appreciate the help here.

Good thinking about the BT keyboard, I still have one MX for a couple of rooms! Was handy before Apple integrate ATV to everything!
We had issues with Intrinsic IP driver when Apple moved to tvOS 15 and broke the known API’s, I had since then fitted an IR bug to every ATV I have, I kept them just in case!
Jesse IR driver is superior IMO as it provides a replica of same features of the original Apple Remote no one else managed to create, Menu double click and u will have App switching so u can close apps, etc. but if this not an issue then Intrinsic is great Driver as well, I used both for a long time but switched to native C4 driver (works well, 0 issues) last Xmas when upgrading to EA5!

U can use IP with Intrinsic driver (50 UKP), or Jesse IR driver (free), both does not need Apple device to work, but u will suffer without an Apple device thought, It will be hell to type passwords all the time on the Apple TV!

You need to be on the same network when setting up the Apple bridge 

Not that i've ever heard. Isn't that fun?

The best part is when the owner finally comes in town a month later and you get ahold of their iPhone and then it screen locks every 5 seconds and you eventually just give up and ask them for their pin code. 

Use an IR driver for AppleTV. One in the database, and better one here:
 

This was a few months back, but I installed a Motion Sensor at our Front Door, since that is where most of our Amazon and other Deliveries take place, and typically they don't knock or ring the bell.  Using a text to voice engine I found on the web, I created an mp3 file: "Someone is at the front door.  Someone is at the front door."
So when motion there is detected, I programmed a few actions:
The T3 in our Family Room, where we tend to hang out, brings up the Front Door Camera (using the DS2 Mini present there) An announcement is made on the T3: "Someone is at the front door.  Someone is at the front door." An email is sent to me, with a camera snapshot from the DS2 Mini. Nothing fancy or elaborate but I really like having this in place.
Occasionally the dog next door will check out the front porch and trigger a false positive, but that doesn't happen often.

All (3) of my Roku devices stopped responding in C4 yesterday as well.  I went in to Composer HE, rescan for players and then set them again by picking the player for that room.  All are working now just fine now.  Interesting.

Dan. We did 10-20 second reboots a few times. We just tried the 2 minute reboot per your suggestion and it fixed it.
so thanks for your input  
 

We just sent the driver over to jvc for testing. We tried factory reset. Non sddp, and sddp. Etc. 

I suspect you're on the right path there.
Always a good idea too

I don't know how your wifi is setup. Many just setup a single SSID as either dual band (5 and 2.4) or single band 5.
We add a dedicated 2.4 only SSID, and stick all the stupid, poor, unknown quality internet of things devices on it.
That keeps them off the 5 band, many of their radios are garbage, many get confused by dual band, so we isolate them.
And if one of them gets hacked, goes rogue, we have a questionable wifi strength or something, I can turn their SSID off real easy and block them all in one stroke.

I've used the TPlink piece a couple of times for similar use, and it's been fine. I've even setup a couple as Internet less routers for little Control4 systems. (ie a simple lighting system)
I'd recommend a 2.4 only SSID, and attach it to that.

Just to close this up:
While waiting for my webhost to get back to me, I did change my password to be compatible with the Chowmain SMTP Driver, and so got that working.
My webhost did then get back to me, and using a different Port setting than what they originally recommended, it is now up and running again. I asked if Gmail was being used, but they said no.
Interestingly, I couldn't get Gmail credentials to work on the DS2, using a new App-generated Password. This does work with the Chowmain Driver, so I'm not sure why it won't with the DS2.
But regardless, I now have 2 options to use here, and my problems did not originate with anything Control4-related. Purely my webhost.

Missed that… sorry! And good luck!

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

@Don Cohen Happy to help where I can.

Really appreciate this, @Darin, C4 PM UI. I updated the Driver, rediscovered devices, and I now have voice control over my Bluray players once again.
It's really great having you guys on the forum and available and receptive to fixing problems when they arise!

Really appreciate this, @Darin, C4 PM UI. I updated the Driver, rediscovered devices, and I now have voice control over my Bluray players once again.
It's really great having you guys on the forum and available and receptive to fixing problems when they arise!

Alexa driver v113 is in testing now with fixes for the 3 issues mentioned in this thread, so we should have those fixes pushed out to you guys soon.

DVD proxy issue was confirmed and they are working to fix it now.

This is not my area of expertise, but the PM and engineers that would don't have C4Forums accounts so I'll pass along what they said.
 

I'm having similar problems, though more selective.
I have multiple virtual Devices for my Theater (Netflix, Amazon, HBO Max, Hulu, etc.) so I can turn any on with Voice Commands. I've used these for years. Most of these are still working, but for some bizarre reason, neither of the Bluray Player players are being recognized. When I log into my Alexa account, they are listed there as devices, but strangely when I log into my.control4.com they're not (while all the others are listed). They have been there in the past, since I have been using them for several years, customized the name, etc.
I have tried multiple things to get this working:
Reboot Controller Reboot the Echo dot I'm using Unlinked the Control4 Skill in the Alexa interface, rebooted the Controller again, and then relinked Rediscovered devices through Alexa multiple times Cleared the cache on the Alexa App, checked for updates (last update was June 1) I even removed one of these bluray devices in the Alexa app, hoping that it would be 'rediscovered', but no joy. It's now nowhere to be seen I renamed one of the devices for the same reason, to see if that would trigger re-recognition, but also no joy The only thing that has changed is Control4's release of OS 3.30, and while I haven't yet upgraded, the release and system changes actually fixed another problem I've had for months, where Alexa would respond "Hmm..I'm having trouble reaching null" whenever I gave a voice command to turn on any of these devices (and which did in fact turn on, despite this odd error).
So no matter what I do, I can't get Alexa to respond to voice commands to activate these 2 bluray players, even though they were shown as devices in the Alexa App. And presumably because there's an issue there, my.control4.com isn't seeing them either. Very strange...