Köhler Medientechnik

I am the dealer. So what i understand from the feedback here in the thread is, that the latest upgrade itself doesn´t seem to be the problem and it should be working. So i think i´ll go through a reboot/refresh cycle again with the client and if that doesn´t help, i´ll start from scratch and remove and re-pair the driver and the ATV.

Hi, i also tried the "refresh" command, didn´t help either. Here´s the output triggering it: -------------------------------------------------------------- ExecuteCommand -------------------------------------------------------------- ExecuteCommand(LUA_ACTION): ACTION: REFRESH ------------------------------------------------------------------ Refresh ----------------------------------------------------------------- ---------------------------------------------------------------- StopDaemon ---------------------------------------------------------------- --------> [6001/9200]: {"method":"stop"} --OCSC--> [6001/9200]: OFFLINE --OCSC--> [6101/9200]: OFFLINE ------------------------------------------------------------- DisconnectRemotes ------------------------------------------------------------ ---DEV--> C4:SendToDevice(43, "NOT_ACTIVE", {}) --------------------------------------------------------------- AppleConnect --------------------------------------------------------------- -------------------------------------------------------------- ReadyToConnect -------------------------------------------------------------- --------------------------------------------------------------- SetSetupCode --------------------------------------------------------------- ---------------------------------------------------------------- StopDaemon ---------------------------------------------------------------- --------> [6001/9200]: {"method":"stop"} --OCSC--> [6001/9200]: ONLINE --------> [6001/9200]: {"method":"status"} <-------- [6001/9200]: {"data":{"bridged":false,"provisioned":true},"method":"status"} { data = { provisioned = true, bridged = false }, method = "status" } Bridge not running... Provisioned: true persisted setup code: 164-45-896 ----------------------------------------------------------- CreateAppleDiscovery ----------------------------------------------------------- -------------------------------------------------------------- BeechDiscovery -------------------------------------------------------------- --------------------------------------------------------------- CreateRemote --------------------------------------------------------------- Creating Non-Voice Remote for Discovery. --------> [6001/9200]: {"args":{"devices":[{"caps":[],"id":1,"name":"Control4 Remote","state":{"remote_tcm:supported-configuration":{"buttons":["menu","playpause","tvhome","select","up","right","down","left","volup","voldown","audioinput","power","generic"],"ticks":1000},"remote_tcm:target-control-list":{}},"type":"remote"}],"force":true,"name":"","persist":"eyJkYyI6ImY0MmI4M2RhIiwiaWQiOiJBRDo3RjpGQzo2NTo3NjoxMyIsImt2Ijp7IjkwOjAwIjoiclhERytrcGYiLCI5MDoxMCI6IkF3QUFBQUlBQUFBQ0FBQUEiLCI5MDoyMCI6IkFnQUFBQT09IiwiOTA6MjEiOiJHQzhTWWZ1bVg0Z1A1MEdkenlzakRJcFdPTzlTcHpXWDV4OEdCK0JCRmk0PSIsImEwOjAwIjoiUWpJME4wVkdOREF0UXpnME1pMDBOVGRGTFVFMk5URXROREE1UVRaQ1FUVTVNRGt3SkZ5QXIxenlQVjRjNXFFTzRXVnQ2ZTZGN2hFM1VlOURWdFBFZHpYRlhQNU1BUT09In0sInJjIjp7IjEiOnsiMDA6MDAiOiJBQUE9IiwiMDA6MDEiOiJacnFHRHc9PSIsIjAxOjAwIjoiWnJxR0R4Z0FCUUJMYVc1dkFBPT0iLCIwMTowMSI6IkFRPT0iLCIwMTowMiI6IkFnPT0iLCIwMTowMyI6IkF3PT0iLCIwMTowNCI6IkJBPT0iLCIwMTowNSI6IkJRPT0iLCIwMTowNiI6IkJnPT0iLCIwMTowNyI6IkJ3PT0iLCIwMTowOCI6IkNBPT0iLCIwMTowOSI6IkNRPT0iLCIwMTowYSI6IkNnPT0iLCIwMTowYiI6IkN3PT0iLCIwMTowYyI6IkRBPT0iLCIwMTowZCI6IkRRPT0ifX0sInNjIjoiMTY0LTQ1LTg5NiJ9","setupcode":"164-45-896"},"method":"bridge"} --OCSC--> [6101/9200]: ONLINE --------> [6101/9200]: {"method":"remote","args":{"id":1}} <-------- [6001/9200]: {"data":{"paired":true,"setupcode":"164-45-896","setupuri":"X-HM://0023QQ1U0Y1YK"},"method":"bridge"} { data = { setupcode = "164-45-896", setupuri = "X-HM://0023QQ1U0Y1YK", paired = true }, method = "bridge" } - Bridge Started. <-------- [6101/9200]: {"data":{"active":0,"available":[{"identifier":260487782,"name":"Kino"}],"bridged":true},"method":"remote"} -------------------------------------------------------------- ParseRemoteMsg -------------------------------------------------------------- { data = { bridged = true, available = { { name = "Kino", identifier = 260487782 } }, active = 0 }, method = "remote" } ---DEV--> C4:SendToDevice(43, "NOT_ACTIVE", {}) Available[260487782]: Kino The Apple TV driver just says "Not Activated"...

