mindedc1

I think this is the web site for the company he was with when he wrote that driver: They may still be able to sell you a copy or they may know where to find him. You may have to use google translate if you don't speak (I'm presuming) Portuguese: https://www.t4control.com.br/loja/

Man, It's going to severely depend on the vintage of the Arecont if it would even be possible. They don't even support ONVIF on the older cameras... very proprietary. They seem to do RTSP but they don't do a great job of supporting third parties. I also see quite a few of the PTZ and muti-sensor cameras which probably are more fun to integrate...good luck.

It's also possible the projector's IP board went bad. I've seen it on a JVR RS520. You could ping the board but C4 IP driver was super flakey. No amount of firmware updating resolved it, had to send in for a board replacement.

I just looked and you are absolutely correct. My apologies to Roku for the slight. I haven't looked at a new one in a few months. From what I can tell they still don't support 23.976 and force everything to 24fps. If this bothers you or not it's personal. Nvidia is on a crusade (well, ok, some sort of side hobby actually) to enable global fresh rate switching and the only way to get any modicum of decent 1080P -> 4K scaling with their ai scaling for streaming content. I think the streaming providers have a lot of blame here with requiring the UI to be in 4K60 before they will present UHD content. I presume this is to limit support issues for all of the weird older TVs that have limitations and constraints around refresh rates, resolutions, and color depth. I have a lot of respect for Nvidia doing AI upscaling and creating a global refresh rate switching API so I'm voting with my dollars. I also have three older Roku premiums in use, one of the little cheapy $30 ones I bring on vacation so by no means think I'm saying it's a bad product.

Minidrivers are NOT working as they do not create an audio path through the driver. I think this is a bug and hopefully we will see a fix soon. The minidrivers also haven't seen an update in a little while, they may need new app strings added specifically for shield. I've about had it with the apps on a few of my smart TVs and I prefer shield over the Roku for video quality reasons. With Roku everything C4 works perfectly but it doensnt support all frame rates and last time I looked no dolby vision.

I can confirm it works (navigation and playback commands) with the older (2017 ?) shield. Controls are snappy with it and the 2019 shield pro. I'm not getting audio path on the universal minidrivers so there is probably an update coming that will fix that. I can also confirm that the other issue I'm seeing relative to the videostorm driver is that it doesn't expose the AV start/stop so no automating your lights to video playback... that's one of the coolest features of the shield with irusb in my book... It's also nice that you don't have to go find the hard remote if the shield reboots to permit the videostorm app access to USB.

I would open a cmd prompt and ping 4.2.2.1 from one of your computers. I would send them continuously. I would do the same to your araknis router. When your internet "drops out", check the pings. If they're still going it's not DNS. if it goes to your arakins but not to the 4.2.2.1 address it's probably something on the fabulous quality cable network. I would get comcast to check the counters on your modem and/or run a test to it.

Also, RE above variable speed blower thermostat integration. I got around this with a zoning board. I actually do have zones, but it handily does the staging of the air handler and exposes standard thermostat wiring to zones... I use Ecobee and it works great.

You can get some basic help here but you're going to quickly need dealer tools. I would engage your dealer, that's what they're there for after all...

