lukas.polivka

Emotiva is VERY specific about the conditions/environment of their products in regard to warranty repair so I would caution using a 3rd party driver. I have seen their preamps have software/processor issues for odd reasons. The costs and efforts for them to make/compete in the AVR/processor space is difficult with all of the different licenses and codecs etc…. I use their amps in almost every home theater instal but I tend to stay away from their processors for some of those reasons. 

I've added it to the instructions as an alternative

Hey, thank you for finding and posting it - myself and I know several other dealers have asked repeatedly, through numerous channels, if something like this was available, and for me personally no searches (outside of 'official' channels) had come up with any alternatives.
 
To be very clear:
I'm just tagging along on this one - my link and post are just how I made it work and most certainly not any claim of ownership of the process!

Hmm. My virus scanner is finding an virus in the 2.96 an 2.92 versions - Just FYI. May want to check your files, others aren't getting flagged.'Course it may just be my virus scanner.

@Ryanjackson
Here's the setup that worked for me on a table top at least:
https://www.dropbox.com/sh/na5pdagpn0jj2ua/AADoeYaiUDgjM66-qSpd7pXta?dl=0
Includes image, dev tool and driver assistant I used plus instructions combined from @Amr, @lukas.polivka and what ended up working for me.
It's only 1 out of 1, but I'll be keeping this 'tool' in my back pocket as a final attempt in case I come across a client with the issue (we've had two over time that were under full warranty two that got a repair option, and only one fullyout of warranty - who hasn't pulled the trigger on replacement yet, so I'll offer to try it for them)

HYG: On a Windows PC/Laptop:

1)Install Rockchip_DriverAssitant_v5.1.1
2)Install RKDevTool_Release_v2.79
3)In RKDevTool open config file change language to 2, [Language] Selected=2, save file
4)Grap a Data Micro USB Cable, not power one, make sure of this to have successful flashing
5)Open RKDevTool, connect your T3 screen USB to computer while putting it in Flash Mode, for TT press “Power” with “Volume up” while plugging in the USB, for wall I think u press “Reset” while plugging in the USB to laptop or PC
6)It should show one device connected!
7)U go to Upgrade firmware tab, Use "Firmware" to load the image, then "Upgrade" to write the image to T3
8]It should show progress, wait till its 100% complete, and in the screen if all good it will say all is good, now the screen will be rebooted and u have ur T3 back!
9)If you keep getting "Match device type failed, stop running!" try pressing the switch button first in the tool then hit upgrade
10)Update/Downgrade to your latest OS3 release!
11)Google the programs, download and install, use this for T3 image: https://mega.nz/file/gaJl1IrY#pGEN1sIxxyL9v8hXQx9lbNlyZ4rVfHAXBBCcOE1rpMY
You will thank me later, I have a PayPal if you want to donate 🤓 as I had just lost a cheap source of bricked screens that I bought over the past year!
 

Hello your site is down and email is down also are you sure, that driver is still available, how to order than?
Thank you

Hi Darin, is the Battery Level Summarizer driver available yet? I cannot see it in the online database.

Happy to announce that as of today, WebView drivers can now work on iOS & Android mobile devices with 321.46+ OS 3 mobile app and a controller running OS 3.1.3+.  However, it does require updates by the driver writer using the latest DriverWorks SDK to take advantage of this new functionality.  If you have WebView drivers you or a client uses that you'd like available on mobile, you'll need to reach out to driver writers with an update request to extended their driver with mobile support.

Hi,
Version 25 of the Satel Integra driver is now available, adding OS 3.2.1 support.
You can find more information about this driver on our website: www.mwiz.pl
You can contact us at info@mwiz.pl
 

Hi,
It's been a while since we have last visited the forums - there is a new version of the driver available now:
 

We only required MQTT to publish data to ThingsBoard. I ended up writing our own driver last night to do this instead and its working well so far.

You might also want to take a look at Control4’s Room Control driver and its events (e.g. Entered Listen Mode, Entered Watch Mode etc.) and variables (to create conditionals to test whether you are in the Watch mode or Listen mode). It’s usually pretty useful for this kind of programming.

We did that in the last version already.  We got a bit impatient waiting for Control4 to implement dynamic speeds so we forked the driver.  Just select the one with the speed that suits not as elegant but it works

You might also want to take a look at Control4’s Room Control driver and its events (e.g. Entered Listen Mode, Entered Watch Mode etc.) and variables (to create conditionals to test whether you are in the Watch mode or Listen mode). It’s usually pretty useful for this kind of programming.

As promised we got this working. Problem was a missing app on the iPhone.

For anyone struggling to get the Apple TV 4k driver working make sure the Apple home app is installed and stays installed.

tell that to people who's significant others do not like clutter, or that have dogs or children who run around the house and knock into things....
Just a personal preference that's all.

no, only current workaround is to install BlueStack and then run the Android app on WIndows/mac

Lukas,
Not a problem.
I actually do have a sample MQTT Client driver that I can email you which provides a template of how you can interface to the MQTT bridge driver, if you send me an email, I'll pass it on.
Thanks
David

Happy Monday everyone -
I have a working C4 Roomba driver and am looking for a few testers to help shake it down - please msg me if you are interested.
A few notes:
The driver is stand-alone (no external/cloud API calls, talks directly to the roomba) Works with "new" iRobot MQTT interface (NOT "old" HTTPS API) I'm working with model 980 It claims to be up-to-date, running firmware v2.4.6-3 Current functionality: Find Roomba on network Get/Extract username and password Basic commands: Start, Stop, Pause, Resume and Dock Let me know if you are interested.
Thanks!

Hi Folks,
I'm the manager of the Mobile and Embedded UI teams at Control4. Thank you for bringing this to our attention! I can assure you we didn't intentionally disable VPN use. However, VPN use through the app isn't an officially supported feature. Currently, 4Sight is the only supported way to connect remotely.
Our apps rely on multicast networking and SSDP to find the primary controller's IP address. Most VPNs are not enabled to transmit multicast packets to a client device. 
In OS 2, the apps had a manual IP address setting. By using the manual IP address setting, you could bypass the need for multicast. To simplify app configuration for the customer, we removed the manual IP setting. We are currently evaluating bringing back the manual IP address setting to provide a workaround for misconfigured networks.
Also, VPN does work on Android as long as the app has connected one time. VPN works on Android due to a speed optimization that caches the last known IP address. As long as the address hasn't changed, VPN will continue to work. We are also evaluating adding that optimization into iOS to speed up the iOS connection time overall. As a side benefit, that will also enable VPN access, if we decide to add it to iOS. 
Thanks again!
Joel

If the devices you want to control are 433mhz you can send a mqtt message from programming with the correct RF info and use it for control.  They do need to be flashed to tasmota from the stock firmware.  They are well loved in the DIY community for adding cheap sensors ie water or contact.

Breaking the law? Not so much unless they signed a non disclosure which means civil not criminal penalties. 

good way to get banned

Actually Control4 has been using SIP for their intercom since the beginning. There's even a generic SIP client driver provided by Control4 and a generic SIP door station driver provided by an external developer. SIP is not Crestron's protocol at all. It's an open IETF standard/spec. https://tools.ietf.org/html/rfc3261