Jump to content


c4Forums Member
  • Content Count

  • Joined

  • Last visited

About rek

  • Rank
    Control4 End User

Profile Information

  • Gender
  • Location

Recent Profile Visitors

2,010 profile views
  1. In that tiny circle, I never doubted for a second it was Keith Richards and some other dude, seriously. Just assumed you were a Stones fan. Color me properly educated.
  2. I assume this is what we're talking about (from HE)?
  3. Have your dealer bind most/all buttons to advanced lighting scenes (build the scenes yourself first to save $). Then you can do everything yourself, and more importantly change your mind, without a dealer call. If you want a button to do your own thing / LED behavior, you can still do it and it'll leave the scene binding there unused in case you need it later. If you rearrange your button caps on a configurable keypad, you'll still have any bound scenes there for current or future use, even if there's no physical button for them at the time. I don't have HE in front of me now so I may not have this exactly right... but there are some caveats (at least I've been bitten by something in the past). IIRC, you can switch the LED behavior to follow if you want to use the scene binding or to push/release or programmable if you want to do your own thing and you won't lose your binding. But if you mess with the other dropdown (can't remember what it's called), you lose your binding, even if you switch back, then you have to call a dealer. [Note: I'm not sure if there's any downside to this - having all those unused bindings / empty scenes.] Do NOT try to simulate proper light control button behavior (i.e. LED tracking and brighten/dim ramping) in script - big crap. Do the binding thing above and it'll be there when you need it. Any tips related to deleting things in order so as not to leave orphaned code around (not sure about this one)?
  4. Just kind of rambling here. Things I've run across or wish I'd known earlier (although I admit I didn't read all the docs first). May or may not fit in your vision, or might trigger some ideas: Best practices. Right time and place to use Macros. Naming conventions to make your life easier. Logging. Organization. Things to have your dealer do (like clean up rooms/names and locations of drivers like you did for me) - make it easier for owner to continue with HE. Scripting/debugging tips. SNMP use. How to find out if you "got here" in code (flash LED or log). Highly recommended additional drivers for the do-it-yourselfer (i.e. "how to own your system"): Renamer, Variable Manipulator, Event Logging. More advanced: Advanced Announcements, IFTTT. Advanced Lighting Scenes. In particular, proper use of tracking. Light device tweaking. Getting the most from your bulb - properly setting Cold Start and Minimum. Getting the most from your buttons. When to use press/release vs. tap. Best practices for combining that with a double or triple tap. Using timers for a long-press (really easy and handy). Some of the tweaks @South Africa C4 user talks about where you combine press and tap with some careful ramp rates. Some "gotchas". Forgetting to refresh nav. Not realizing there's more stuff on the screen (usually scrolled off the edge at the bottom of actions). Certain documentation you should keep for yourself (so you don't forget important things about your variables, macros, ... and get lost in your own project since you can't really add comments to script). Ask your dealer for a dump of your code (and bindings).
  5. I did enough playing to confirm the date and time functions should do what I wanted. But I haven't got around to incorporating them into my project, yet.
  6. Yeh, without anyone else having this issue, definitely seems environmental. I'll just sit on it - don't currently need that functionality. Thx.
  7. Correct. Clicking ... brings up a dialog with just the top-level node and nothing under it (like the pic I posted 7/8).
  8. Same "empty tree" problem for me with 1.0.10.
  9. 1.0.9 fixed Refresh Navs for me too! FYI, Rename action still has an empty TargetDevice tree for me.
  10. Broken record here... +1 for @Matt Lowe. Advice, oft repeated, for OP. I spent 2+ years with local dealer only - good relationship and good work - called them when had enough work to justify their visit. Finally decided to try remote since everyone else was doing it. Holy crap, I could kick myself for those 2 years. Go local when you need it - you won't have to very often at all. Remote otherwise - you will NOT be disappointed. The comfort and relaxing feel of that level of control is awesome and plenty cheap and convenient. IMO it's basically C4 DIY - best of both worlds. Get HE, Renamer (which by the way I don't think is free), and your favorite remote dealer from this site. Done.
  11. Anyone have or know how to get hold of a sample of an engraved button (like what I would get if I ordered from C4)? I have white keypad dimmers (KD120). Looking to put one in action at the house to socialize the idea so I can get it on the family budget. Also, I had a previous dealer lightly recommend against using icons in the engravings - he just didn't they looked as good as the lettering. Anyone concur?
  12. My project size (based on backup size) has been running pretty constant over the past couple of years since install at ~10M. Recently I started getting quite a few more drivers and Experience Buttons installed and noticed the size at ~12M - seemed reasonable. Over the weekend I noticed I was at ~60M, a big increase. I'm suspecting maybe the bulk of that jump was from Experience Buttons, in particular the BlackWire Emoji pack (especially considering the "getting artwork..." step of refreshing Navs takes noticeably longer). My questions: Does that all sound reasonable? Do I even care? Do I need to be thrifty in asking for additional instances of the BW Emoji's to be installed or are those graphics shared across instances?
  • Create New...