Andrew luecke

Not sure what you mean? Although, I've never used the Pakedge NVR's

Just a heads up.. If you're not using the inbuilt ports on the NVR (especially if you aren't using events) my recommendation would be to ensure you're using a proper VLAN for cameras (so you need to also ensure you have a smart switch). The ports on most NVR's are isolated from the main network. But if they're not being used (if you're using the normal switch), someone could disconnect a camera and get internal network access, and potentially compromise the home security. Unrelated, but same thing about open networks. Never use them (even when hidden). I'd also recommend against using Wifi Cameras (particularly if they don't have protected management frame support) On more consideration is that PC's tend to consume a lot more power than NVR's (so long term, the costs could add up). Most people imho are still best off using standard NVR's

Firstly, this is personal opinion. I agree it is likely NOT Control4's fault. Control4 is very likely trying to get Apple Music support, but a lot of the negotiating would possibly be about policies / politics (from Apple) than anything else. Control4 definitely has the know-how to implement Apple music. The fact that nobody is supporting Apple Music suggests the issues are with Apple.. When people develop for Apple, they have to give up a lot (which is why Apple is getting sued in so many countries now). Some evidence of the hostility, is stuff like: forcing developers to use their sign in system (clearly for the purpose of self-benefit): https://developer.apple.com/forums/thread/124006 . Blatantly kicking out competing apps Delaying competitors products (like the Pebble, which was still awaiting approval weeks later). I'm guessing approval time for apps is still long too.. https://www.ilounge.com/index.php/news/comments/apple-developers-fight-over-tightening-iphone-nda . They've also always had NDA's in place, which stifle developers from talking about policies https://en.wikipedia.org/wiki/Epic_Games_v._Apple Whilst traditionally they used to support open standards, slowly, they drifted further from that too recently with depreciating OpenGL for their own API (Metal), and not supporting Vulkan. In fact to give you an idea of how ridiculous things seemingly are sometimes when dealing with Apple, shortly before Boot camp was released 20 years ago, a national (?) sales manager at Apple Australia basically called me an idiot (with customers around) for demonstrating that the new Intel Macs were a great transition technology by demonstrating windows on it ("why would people want to run windows?" was part of his response). A week later, boot camp was out, and he was proudly in our showroom repeating the exact same arguments I had made a week earlier and pretended the initial conversation never took place. Whereas, companies like Control4 foster 3rd party development and directly support 3rd party development (the control4 team is great to deal with all around), and ideas are readily considered If Control4 introduced Apple Music, don't be surprised if the demands made by Apple were similar to making it the prominent music service, automatically installing the driver, plastering it everywhere in control4, requiring Apple ID login support etc. It also wouldn't surprise me if Control4 was required to report additional information (which could be utilised anti-competitively). I'd assume they would also require that they could change their policies at any time, or their API with short warning, etc. It is also entirely possible they would dictate the required hardware too and would require Control4 to pay them additional money If Control4 added Apple Music, they'd likely need to give up a LOT (if Apple permitted it at all), and the terms of any contract would be under NDA anyway (Control4 might be working on it, but unable to talk about it). Unless the terms are similar to other providers, I personally think it would be a really bad thing for Control4 to add support long-term. There are so many competing music services around customers can use.

I've only heard about it.. But wouldn't those be only 30W? Or are they POE++?

Just wondering what you do instead?

A modern alternative to analog knobs would be configurable keypads linked to the volume. And multiple amps

G'day guys, just letting you know that if you are having trouble with Blind levels, send me a message (we have a patch available, which will be rolled out into the upcoming release after Christmas). The bug causes the level to go to 100% or 0% in some cases.

I obviously don't have access to the android subsystem here, but, if you can't find anything in Google, I'd start by taking a look at the HyperV settings (Android subsystem uses HyperV to some capacity, so maybe start by looking into using a network bridge on that, instead of routed mode)

Yeah.. I had all the dependencies enabled.. Was in development mode, etc. the correct file simply didn't show in the list.. But either way, I think it's better I wait until it's official. I'll be extremely disappointed if it doesn't go international on the first release (at least for countries without export restrictions)