Rucks isn't the only game for enterprise wifi gear. We use Ruckus and Fortinet for SOHO customers. Ironically I would tend to not use Ruckus for large installs, we use Aruba or Mist for those. Unleashed scales to something like 50ap max, Aruba instant scales to over 100. All of the controllerless solutions have scaling issues in large environments except Mist. We have customers with 10s of thousands of APs with hundreds per site so something like Ruckus is a no-go for them. Aruba Instant is probably the same range pricewise as Ruckus but no user friendly app. Aruba is also about to go subscription with AOS10 so not a good choice for home use. Mist is already subscription so also not a good choice for home use. If you look at sales, Cisco, Aruba, Comscope/Ruckus, and Hauwei have the perponderance of the market. Ubiquiti is the big fish of the little guys with 4%...Luxul, Araknis, Packedge etc.. together are a rouding error... RE 6E, it's more important and will have more real world benefits than 802.11AX/WiFi 6: 1. Additional channels will allow enterprise customers to run 40 or 80 mhz channels. This is an issue with hundreds of APs in a building, especially if you are near ground radar that kills some of the DFS spectrum. 2. No legacy support. Wifi is a shared medium and clients can be anything from an 802.11B/G client with 1 spatial stream to a new Mac Laptop with an AX radio with 3x3 mimo. All communications to multiple nodes (broadcasts and multicasts) are sent at the lowest allowed connection rate. This wastes huge ammounts of bandwith. The old 802.11 signalling is someting like 16 or 32 bits per waveform (can't remember), whereas with OFDM an AX radio can pack 1024 bits per waveform. Further, in pre-AX, the client waits for clear air and talks. This doesn't provide the best performance. In AX signalling the AP controls client transmit opportunities so it can get better performance or do fancy mu-mimo things depending on who can hear what. That all completely breaks if you have a legacy node on the AP. No legacy support means far superior performance. 3. Everybody gets to buy or sell new gear. 6e requires new hardware because not just the radio but the signal path and antennas have to be reconfigured to work at 6Ghz. Enterprise radios usually have sideband filters to prevent interaction with cellular signals so they would need those filters changed/removed to work in the first place at a minimum. We are expecting 6e units on price lists from leading manufacturers this fall with ship before EOY. I would assume the first round of chips will work OK but I wouldn't pay a premium for gen 1 hardware. I also wouldn't not buy if I needed gear. All things being equal I would wait for Gen 2 hardware with massive performance/stability improvements as we've seen year after year with N, AC, and AX.

I would go Ruckus Unleashed, never need to look at the UI, they just work. There is a phone app for the very rare occassions you want a question answered or you want to ugprade firmware. The ratio of Ruckus installed base to the hyper-niche products has to be rediculous and wifi is all about client compatibility (at least until every device is 802.11ax/Wifi6 or 6Ghz).

The Vera integration works quite nicely most of the time but if you have a large number of zwave devices the communications can get bogged.. I have 80-ish lighting loads on zwave and it hangs my EA-5 on boot, I have to power off the Vera when starting the EA-5. This didnt happen when I had a small number of zwave devices. I spent less than $30 on most of my zwave loads (most loads) and the few places I have dimmers I have fairly nice cooper aspire dimmers which do support instant feedback....it would cost thousands to re-do with C4 so I'm stuck in a spot with mine for the forseeable future.

The sexy setup is blue iris with the AI object recognition AITool. There is a thread somewhere on how to set that up, google will surely find it. I use Hikvision cameras but I'm cheap and not worried about chinese snooping given that my cams are on an isolated firewall segment. There are hikvision drivers as well as drivers for Blue Iris. I have tried some other brands, keep coming back to Hikvision for value. I have a Dahua currently in my setup and it works well. You will need a dedicated PC with an i5 without AI and depending on the amount of cameras and resolution an i7 for AI. I have 10 cameras and a recent i7 can handle AI on top of Blue Iris quite handily. The beauty of Blue Iris is it will work with almost any model of IP camera, get cheap ones here, expensive ones there, special feature for that one over there, no problem. I slowly expanded my system over time and wound up moving a bunch of cams around because you want to optimize the field of view/zoom for each location. I have C4 bypass BI for live viewing and pull streams direct from the camera.

So some clarification and information for you to cut through the clutter. I'm a networking professional and have architected many very large high scale networks (500K user+ type environments). I was CCIE level 20 years ago, tier 3 tac level at a Cisco competitor, have moved on to other products but manage a networking team now. My guys install around 20K access points each year and thousands of switches, lots of large firewalls etc. I also do a little C4 programming as freelance for a dealer on the side, some C4 driver development as well as have a decently large install myself with lots of odd things. I run pro networking gear myself at home in my environment (Ruckus and Juniper switching, have use Mist, Aerohive, and Aruba APs with my current C4 setup as well). All of the C4 restrictions around networking are because most dealers don't have an in-depth knowledge of networking. Let's discuss: C4 uses broadcast - not true. Do a wireshark and set the display filter for eth.dst == ff:ff:ff:ff:ff:ff, you'll see lots of ARPs and probably netbios garbage but nothing important for C4 beyond ARP. C4 does rely heavily on multicast (wireshark display filter ip.addr >= 224.0.0.0). Ubiquiti is supposedly on the "no" list because of some UBNT hardware not forwarding multicast, specifically the routers as I recall. It works fine other than that rare case, no reason to change to Cisco or anything else. Spanning Tree Protocol - Recommended against because it's a pain to configure properly and configured improperly you can have issues, I suppose they consider it better to allow a customer's network to get locked in a hard loop. It works fine, I've used MSTP, RPVST+ and some other flavors with C4 and it's fine if configured properly. Home grade switches may have poor implementations. Flow Control - Properly implemented flow control is fine, the issue is most network hardware doesn't expose getting pause frames from devices that are overloaded..again instead of identifying the problem it turns into some sort of mystery that's resolved when the overloaded device is replaced randomly. This could be an issue in switch to switch communications or server to server where lots of disk IO is happening. If you're running pro gear and routinely check for pause frames as part of your troubleshooting not an issue. QoS (Quality of Service) - I've also used switch level QoS with no issues, I would be cautitous about QoS or traffic shaping in home grade routers. Industry standard DiffServe on switches works fine. I would avoid punishing multicast or anything C4 is doing. I would also avoid voice prioritization for wireless unless you have someone who really knows what they're doing set it up. Lots of bugs in those features on most wireless products. Wireless isolation (QoS setting) - This will cause problems RE C4 discovery works off of multicast. Privacy Separator - presume this is same as client isolation, same deal PaGP (Port Aggregation Protocol) - Works fine as well as LACP/802.3AD dynamic and static. If you don't know how to configure these protocols you can of course create problems. There are special criteria in PIM environments with LAG/PAGP IGMP Snooping (or any other Multicast Filtration of any kind) - Presuming from the bitching I hear from dealer friends about this, I presume that either the C4 gear doesn't prune/join properly or they've had networking folks not set this feature up. I run IGMP enabled on my Juniper switches but your mileage may vary. They left off storm control, DHCP snooping, Dynamic ARP inspection, etc here but again, I use it and it works fine. So, the recipe for success, is keep all the C4 gear and all the clients that talk to it on the same VLAN, even over wireless. You should be able to have multiple VLANS working with PIM with a phone or touchpad on one side, however if any of the C4 devices don't handle IGMP properly you may still have issues. C4 doesn't really define which devices need which s, g publicly so any PIM troubleshooting would be a guessing game. You may also have RP overload in a home environment with a setup that large. We generally filter out SSDP, MDNS, Bonjour etc in corp environments as I've seen 50 misbehaving clients take down a 1 terabit line rate switch with enough control plane traffic thanks to MDNS. Though technically possible you would be in the minority with this type setup. The exception here would be things that do not need multicast discovery. For example I have all of my IP cameras on a firewall zone on an isolated switch (ethernet connection on the outside of my house, security problem!). The IPs are manually configured in C4 so no need for multicast, works great. If you put things that never need to talk to C4 on different VLANs, that's fine as well. I saw you ran some pings as a test. 12 pings isn't enough and if you're running 1G or 10G you're not loading enough of the wire to see an issue. I would run 1000 pings and I would also increase the packet size to 1472, after applying the header that's the largest payload you can squeak through a 1500 byte mtu ethernet connection. If you run 100% clean with no loss I would say it's unlikely network is your issue. You will see loss over wireless, I would test from wired. You could still have multicast being blocked but that would be more difficult to test. You can use netcat if you have a unix system or if you have two laptops you can generate a multicast stream with VLC and some video file. Google will explain that process better that I am willing to here. I would also suspect that your issue with controls not working is not a multicast issue. Multicast is used by C4 for discovery. Once the remote device is discovered (Say an EA1) the communications are unicast for which ping is a good test. Anyone that doesn't believe me is free to use the above wireshark filters to find out for themselves. I think it's unlikely you have a wired network issue. I would look into the EA that runs director. I've had severe C4 latency issues with an IP driver (Yes, a Control 4 issued driver BTW) eating a lot of CPU and lagging out director. Identifying that driver and fixing an issue with it has completely resolved the issue. I spent a week on the phone with support on that one. Engaging your dealer is the best way to identify if something like that is causing the issue because they're going to have access to deeper troubleshooting tools that you don't. You could also be having a spectrum issue with zigbee. It's sitting on the 2.4 band. Given that you have 11 APs, hopefully someone has told you or you know to turn off most or all of the 2.4ghz radios. There are only three non-overlapping channels in 2.4, given that there's better reach on 2.4 vs 5ghz, it would be difficult to not have channel overlap 3-4x in that setup. I would only use 5Ghz if possible and potentially only enable 2.4 on three APs at most. If you need more you should do a heatmap of your house and identify which APs have the most RF barrier between them and configure the overlapping channels there, using the attenuation of of your structure to your benefit, adjusting down power as needed. Just the SSID broadcast from two networks (user and guest) could eat something like 40% of the 2.4 ghz bandwidth if replicated on three APs overlapping each other...it would also trash zigbee pretty bad. If someone configured the ubnt gear for 40 or 80 mhz channels on 2.4 you will have similar issues as well. My recomendation would be to disable 2.4 altogether if possible and use strictly non-overlapping channels on 5ghz, I think with 40mhz channels you should be able to just make it. Speaking of wireless, I would also get someone who is a drop dead expert on the ubiquiti gear or an expert with Airmagnet to look into the wireless, especially if the touchscreens are wireless. 802.11r/k are squirlley in a lot of client and AP chipsets, you may have stability issued on the T3s with roaming given the number of APs you have r/k/v enabled. Band steering can also create issues etc... There are other issues with fast roaming on cheap gear as it generally doesn't generate l2 forwarding table updates on a client roam. Controller based enterprise gear does this, UBNT might, however I don't know. My understanding is that the UBNT controller doesn't really handle traffic so I would expect not. Other solutions like Mist, Aerohive, and Ruckus unleashed have this sorted in a decentralized forwarding plane setup so perhaps UBNT has this as well. I'm also not sure how well autopower/auto channel works on ubnt, generally only Mist, Aruba, and Cisco have this actually working. You should probably use an analyzer to tune down the power on your APs to make a more microcell environment. I would get an expert on UBNT wireless as its very complicated and it's much more about the skeletons in the closet on each platform. Actually, just looked before submitting and it seems the T3s are 2.4 ghz only. If you're running them on wifi, I would kill all but one of your APs and put a T3 right next to the active AP and see if that stabilizes the T3. If so you probably have channel overlap issues on 2.4ghz. Good luck, hopefully this helps.

There are two ways to send commands into Kodi. The first is to use an API to tell kodi to do something. This is an absolute command such as FF, RW, menu up/down etc. the meaning of the command never changes. The other way is to send a "keypress" into kodi. The behavior of the keypress is context dependent. I.E. in the menu left means menu left but while watching the video it means rewind. This also means your're doing things the way kodi wants the remote to work. It's possible for Alan to have written his driver to take into account the various conditions in his driver and say "While in menu left means left, however while watching video left means rewind" and pull the correct API at the right time however the amount of programming and testing to get it right is significant. There is a free (both meanings) kodi driver floating around that I have made a large number of improvements to. This uses the second method of control where it sends the commands in. I extended the driver to work better in more situations, maintain network connectivity better, and have access to the first API for triggering media scans, also signaling to C4 when video starts/stops, and a few other things. I have support for kodi devices that need an IR power on/off but would still be controlled over the network. The free driver is an older .c4i driver so it doesn't have nice icons etc... my rework is a .c4z and includes icons. Alans driver does a lot of things and he is a great part of the community so I don't want to say anything negative or take anything away from him or his work. There may be a way to make it work for you. If his driver doesn't support your specific scenario I wouldn't count that as a flaw, just a corner case that's not accounted for and the Neeo remote is very new. I don't have a copy of his driver so I can't help you out. I believe my driver/the free driver would not have the corner case issue you have above. I also don't have a Neeo remote and due to a significant number of custom drivers on my system am not planning on upgrading to 3.0 super soon. If you want a copy of my driver I would be happy to share here. Its posted elsewhere here and on the Kodi forum.

I'm US based so I am unfamiliar with the BBC restrictions. Roku is the easiest to integrate and excellent user experience, however the NVidia shield is the best standalone Andoid TV streamer. You will need an irUSB from videostorm to get it integrated well. It's more work to program than a Roku. It has mini drivers like the Roku and it can output 4K60P HDR and Atmos. The performance is excellent for streaming. Another option if you're in the mood to buy a TV is to get a Bravia model with Android TV and integrated apps... Mini drivers as well and excellent user experience. I personally have one of each of the above in varying rooms for varying reasons mostly based on when purchases were made. The family has no idea what device is in what room, they just know hit the netflix button to watch netflix etc.... I did have a compatibility issue with my JVC projector and the Roku which both companies are still blaming on the other. I've never had a problem with Roku on any flat panels so go figure...

I've cascaded a HDMI switch behind a onkyo receiver. Works like a champ. The HDMI switch is serial and the reciever is network controlled so it's pretty solid from a control perspective. I could see certain combinations could result in issues.

Onkyo integrates well via network as does Dennon/Marantz.

I got dizzy reading all the arguing about max throughput. I'm ignoring that for sake of OP. I would recommend using a site survey tool to check your wireless. There is a demo mode from NetSpot for OSX and a few wireless tools for windows that can do the same. What you need to do is go to the places you are having performance problems and look at the networks you can see and the channels they are on. If they are sitting on the same channels your network is on or if they overlap (google 5ghz wifi channel map) a portion of your channel, move your channel. Say you are configured for channel 36 with 40mhz channels and your neighbor is sitting on 40 with 20mhz channels you will get good throughput on the first spatial stream but not the second. If your neighbors gear is really crappo they could have sideband leaking down into your chan 36 too.. You will also want to make sure you have -65dbm signal or more. I would not "crank up the power" on the AP as they generally have more robust antenna systems than your mobile devices and adding power will just have them blast over an area that a client cant respond clearly in. You will get distant clients connected at lower rates and not wanting to roam resulting in a crappy experience. If you have 802.11AC wave 2 and a mu-mimo client, are using non-overlapping 80 mhz channels, and are in close physical proximity to the AP you can get super high speeds. If you are in a dense environment and have a lot of interference from neighbors its better to drop back to a non-overlapping 40 mhz channel than try and use an 80mhz. Generally most of the traffic is sitting in the first channel/spatial stream until you transfer a large file so the upper channels don't see much action. Someone above talked about multicast. Broadcast is more likely to be an issue in a residential environment as most residential products don't do a LOT of multicast. The issue with boradcast/multicast in wireless is that since it's addressed to multiple clients, it's sent at the slowest speed or sometimes the slowest configured speed. For example, you have a hotrod wifi6 radio with 160ghz channel bandwith and a multirate ethernet connection linked at 10G. In theory you can have a ~1g throughput client (we can argue this later, lets solve the problem now). You can also have an 802.11a client linked up at 4 mb/sec. The older client's bits are flipped at a small portion of the rate of the new client, wasting airtime/bandwidth. When you have a ton of BUM traffic it wastes airtime. I've seen at a hospital an 80% airtime consumption (YIKES!) with BUM traffic. Another example are the BSS broadcasts that announce the SSID. Those are sent at base rate and approximately 32 SSIDs on the same channel will use 100% of the airtime because it's transmitted at a very slow rate. You can mitigate by increasing the minimum connection speed which will reduce your cell size. I would also reduce your power to a moderate level to cover the area the AP is supposed to cover. You may need another AP and to reposition what you have, however the throughput and reliability could be higher. Also don't use 2.4 for anything if you can avoid. In summary: Use a tool to determine channel use by your neighbors, this changes over time so you may need to adust periodically Verify you have -65 coverage everywhere with the same tool Verify you have non-overlapping coverage on each channel of each AP with the same tool Reduce AP power to moderate levels if you've increased power settings Do not use 2.4 if possible

The install guide for the CBM has it, should have been in the box. You can also ask google. The serial side to the controller is serial and you can swap pins 2/3 (TX/RX) as that will swap the serial from "straight through" to "null modem". When you get that side working and a driver loaded the light pattern will change and the driver will talk to the module. I can't underscore the proper driver enough.

Ugh. These things suck to install. You will be wiring your own cable as the CBM side is a terminal block. The pins in question are 2,3,5 on a db9. If you think the cable is the issue you can swap 2/3, You can't fry either side with serial voltage so don;t be afraid to experiment. The other places to get sideways are choosing the correct driver and at the panel. The wrong driver will lock the control bus up on your panel requiring a hard reset of the panel and will never load the zone names. If that happens you have the wrong driver. You can also make a lot of mistakes in the programming of the panel, but you can figure that out if you get the driver right. Good luck

Onkyo shares the same pedigree as integra and the integration is really good. You have two way driver, great access to the input and output zones, you can tie the second zone to a different room and it appears to the user to function as a seperate device. I am not familiar with using the internal network sources (internal spotify for example) with zone 2 as I find that it's easier to do all that from C4 or an outboard device and split/matrix across zones. I know with Dennon/Marantz it gets weird when airplaying directly to the reciever and trying to use zone 2... it assumes an incoming airplay connection means make the main zone play airplay... The only caution is if you are using the second zone output it may not support a digital input until you get into fairly high in the product line. I think that as a rule Onkyo (and absolutely Integra, but we're getting spendy again) sound much better than their Sony equivalents.

