Andrew luecke

Really old thread, but since its been reopened, we now have an Auslock and TTLock Driver https://chowmain.software/drivers/control4-auslock https://chowmain.software/drivers/control4-ttlock-driver

Wiz I think have something

You mean Composer HE right?

Honestly, I agree there still aren't any real-world applications for home users released yet for Wifi 7. But, I wouldn't be surprised if we start to see technologies like better wireless MOIP baluns a few months after the standard is finalised (and can think of a few that used their own rf standard). Wifi 7 has a worst case latency of only 10ms (best case 1ms, which is less than 1 frame), and 30gb performance. But, that will only mainly benefit specialized applications, or hardware designed for it (maybe also gaming if you're relying on wifi). I'm still using Wifi 5 too (which is enough for me at the moment), but will upgrade to 7 when proper AP's get released

It's a bit early for proper brands like Ruckus to have Wifi7 still. The big advantage of Wifi 7 will realistically be guaranteed low latency (which may also open up new classes of devices), or possibly full-quality streaming of high res footage over wifi without quality loss (but for that kind of bandwidth, you'll need Fibre+SFP or 10gbps Link Aggregation). So, many installs will likely only benefit from the latency improvements for now (but really depends on the usecase. It won't help if your usecase is netflix) If you're building and want WiFi 7, make sure you install conduit to your AP at a minimum, but you probably want fiber and ethernet running to your AP's to be able to use them at full capacity

It's probably a dynamic event. It will show up in programming though most likely

What version iOS app are you using?

Also, if there isn't a command that does what you need, the variables available on this driver are extensive (I basically tried to expose all of them, and it's a huge list

From our understanding, any device that supports the big ass fan mobile app via wifi will also work with our driver.

Do a refresh Navigators, and it will possibly fix it.. And ensure your locale is US. Otherwise, speak with your dealer (it could be something easy)

I don't think we've had any calls for our (Chowmain) thermostat drivers and this issue so far. So, statistically, less likely to be a app bug or OS bug. More likely driver or system configuration related

Removed

If you're looking to the Shelly chowmain driver. Happy to answer any questions By the way, I recommend the plus modules (as they're gen 2)

Control4 has a normal 2n intercom driver in their database which I have used onsite twice with standard versa (2n branded) units. But to utilise all capabilities on them, you need the additional 2n licences such as the enhanced automation licence (but that's the same with every automation system). The control4 unit has those licences included already. Also, c4 does allow 3rd parties to develop intercom drivers too (ie, our hikvision or dahua intercom drivers as an example)

SR260 has nothing to do with OvrC (and every dealer should know this). And the SR260's actually use Zigbee.. Are you sure its not a NEEO? Even then, Control4 uses auto-discovery. The only thing I can think of is a controller is linked using static IP (which is never done in general preventing that Zigbee ZAP from working), but even that should be fixable without OvrC, as they can simply change the address back using the standard tools (unless your whole network range has changed) Maybe I'm understanding wrong or he understood wrong? Are you sure this is a trained dealer?

You mean 1 semester right? Itunes was the primary example they used to use, and it was specifically targeted because the interface Apple utilised was completely inconsistent with the rest of the OS. https://www.flagsoft.com/cmswp/de/product-testing/top-10-user-interface-design-flaws-within-os-x/ sums up a few of them (the Traffic light buttons themselves and the behavior of the buttons are also a super common example, as they perform inconsistently).. Lots of design issues with finder, etc. Also, Apple often doesn't expose some functionality well. Windows is by no means perfect either, or android (they have their own issues, and guessing things might have changed in the past 10-15 years, as the inconsistency in Windows is a disaster now, but they're fixing that again). For icon design, sure, MacOS does a good job (and I'll admit that), so my comment might not be relevant. On the other hand though, the norm does seem to be to have a transition period, and this is happening even with bigger vendors now (and I'd imagine there is a lot involved for changing the entire interface too). I studied comp sci 15-20 years ago though (so things may have changed Also, keep in mind, one of my development computers at the moment is a MAC studio M2..

So.. The funny thing is that UI design classes in computer science, they regularly often use MacOS as an example of bad interface design. They do a good job with icons though, and in general otherwise (stuff like Spotlight and Timemachine they're still doing an amazing job against Microsoft, 15 years after it was released) Also, it is worth noting Apple regularly disregards their own Interface guidelines (but, have gotten better.. iTunes was the main example demonstrating this, and their top buttons close/minimise/maximise buttons).

The BAF mobile app firmware is not compatible with v1 /haiku app firmware and vice versa. That being said, the v2/BAF firmware and driver (free upgrade for v1 users) is significantly better. And we've only maybe had 1 or 2 support enquiries. One is an issue with Alexa (which turned out isn't a bug with our driver, and may be resolved by now), the second is something we're investigating (led button colour issue for configurable keypads), which doesn't affect the operation of the driver

You could limit them to 2.4ghz on their own ssid if this is a concern. But in general, not really. Plus series is more efficient however. We do ping them when the unit requests, whereas on the non plus we do a full poll every few seconds by default (but we recommend changing to 30s, but this might be slightly less efficient) Also, keep in mind if you only want on/off control, Shelly does a 2x relay module such as the Shelly plus 2pm which can also reduce the modules required. If you're using multiple APs, obviously, these modules will be split between the APs too

Just to clarify, I was referring to v2. V1 required polling. V2 is a total rewrite and utilizes a different protocol which provides feedback in realtime (and a huge amount of capabilities exposed via read/write variables).

In regards to big ass fans, I think we've only ever had 1 or 2 support tickets for it. It's an incredibly solid product and driver

Yep.. So, you basically wire the light to the switch, and the button to the switch via another terminal. Then wire power to the puck. You can use the switch as required (with or without a light), and control via Control4 If you have centralised wiring (which is unlikely, if its a retrofit), use the Pro PM DIN modules instead of Plus PM modules.

Get Shelly.. You can use ANY conventional switch then. You simply throw the puck behind the switch then. You can also use Control4 Zigbee pucks as an alternative. They make dimmers and Switches (I recommend Plus series) https://www.shelly.com/en/products/switching-and-triggering#unfiltered Combine with our shelly driver . We have thousands of installations using this driver

Why Z-Wave explicitly? You can use stuff like Shelly (pucks in wall, or the Shelly Dimmer US), TPLink, or other products.

24gbps Wifi 7 (Draft) routers already exist. The BE900 as an example has a SFP port built in. It's reasonable to expect high-end wifi AP's will also take this approach (but likely offer Link Aggregation too via copper, if you want to run 4x copper cables to the high end Wifi 7 AP's when released). Apparently 200x wifi7 draft products already exist.. Fibre is cheap these days, is electrically isolated and doesn't have interference problems. You also don't need to worry about length limitations (as much) either A 2C OM4 30m preterminated fibre lead is likely cheaper than $40USD (so not expensive at all, and extra cores are more cost effective). SFP modules are also cheap. I've pulled cables through using a pull cord, and sometimes, it can take a lot of screwing around (especially if there are already cables in the conduit, or if you're running multiple cables). You also still can use pull cord. Due to the low latency of WiFi 7 we may see more AV applications It's up to each installer to determine if they want to install fiber or not. But the price difference these days isn't excessive for preterminated. At the bare minimum, it should be going to WIFI points already (the roadmap there is already mostly obvious).