Unfortunately, it isn't that easy, and there is no straightforward tutorial. Control4 will still require a custom driver to translate between those protocols and control4. Websockets and such is just a way to communicate (like using paper, or speaking). But you need a driver to translate the language/words. There's no step by step to writing the driver. It could be worthwhile recommending the manufacturer contacts chowmain software for a quote to write that driver. Also, If they want the control4 API, this info is fairly accessible online, however, unless they have an experienced control4 developer on staff, it will likely be cheaper (and they'll have far better results) to get it professionally developed (before I started working for chowmain, I wrote my own lighting driver. And so I can tell you that it takes months. We're considering releasing our own comparable driver now and we're not going to even use that code as even a year of experience produces far better code).

Thanks. But tried this shortly after launch and procedure didn't work properly. Also, figured it would simply be best to use blue stacks until proper integration is available (to eliminate any other unwanted flow on effects in the future). Microsoft should simply release it worldwide though.

I suspect it's because they use the Amazon store, so maybe it's a licencing agreement /politics thing more than anything. Not sure when we're getting it

Just a heads up.. If you're international like me, Android Subsystem isn't available yet (and yes, +1 for bluestacks)

Here in Australia at least, the USG's shipped with crappy 1A 12V power supplies. It may be similar to US, but after swapping them with bigger ones, they were solid. The original firmware on them was horrible though. The EdgeRouter Lite 3's though was another product (few years ago) with bad hardware.. The USB memory on them failed quickly

Not to stretch the topic, I have a UDM at home only, but have they fixed policy based routing of WAN?

Unless things have changed though, failover couldn't prioritise a specific connection to failback to, and there was no proper policy based WAN routing which is available on other enterprise routers (but, they had seemingly plenty of time to continuously redesign the GUI). That being said, CloudKey V1 was a product that should have been recalled (that I forgot about), and the USG was released prematurely too. The UAP-ACv1 was also a rush job. I haven't been an installer for the past year though (so things may have improved). One would argue though that the priority for a network company should be to release Wifi6 AP's as a priority, instead of access control Things have gotten better, and the current hardware is good.. But their prioritises are a bit weird at times

It varies.. They have had buggy hardware before (which was recalled), but so does everyone. The biggest risk with ubiquiti is firmware. They often release products with unfinished firmware, and sometimes, their quality of software dips (like when they released firmware that fried the UAP-Pro radios). Or the UAP-SHD which is advertised as WIPS, but doesn't actually seem to be.. My biggest concern at the moment is that, once again, they are diversifying their product range too much and focusing less on networking, and working on things like access control. They don't even have proper Dual WAN yet on their gateways when I tried last year (which is weird for a networking company). They also could be doing things like create a public API so we can integrate safely (I started writing a Unifi driver last year actually, but I'm hesitant about finishing it personally, because the API could change between releases) Good products. They have their own risks, but I wouldn't say failing hardware however is one of them personally.. In my previous job, we sold heaps of it, and the majority of issues was user error (like plugging a network cable into the console port of switches), or firmware. We didn't have to do many returns

I'd be hesitant about this one too (and I'm a huge ubiquiti fan).. If the specs are right, 2GB of ram probably means it's running android go I'm guessing, so, not futureproof at all... I wouldn't expect normal apps to run on it well. Also, Ubiquiti is a bit hostile towards the 3rd party integration, so I wouldn't get this for anything related to C4.

G'day, You may have been the person who emailed me (I didn't get a chance to respond).. Firstly, apologies for the long delay (I've been busy organising a camping trip for my hiking group). So, a few things have changed since I developed the driver... This driver was actually developed as a project shortly before I started working for Chowmain, and the powertools driver is no longer in development. At the time, I didn't really have the hardware to do it (as it was a personal project, and I actually spent money for the hardware) I've sent you an email in regards to the driver. Andy

Shelly's new DIN mount Pro 4/2/1PM modules are actually ethernet, bluetooth and wifi (but I've only used them on wifi). They're Gen 2 devices too (so use the newer protocol) and supported from day 1 of our release (or earlier actually)

G'day, Feel free to send me a message.. Also, ensure you're using shelly_module for old devices, shelly_module_ng for new modules.

Just a heads up.. If you do end up using Shelly and our driver, shoot me a message, and I'll add you to the beta list (as a new beta which fixes 3 bugs is expected to drop within the next few days )

