Jump to content

Andrew luecke

c4Forums Member
  • Content Count

    10
  • Joined

  • Last visited

About Andrew luecke

  • Rank
    Control4 End User

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Pre-release 5 is out, and now includes Auto-adding of drivers using the new C4 3.2.0 AddDevice API. Just want to thank everyone at C4.. An updated Preview is available below:
  2. Pre-release 2 is now available from: https://cbuslink.com/ (keep in mind, this is still a development build). It fixes 2 major bugs with Dimmer (Managed) control: 100% gets treated in certain circumstances as level: 100, not 255/FF (as per CBUS) iPhone/Android support is fixed for dimmers
  3. G'day guy's, (finally) introducing my new Cloud-based C-Bus Powertools Driver for Control4 designed for Clipsal CBUS Lighting Systems. Clipsal CBUS is a Lighting system developed by Clipsal/Schneider Electric which is common particularly in Australia. This is a dropin for the Extra Vegetables drivers (or long term standalone driver) with Cloud functionality for remote access to the lighting system, and fast provisioning. This is currently a time limited prerelease!! We're still looking at distributors for the driver. As this is a pre-release, we recommend only using it for testing on production systems (Sniffing is probably safe to use, but our powertools auto-provision drivers will likely break). Download and more Info: https://cbuslink.com/ Why use it? Cloud Gateway. Access Application logging and test components of the CBUS system remotely. No port forwarding required. SSL encrypted Rapidly commission Clipsal C-BUS Lighting on Control (5mins vs 2 hours), with sniffing, imports, auto-renaming, and auto-provisioning of groups/applications Import XML Tags/cgl files quickly into the database. So, you can have a sparky commission the system, and just give the c4 the programming to import, which can be imported in seconds. No need to keep the sparky onsite. If you don't have the CBUS file, you don't need CBUS Toolkit. Just walk around the house pressing light buttons and look at the application log for ID's. Also perfect for when you miss a circuit in an existing extra veg system and can't get back onsite due to isolation Drop in with Extra vegetables. You can still (mostly) use the sniffing capabilities, and merge both systems safely (you'll miss some functionality however) What doesn't work Currently, you must must use an Extra vegetable driver and legacy mode with it. That's not a bad thing (it's safe to do, and allows mixed systems for testing)... Allows easy migration too This trial will break eventually because I'm making some major changes to the API. The final will be a stable api You can rename drivers in the Web, but changes to the drivers directly won't be relayed to the web.. You can still change them, but the database won't update correctly Other minor things Dimmer and lighting relay/On off drivers seems to work here, the rest of them are lessor tested No blind driver yet.. Still on the lookout for a module.. You can still intermix the extra veg blind driver in legacy mode anyway (just no auto-provisioning of that driver Contact me Details are on: https://cbuslink.com/ Also, still on the lookout for extra modules (such as blind). If you work with extra vegetables and still have the source code, please feel free to get in touch too (as this would allow me to upgrade the original drivers to support auto-provisioning, or at least I could provide the commands I require to do so) Demo Video
  4. G'day all. Just wondering if there is a way to change properties of other drivers without using messages. Working on a replacement for the cbus driver and was investigating using mine as an extension to the existing driver. I couldn't see anything in the API docs but just wanted to confirm 100% in case I missed it
  5. Just a few updates (to the people who have messaged me). I'm currently in the process of rejigging a lot of this to bounce off a server, to take some load off the C4 Controller. As a plus, because of the redesign, in most cases (even satellite with 500ms lag), the web interface will probably be faster than the old webserver. Port forwarding won't be needed either (so, it should also work on double NAT'ed connections).
  6. Just a sneak preview of the new CBUS PowerTools Driver I'm developing (keep in mind, it's still in development, and certain parts of the architecture may change). It's designed for VERY fast commissioning of Clipsal CBUS Lighting Systems Features: VERY Fast commissioning of CBUS systems (5mins vs 2 hours for a standard CBUS System, with automatic group type detection). Managed drivers. YOU DON'T HAVE TO ENTER Group addresses, application addresses or even names of circuits. Less copy and paste = less mistakes Import from CBUS Toolkit (CGL / Tags XML) Built in Webserver to facilitate setup (this may change, and may be shifted to an online service, included with the driver, to be accessible online to installers, take load off the controllers, and allow better management ). I'm hoping to also support a few features missing from the standard drivers I'm hoping to complete the driver within the next month or so (however, it's dependent on access to hardware. I'm located in VIC Australia if anyone has any CBUS hardware they are hoping to sell cheap (even if it has faulty channels, that's ok for testing purposes) or can get me in touch with Clipsal for hardware. The plumbing is mostly done, and it's now simply a case of completing the comms between the gateway and Control4. If anyone has any feedback, it's also welcome.
  7. That's ok.. I worked around it in a different way.. I created a fast provisioning system thing, and fully managed the drivers instead... still needs some rejigging I have a preview on:
  8. Actually.. You might be right.. I'll try speaking to Control4.. There is C4:AddDevice() but it says Command Not Supported
  9. There must be a way to do it.. surely.. Maybe a mix between using dependencies, dynamic bindings? I'm trying to provide a replacement to an old driver with one which is less painful..
  10. G'day guys, Developing a driver in LUA, and was wondering if anyone knows of a way to add additional C4i or C4z files to a project programmatically (which I could then edit it's properties externally), similar to Sonos Network (which automatically adds extra players). There must be an API function to do it, but unable to find it Thanks, Andy
×
×
  • Create New...