lukas.polivka

Those “real” / official instructions didn't work for me on most touch screens where I encountered this bootloader error. Using RKDevTool helped in most cases, but yeah, I came across some T3 which I was unable to recover either way.

Could be special characters or spaces in the path. Move the folder somewhere else.

Also found this: https://emotivalounge.proboards.com/thread/56879/rmc-owners-thread-post-firmware?q=ip+control (may have been fixed in the firmware in the meanwhile though)

This is probably an old piece, out of warranty/support, but thanks for the warning.

Hi! Any luck with the Emotiva RMC-1 IP driver? URC Total Control 2.0 driver seems to exist, albeit only 1-way: https://cdn.shopify.com/s/files/1/2572/6926/files/URC_Total_Control_2.0_Emotiva_IP_Control_Integraiton_04082020_rev1.0.pdf?v=1586459947

Nevermind, seems like the manufacturer already has a working driver (written by BlackWire Designs, but it's not on either website for some reason). As far as I can tell it's free. So just contact your supplier/distributor/McIntosh directly.

Hi! Does anyone have the serial protocol documentation for this device? I tried looking for it on the manufacturer's website without success. A dealer tried using the driver for C2500 but it does not work, some of the commands are different. I was able to figure out only some of them. First of all, the commands do not specify any zone (Z1, Z2) so the string matching patterns had to be modified. Then instead of VST num it uses VOL num to set volume level, PWR 0 and PWR 1 to turn it off/on instead of PON and POF. I wasn't able to figure out the volume up and volume down commands. And inputs are behaving erraticaly. If you choose an input using the front panel dial, you get e.g INP 9 back, but when you select input 9 using INP 9, the device returns INP 9... but actually always switches to an input that's IIRC one higher (or lower).

You need to press & hold the unlabeled pinhole (for IW) or volume up button (for TT), then plug the USB cable in (or shortly press the Reset pinhole button).

You can download the tools here: https://dl.radxa.com/rock_pro/tools/windows/ I used RKDevTool_Release_v2.96-20221121, Rockchip_DriverAssitant_v5.1.1. I didn't make any changes to the config.ini file, the RKDevTool started in English. If you get an error saying the tool cannot find the config.ini file, move the whole folder somewhere else, e.g. to the C:\ root (it's some path issue, either special characters or the path is too long or something like that). You know the touch screen is in the correct mode when the app says Found One LOADER Device; not Found One ADB Device or Found One MSC Device or No Devices Found. You can just simply press & hold the recovery button on the device (IW: left-hand pinhole, TT: volume up button) while plugging the USB cable in, it should start in the correct LOADER mode immediately. (This helped me with a 10" IW which either wouldn't react to the Reset button or would always end up in the ADB mode for some reaseon.) Or plug the USB cable in first, then press & hold the recovery button and then just shortly press the Reset (pinhole) button if it's easier. The device should show up in RKDevTool almost immediately as a LOADER Device, it shouldn't be necessary to keep holding the recovery button for long.

Any plans to move the driver to https://drivercentral.io/ or https://blackwiredesigns.com/ yet? I think it would boost the confidence in the solution and its visibility a lot. And it would take the burden of keeping the site alive and providing first level support off your hands (for a fee, of course).

Hi! Is this driver still available? The e-mail address reportedly does not work anymore.

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

Anyone has any up-to-date info about or experience with the Android TV Dune players? Would they work with either https://www.video-storm.com/proddetail.php?prod=IRUSB or better yet https://drivercentral.io/platforms/control4-drivers/audio-video/google-android-control4-driver-chowmain/?

Good! How about distributing your driver through https://drivercentral.io/ and/or http://blackwiredesigns.com/? More exposure, no need to deal with dealer registrations/verification...

PW has their own adapter / cable. But it's limited in length.

From the DoorBird D10x installation manual:

No way to change that. I talked to Alan about it when bond came out. The number of speeds can't be dynamic in c4 so he had to set it to 7 to account for everything They could create separate versions with 1-7 speeds (or whatever numbers make sense)…

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.

Hello, what's the current home of the Satel Integra driver? Is it still available? I cannot find it at homeation.com. mwiz.pl doesn't seem to be fully functional.

Additionally, you might want to execute some more commands later in the script, i.e., after the if-else block, regardles of which branch (if-else) was chosen. It's not possible with the 'Stop' command (unless you duplicate those commands before each Stop). The script just ends there.

Thanks, David. Perfect! We sell Shelly devices (mostly stand-alone, but sometimes a device or two can be added to Control4) so this is interesting for us too.

Hello! Does anyone have any experience integrating a large-ish number of LIFX devices to Control4, say 64? Any trouble with that? Has anyone tested and compared both Chowmain's driver based on the cloud API vs. berto's driver based on the LAN API?

Cool, didn't know that. Although the nice thing about multiplatform tools is that you can learn them once and then use them on any system. (Then again, learning to use native tools has its upsides too.)

By the way, I think that the satellite or cable proxies might be more suitable than the dvd proxy for your IPTV STB driver.

No need to resize icons by hand. Use imagemagick. Run these commands by hand, or create a bat file (if on Windows) or a shell script (if on a *ix OS such a Linux or macOS). (Assuming imagemagick's executables are in your PATH.) magick convert deviceicon.png -resize 70x70 70x70.png magick convert deviceicon.png -resize 90x90 90x90.png magick convert deviceicon.png -resize 300x300 300x300.png magick convert deviceicon.png -resize 512x512 512x512.png magick convert deviceicon.png -resize 1024x1024 1024x1024.png Example bat file (my first, so not a stellar example, but it gets the job done): @echo off SET filename=%1 FOR /F "tokens=2 delims=." %%A IN ("%filename%") DO (set extension=%%A) FOR %%F IN (70x70,90x90,300x300,512x512,1024x1024) DO (magick convert %filename% -resize %%F %%F.%extension%) Save, and run as imageresizer deviceicon.png