G'day, I actually wrote the Chowmain Shelly Driver.. In the past, I had a Vera plus installed in my place, with a lot of the Zwave Plus gear. Zwave So, Zwave is obviously mesh based. Great for your typical smaller home, but as a custom installer, chances are, you have an awesome wifi network anyway (or should). You can guarantee the quality of the connection on Wifi a bit better. Zwave is 900mhz so should have better penetration, but there are also less channels available (so, more affected by intererence). And similar to Zigbee, if you have less Zwave devices, you may have a coverage gap, and areas where you need to extend the signal somehow. A good Zwave job can be as good as a wifi job though (if you're using a good gateway). Zwave does have a bigger range of products, and a wider variety of manufacturers. Zwave is more power efficient, so some devices like remotes may work for longer before they need new batteries (if you need them, few C4 users do). Shelly has some really cool products like the Uni though for upgrading dumb devices to smart devices. Shelly Protocols: There are two types of Shelly modules now, Shelly Gen 1, Shelly Gen 2 (generally known as Shelly NG). Shelly NG will (likely) be all modules released from now, and Shelly PM Pro (4,2,1), Shelly 1 Plus, Shelly 1Plus PM, and since it uses Websockets and a cleaner protocol (and newer chips), its preferred. With Shelly, we basically poll it (and I have some secret sauce that was added into late releases, so it's now extremely fast). In fact, I combined a Shelly Light with Tuya PIR sensor (which had its own built in light), and both the Tuya Light and Shelly triggered at the same time.. Both are great protocols, but the new ShellyNG protocol is a lot more succinct. With Shelly, its cheap, and we have a 90 day trial (or showroom licence) for all of our drivers at chowmain (and you can contact me anytime if you have an issue). All feature requests have been resolved with our driver at this time, with the exception of 1 which can't be implemented well (dimmer calibration, which is only ever needed once, and is easily accessible via web interface). We have a lot of users with our driver (everything from effects to Control4 BUTTON_LINK connections are supported.. We even built in an easy announcement option). We only have 3 outstanding issues (2 unconfirmed, and those are only unconfirmed as the installers took a while to get back to us, and I was awaiting some additional hardware). I'm hoping to have all resolved within the next week (so we're back down to 0 once again) If you do have any questions, feel free to contact me. But overall, the protocol is extremely fast (and we actually work directly with the Allterco / Shelly team, who are amazing to work with). Shelly is a great Wifi based product, and Shelly NG makes it even better. So, I definitely recommend them.

G'day all. Jay Basen (who many of you may recognise for his own Home Automation endeavours) from Residential Tech Today is seeking information in an upcoming article about how Control4 home installers utilise Shelly products. It is an excellent opportunity to help showcase some of your work to consumers and other installers (in particular, some of your more unique applications or installations in exotic locations). We've already heard from a variety of installers who use our drivers, and this is a great way for the world to hear about your installations too. You can drop me a message, and I'll provide his contact details so you are able to get in touch. Andy

Honestly, a lot of it comes down to price, consistency, troubleshooting, security, performance imho. Ubiquiti is cheaper than Ruckus, Ruckus has lower risk for firmware, Ubiquiti controller is fairly awesome (and supports their routers too), Ruckus security is better (they support proper WIPS, whereas even the UAP-SHD has imho fake WIPS, and Ruckus probably takes vulnerabilities more seriously, and I think they probably beat Ubiquiti to WPA3 too), and the maximum throughput of Ruckus is obviously higher at this time (in a high density environment, at this time it might perform better too handling the noise. In most home environments, noise is probably less of an issue). In regards to roaming, both support 802.11k so I'd actually be fairly surprised if Roaming performance was any different for modern devices (as 802.11k allows devices to see how strong the signal being received by the AP is, and vice versa, they can already see). Apple only starts roaming at -70db. Roaming on both brands is fine.. Ubiquiti is good if you know what you're doing with it, but if you're not good at networking, Ruckus might be better. Don't touch Aruba at all unless you know what you're doing. Snap One owns Access Networks though so if you want Ruckus, you could buy from Access Networks directly. On a low density home network, both have their own strengths. If price isn't an issue though, Ruckus these days.. The MAIN risk to manage is that you need to ensure you put sufficient AP's in. I've come across many jobs where installers installed enterprise products like Aruba and Ruckus, but skimped on them (because the price was more expensive), and so because there were less AP's, coverage in some areas became flaky. If you're going to install 15 Ubiquiti AP's, make sure you assume the same number of Ruckus might be needed (I've been to so many houses where top of the line AP's were used.. But there weren't enough of them).