You mean in the ATV driver? Did that, no change.

Hi, one of my clients did an update of his ATV 4K to tvOS16 and that apparently killed the connection to the control system (EA-1). Driver is the C4 Bridge driver (v45), and the ATV driver (v43) says "not activated". Any idea to get it back working?

OK, thanks for the confirmation. Then i´ll have a look with Wireshark.

What about the free "Extra Vegetables" Wake On LAN driver? According to the name, one could expect it to do WoL but it doesn´t seem to work. Lua output says "magic packet send", but nothing happens.

That´s a bearing damage of the switch fan as you correctly assumed. Should be changed.

And after signing out of your profile?

Any chance to check back from a different location (LAN) or via smartphone (no wifi)?

Looks fine for me.

Hm, i think i got it. Just using the "Single Lamp Brightness - FREE" instead of the "Single Lamp Full Color - FREE" driver seems to do the trick. Since i do not need any control of the colors from within C4, i´m fine with just being able to adjust brightness which is enough to do a fade-in and fade-out.

Mh, OK. But i don´t need the color codes in C4 anyway - i just want to fade into what they are set to by the client with the app.

Hi, i´ve got a client who wants to integrate a couple of Hue lights (some white spots and a LED RGB stripe) into his C4 environment. In general it works (Hue bridge driver installed and configured and spots and stripes successfully added to project). The only issue i have is the following related to the RGB stripe: The client is setting the colors for the RGB stripe with the Hue app on his smartphone. The plan with C4 is, to just fade into this preselected color and then fade down to black based on programming and/or button press. To achieve that, i´ve set "Turn on Values" to "Last used Values". However, when turning on, the color´s do not match to what was set in the Hue app (warm white instead of the red the client set in the app). Any ideas where to look? Cheers, Thorsten

Yes, i´ve seen them. Since they are DIN mount modules and therefore often to found in metal enclosures, i´d have some doubts on non-wired communication here. What i´d appreciate if there would be a possiblity to daisy-chain modules using the ethernet-ports because otherwise, you´d need quite a lot of ethernet ports and cabling to connect them wired.

I was actually the "everything besides wired is prone to failure"-type of guy and if wiring is not possible, use a proprietary system like zwave or zigbee. However, i did a test install of some Shelly devices at my friends house and no issue was reported at all since then (a couple of months ago). So i can confirm they are absolutely reliable and will start to use them in real client installs. A stable wifi is an absolute requirement, but nowadays that´s the case anyway.

True - that´s why i pointed out that there´s an additional twist with handling software licenses as compared to just a hardware purchase. I think what´s seen as "easy" and what not, depends on the customer´s point of view. The customers i have would hate it if they had to deal with the purchase and license stuff related to 3rd party drivers themselves. The more hands-on type of customer wouldn´t have a problem with that and potentially even prefer it. I´ve got the impression the real problem here is that some of the users here just don´t like the dealer model anyway, so of course they hate the "blackwire approach" anyway.

I don´t see the big difference to other areas. If you want to buy a Yamaha AVR, you can´t directly buy from Yamaha as an end-user. There is Yamaha as the manufacturer, a distributor who sells stuff from the manufacturer to the dealer, the dealer sells to the end-user. So the general concept is not new. What´s a bit different with software is, that you don´t actually have a product in your hand, but you buy a license. This needs some license management and there should indeed be a mechanism in place to "hand over" that license to the "end-customer" as part of the solution he gets from the dealer. So IMHO the "end-customer" should at least get some prove of purchase for 3rd party drivers so he can ownership in case the dealer dispappears.

OK, thanks. As i said, in terms of hardware and firmware, both the Binary and the AVPro unit seem to be pretty similar, so my guess is under the hood it´s more or less the same anyway. But i´ll have a closer look at AVPro anyway.

After all, there´s some procurement and license management to be done by the dealer. The dealer is the customer in the portal, purchases the license and then assigns to the endusers (his clients) project. The dealer is doing this for multiple endusers. That´s how the mechanism works - the dealer´s an essential part of the process. And this is nothing new - it works this way in many other businesses as well. (perhaps besides the license piece)

hey guys - peace...

Ah, OK - got it. I´ve had pretty good results with them in the past (EDIT: at least for such simple tasks like splitting w/o downscaling). What´s the issue with them? I can get both Binary and AVPro from my distributor so i could easily switch.

My comment was actually aimed at my suggestion of the Binary splitter and the AVPro Edge splitter suggested by msgreenf.

Looks like both are more or less the same kit.

I´ve got good experince with the Binary B-260-444-HDR-SP12SA Splitter for these kind of jobs.

Had the same issue today with an installation - Director reboot didn´t fix it, but power cycling the controller did.