booch

FWIW, an alternative option is separately adding a sensor (or two) to communicate position. There are micro reed switches that can easily be completely hidden in a rail and plenty of devices to read them, if interested/inclined to DIY a little. Certainly not the lux option, but does get you to the same place with much more flexibility and OoM lower-cost options on motors/components. Tried it myself on some heavy, custom RH drapes I wasn't looking to replace or majorly disturb and it worked great.

Welcome/happy to help!

What version are you on? How complex, e.g., number of devices/zones, associated programming, are your annoucements? Mine (and others) have acted up on 3.3.1 (e.g., T3s not playing at all, zone volume not adjusting, etc.) In my case, I've temporarily moved to zones vs. T3s and reducled complexity, e.g., fewer rooms, to restore. The other suggestions are good but your issues may be software-side, like mine. (Hopefully gets fixed soon.)

Hypothesis makes sense -- I've been experiencing the same thing with certain macros/agent commands. T3 annoucements/sound not playing also an issue for me/others I've heard of. Hopefully as the installed base expands they'll detect/resolve.

Do the Chime specs mention anything about max. simultaneous streams? I know my HIK cameras only support 6 due to processing limits (for the individually-negotiated connections C4 devices use, in my case). That said, since I've been on 3.3.1 all kinds of programming/agents have been buggy, and I had to delete and re-add the (same) navigation programming to get those working again.

There is a free, C4-developed driver called "Weather Station" which allows you to program off its variables, including outside temp. (I use wind chill to dynamically adjust my patio heaters.)

Ditto AC Infinity. (As a shout, their build/packaging is 'Apple level'.) I'm running two CLOUDLINE T6 duct fans as rack exhausts (routed through the wall to my conditioned crawl space). Also added additional intake grilles to both the rack and AV closet door. As others have said, there's def. balance/science to airflow, so I'd experiment with less relative intake vs. exhaust volume before cutting. Lots of good online tools to calculate CFM, etc. (See attached pics.) My rack is packed, so it used to get above 100°, now it's 80-85°, which protects against devices acting up due to overheat, and presumably, premature failure.

If anyone else happens to have the issue, I solved it by switching my non-Snap cams to digest auth. (Logging suggested the cams were getting overloaded by C4 calls via basic.)

Something is up with my iOS previews too -- no change in programming. If I toggle a few times between the camera feeds and overview they come back. Other navigators (T3s) are fine. Hopefully the next app. update addresses it.

The Shelly Uni can measure voltage. Not sure if/how that's exposed in Composer though -- the driver dev. (Chowmain) should be able to check that for you.

All this is possible with my setup, as it behaves like any other native device, accessable through 4Sight, etc. I have keypad buttons too and disable them when our cleaners are here, for example. The nice thing about going relay/contact, IMO, is you don't have to deal with third-party apps., cloud, drivers, etc. Mr. Steam sells a module for this purpose, FYI. Perhaps the other brands do too.

Not sure what functionality you're looking for, but I have my Mr. Steams connected to Z2IOs for power control and state monitoring -- works great. Made an experience button too, if helpful (below). MrSteam.c4z

Do you guys have a manual/doc. handy that elaborates on this? I'm competent enough (through massive trial and error, ha) to use public APIs, so I'm interested in the details/what's possible. Thanks!

Just speculating, but this may be legal/rights/licensing related to something in their stack rather than technological. (Not uncommon in product and may also be enforced via localization in addition to distribution.)

Yeah, I got ya. The ‘easy’ comment was more based on the lack of capabilities offered by competitive streaming boxes. (Looking at you, Apple TV.) The omission of local APIs in the (IoT) space really peeves me, as it results in tons of fragmentation and much useless hardware down the road (when companies drop support, go under, etc.) In defense of Roku, I also think there’s some logic in omitting comprehensive search capabilities — beyond what they’ve provided — in their API, as it’d necessarily vary by partner/channel, and those partners provide it. In this case, also integrating the YouTube API offers many ways to return the necessary content info. to pass. For example, I got on this because I want the TV’s to come on and launch a livestream if certain conditions are met (both from their YouTube channel/their Twitter feed and at the house), and the combination works well.

Just wanted to offer a quick take on this, even if way delayed. Was interested in doing this and got it (deep links to YouTube via Roku) working. It's pretty easy, actually. Roku has a local API published here and a deep linking tester here. The YouTube HTTP (POST) command to launch a specific video is: http://<your Roku IP>:8060/launch/837?contentId=<specific video ID>&mediaType=<what it is, e.g., episode, live, etc.> The API also lets you search for content vs. just call specific content and all kinds of other stuff. The commands can be sent a bunch of ways, including the Generic TCP Driver. Cheers!

Thanks, man! It was a bit of a byproduct of figuring out how to ad hoc activate my irrigation. Didn't really want 16 buttons for all the zones, so made these two consolidated buttons (below). Wife likes it since she's into landscaping right now which is all that matters, ha! (If you're extra curious btw, the way these work is first you select the zone on the 'map' of our yard, then it defaults you to 'test,' which is really just a 3m run cause my son likes to run through them. Clicking again takes you to 'auto,' which runs whatever duration the Rain Bird program is set for.) Irrigation.mp4

No -- it's just the 'Experience Button Key Status' driver repacked with images I made for each state plus a little programming to interpret the input and allow the 'clicks' to feel intuitive as you interact with it, e.g., once a number is selected by cycling, it goes back to the 'all unpressed' state. (Note that the video I posted above was created on my Windows PC though (running Android emulation), but that was purely to capture it for posting -- works identically on all navigators and phones.)

Thanks! Can recreate them in 8-bit and reduce the file size by about half, so will try that.

FWIW, I'm not a fan of the dealer model with its current constraints either given I'm a hands on/technically-minded guy and our local folks, while nice, don't get me anywhere near the responsiveness or depth I need to be comfortable with a ~$200K investment (not considering the 'soft costs'/annoyance if things weren't working in the house I live in). I now work remotely with someone from the forum (Ari) and it's totally solved that. Something to consider as there are a lot of good folks here.

Certainly a nit vs. a crisis-level issue, ha, but as I've accumulated more custom buttons (based of the Experience, UI Status drivers), I've noticed they load more slowly (lag) in the iPhone app./navigators than the unedited/commercial ones. Anyone know is this is a function of the architecture or I just need to compress my graphics/file sizes more?

Experimenting with a 'key code entry' UI button tonight and remembered this thread so figured I'd share. Built the below (video) which cycles through the state of all 'numbers' on the virtual pad in navigator. Enter code correctly (1-3-5 in this case) and it 'unlocks' (enabling functionality) Enter incorrectly, e.g., out of order, wrong length, etc., goes to off Select while 'unlocked' and it goes to off/'locked' Could of course tweak the concept, e.g., # of buttons, visual style, etc. If anyone's interested, happy to send. Key Code.mp4

Wish this was HIK! Still can't get any reliable motion sensing out of mine (or when I do, the right integration of the events).

Thanks for the tip -- will experiment. Thankfully, have plenty of pipe leftover for a short shroud!

Thanks!