Andrew luecke

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).

G'day Kaas, Just letting you know, we haven't come across this device (only online), however, my suspicions are that it might simply be an Android device which runs a Tuya Client (the Doodle Intelligence app they mention) and there might not be much we can integrate with at all. Sometimes products like these also work a lot better theoretically, than practically (and I've noticed that there don't seem to be any reviews or videos anywhere, so it might be vapourware). It's also clear-cut case of copyright infringement, so I suspect we'll never see it internationally (any distributor willing to touch this would do so expecting to have to fight a lawsuit).

G'day All, We have some major Announcements with Tuya. NEW RELEASE - 20211112 [STABLE] Firstly, we would like to announce the release of 20211112. This is a MAJOR feature release, that we STRONGLY recommend is setup for customers, that adds a few major new features: 1. Real Time feedback Additional setup is required, however, Control4 can now update feedback status in realtime (instead of 2-5min delay via polling) using the Status Notifications API The biggest benefit of this is that if the light is triggered via PIR, or Tuya button, it will turn on instantly in Control4 too, so Control4 will match the device status correctly. This is a major update (and we found that feedback is actually really fast, despite being cloud based). PIR is detected almost instantly. You could also use switch relays as triggers for control4 now, without needing to wait minutes for the trigger to occur 2. NEW Tuya Sensor Driver. This driver facilitates triggering Control4 actions from Tuya via RELAY, Button links or contact closure. It supports all boolean, Integer and enumeration variables (and similar to our other drivers, Tuya Variables are also exposed as Control4 variables and the driver can be mixed or matched with others). It also adds easy support for sending notifications. Some examples of use are: Turn on Control4 lights when a Tuya PIR is activated Trigger a doorbell sound via announcement when a button is pushed When the brightness of a light decreases below a certain level (as an example) Trigger an announcement in the kitchen when the water kettle has finished boiling (and turned off) 3. Blind Levels Our driver now supports setting percent levels for Tuya Blinds (as requested). Please note, there are caveats (as per the documentation. Some blind controller may not operate correctly). This was made possible only because of the new feedback code. New QuickSetup Video By popular request, we now have a video quick-setup guide to assist with installation. The video covers the full setup, including configuration of the message service for instant feedback and provides more information on the codes system.

Good news everybody. We're happy to announce stable release 20211108. This new release adds the following new features (as per popular request): Positional Blinds support (requires calibration of blinds in the module web interface). After enabling calibration, Set Control Type to Level in Properties. Smooth ramping of dimming for button links (which must be set to dimmable). Advanced Lighting Ramping support, with support for long ramping. PLEASE NOTE: attempting to ramp both White and colour channels simultaneously for long periods may cause problems with the color mode switching back and forth Major Bug fixes Please note, we have found that some people on old releases may find that even with auto-update enabled, that they may need to update their installations manually For a link to the latest driver download, please go to: http://www.chowmainsoft.com/shelly-control4 Detailed Changelog is below: 20211108 [STABLE] This new stable release primarily adds: Optional support for smooth dimmable ramping on button links Level/discrete support on Blinds. Bug fixes and and other improvements have also been included Refer to the Beta changes for full information. Specific changes for 20211108 are: Update Documentation (All) Minor Backend Improvements (All) 20211105 [BETA] Webviews keep incorrectly resetting to default in some cases (Thanks David Hancock) - (Module) Improved Debugging (All) 20211025 [BETA] FEATURE: Add Support For Blind Levels. To enable, set new Control Type property to Levels. Default is toggle (blinds, modules). Stability fixes for feedback disconnections (Module). 20211019 [BETA] Add Support For Button Link Smooth Ramping. Please note, Button Link behavior must be set to Dimmable (All Dimmable Light drivers) Switch default Button Ramp rate from 5% to 8% for smoother ramping (All Dimmable Light drivers) Add Short term and Long term Ramping support. All Dimmable modules supported, with the exception of the Shelly SHBLB-1 Bulb which does NOT support smooth ramping. Please note, attempting to ramp color and white channel on some devices simultaneously may cause problems.. (All Dimmable Light drivers) As there have been no reports of problems since introduction on 20210916, Dimmable Button Links now defaults to "Dimmable". Original behavior can be restored by switching to On/Off (All Dimmable Light drivers)

G'day guys, Just letting you know that we have a major new beta available for those interested in testing (which we're hoping to launch next week). We're particularly looking for those with larger installs or with a wide variety of smart-home wifi devices

G'day. Those who are in the beta program, will shortly be receiving a beta which enables full feedback for blinds (which is available by enabling Control Type: Level in the blind module), and a few stability fixes. We expect this version to be pushed to driver central later this week. If you wish to join the beta program, let me know To the best of knowledge, this functionality, combined with long ramping fulfills all known feature requests made (so if there are any other requests, feel free to let me know). Also, feel free to message me directly if there are any known issues you have come across (in particular, regarding external temperature). Andy