Make sure that you are configured for fast roaming and stay on the same IP network while you roam between APs. It sounds like the tablet is potentially doing a full re-authentication and doing a new DHCP request which flushes all the active network connections to applications. If you have a properly configured system and decent gear you should be able to roam without dropping the C4 app no problem. You should make sure the ubiquiti isn't configured to NAT the clients and that you only have one DHCP server on the network.

I use a Zwave LED strip driver by Fibaro, a Vera controller, and the extraveg vera drivers. It shows up as 4 dimmers to C4 (RGBW) and works instantly. Vera is $80-100, LED driver was $60. I use superbright LEDs from Amazon ($20 for 15 feet with 300 LEDs) with an amazon 12V power supply ($30) and a signal amplifier ($10) because I am driving quite a few strips. YMMV on C4 integration costs.

It's an ugly world out there for 4K streaming. Outside of Apple TV (great product, limited in the ways you can integrate with C4 or anything else, I.E users are banging around in the menu designed for apple remote using the C4 remote - feels clunky), the Nvidia Shield is fantastic for Netflix, Amazon Prime, Movies Anywhere etc... If you are willing to throw $30 at it on top of the cost of the shield, the videostorm IRUSB gives you extremely responsive control of the shield and lets you directly open apps... for example, the family just hits "watch" and then selects "Netflix" or whatever. You can get the same integration from Roku with the native Roku driver but I've had problems with signal stability with the Roku. The rules from Netflix and Amazon are that you don't get UHD unless the hardware detects 4K60 4:4:4. Make sure if you are after online streamed 4K UHD your whole rig is capable of 18Ghz throughput: cables, TV, reciever, HDMI switches etc. I cant speak to Plex, but for Kodi getting proper 4K UHD output requires a streamer with hardware decoding, meaning that if you want to use a HTPC or a NUC, it's going to have to be modern and fairly pricy. There are hardware streamer devices out there that support 4K playback, but most of them run on Android which only recieved the ability to process HDR in Nougat. There is no actual color management, just the ability to pass the 10bit color for say HDR10 with P3 color space. What I have found is that at least on the shield the APIs are not properly implemented and if you're switching back and forth between standard 1080P content with rec.709 color space and UHD with P3 or BT.2020 color space is that it will get all off and wonky. The only device that seems to implement this properly is the Minix U9-H, which does handle it properly along with properly bitstreaming Atmos, DTS-MA etc. The catch is that the android OS shipped with the U9 has the same problem. The solution is to boot Librelec from a sd card. There is a kernel fork for librelec that enables all the hardware to support the 4K UHD output. It's painful to setup but it seems to be pretty solid. The one pain point with C4 and the Minix device is that it doesn't support wake on lan. I had to create an IR driver with just the single power on command which I fire programatically. I control and power off via the Kodi driver. This will all probably (hopefully) change over time as android gets better support for manipulating color space and the kodi developers perfect use on the platform. Right now there aren't enough people doing it to get developer attention.