jlemonakis

There's a project I was working on with a CA-10 and had the same issue. Same result with latest version of everything.

On 4/25/2022 at 10:23 AM, DLite said:

Thanks! I never thought to look there.

When you play with the Sonos network driver programming, leave the Sonos app open in front of you with the rooms screen up and you'll see what I'm referring to.

I like using the room control driver event "Listen device selected" as a "music is playing here now" trigger.

If you're specifically only using Sonos, look deeper into the Sonos network driver events/actions, since that is what directly controls Sonos matrix. On the output tab of the network driver events, "When audio [int] changed" directly correlates to the Sonos room joins, and is bidirectional with C4 at this point. "Audio x" is determined by which rooms are connected to the network driver audio zones. When I program stuff like this I like to have a list of each Sonos zone written down and the corresponding C4 Sonos network audio number that's associated with it.

On 6/4/2021 at 3:24 PM, WisC4 said:

Just switched from DS2 to Chime.  Previously had the DS2  recording to Luma NVR.  DS2 used to output a secondary stream that the NVR would display on a multi-camera layout in the web browser.  Chime does not seem to have the ability to offer a second stream so my Chime camera shows up blank in the multi-camera layout.  Any known workarounds?

 

 

Are you using ONVIF or RTSP? 

Really you should aim for at least -65 RSSI as the bare minimum for any device you want good connectivity with. Your issue is a combination of really weak wifi signal and NEEO has a garbage wifi chipset. Make a dedicated SSID on the nearest AP (and only on that AP) so that it doesn't try to roam to another AP. 

17 hours ago, msgreenf said:

Not 2 way. 

Yeah but if he's just using it to trigger the scene he probably doesn't need two-way and that should work perfectly.

Check things like what? Status of certain devices? 

You can use C4 to broadcast messages over Google home but I don't know if it supports the newest discrete room broadcast functionality yet, and development stopped.. But this will allow you to do what you're talking about. 

https://assistantrelay.com/

However this will not allow you to feed COMMANDS into Google home. 

I've been on the dealer end of this issue on a few sites, and also with the EA-5 in particular. Apparently it's like a "known issue" that after updates and stuff the outputs can get dropped/set to 0 (unacceptable imo), however in most of the cases I've dealt with it wasn't after an update and was completely random. C4 just acted like it shouldn't be happening and didn't hear about it from anyone else. I feel like it's another one of those bugs that was just never addressed. As far as I can tell it seems to be a director bug rather than a controller issue. It has something to do with a desync between the UI and director in that one area.

On 11/29/2020 at 9:30 PM, turls said:

The RoomMe sensors are on sale right now, but no sign yet of a smaller version.  I'm still waiting, as the way these work, it seems like you don't get a room exit until another beacon picks you up, so it is probably going to be pretty hard to pick only certain rooms to have a beacon in.

Sorry for late response. This was my experience as well, however I was able to successfully create an experimental "follow me". I don't use it much because I feel that it would only work really well if you're the only one in the house. I don't want to maintain other people's phones etc to make sure it's setup correctly.

Is there another Sonos device(s) that aren't hooked up to the matrix that are also not added to C4? I know some weird stuff can happen if you leave a Sonos device out of C4 that exists on the network somewhere, even if it's like a random Sonos One in a guest room or something.

Send audio from C4 into line-in on a Sonos device that has one. Make sure auto-play is enabled in the Sonos device for line-in. Make sure that ALL networked Sonos devices are added to C4. Program in C4 when audio is sensed on Sonos device that takes in the C4 audio, to connect the target soundbar(s) input with the line-in Sonos device input. 

Forwarding question from another topic that was asked previously in this thread. Is there any way to send POST commands using bearer tokens like OAUTH etc? 

On 10/30/2020 at 11:34 AM, zaphod said:

It appears that this uses HTTP POST commands so you should be able to send those commands using the TCP/IP generic driver.

In an ideal world someone would write a driver so that C4 could directly send those commands.

I've been trying to figure out how to make it work with C4 but haven't been able to yet because it uses OAUTH. How do you send post commands through C4 when there's a bearer token used?

Using Chowmain's driver it looks like I should just be able to put all of the info in as a giant data block but I'm not sure how to get the formatting right. Has anyone had any luck with authenticated HTTP post commands elsewhere and how did you accomplish this? I use HTTP Get on 99% of everything else which doesn't require the same level of auth or return any info back. 

I just set it up and was able to send commands to Google home. Now just need to tie it into C4. 

Has anyone had success with this? Assistant-relay seems like it could work in this way but I forgot about this. 

RoomMe, but like someone else said, don't think there's a way to switch the mobile client over to a different room in the way that you want. 

On 5/25/2020 at 12:14 PM, lippavisual said:

Your controller running director should be set statically.  I’d also advise any other C4 equipment to be static as well.

This way if your network crashes, router dies, whatever, your system will still chug along happily and keep working.

There have been many complaints about systems slowing to a crawl or just stop working when ISP services go down.  Mostly do to using ISP provided gear or keeping equipment on DHCP and router craps out.

Doing the above solves the problem.

 

 

No it doesn't anymore unfortunately. We always set C4 and other networking/AV equipment as a static out of range, and have noticed a lot recently that systems are becoming unresponsive or not functioning correctly (even just core C4 stuff that has nothing to do with Internet access). Apparently C4s stance is that the thing that can cause this now are some 3rd party drivers or cloud driver managers etc. 

I've had a bunch of them for I think around 3 years or so, with no down time. They're actually super reliable, and now the chowmain driver allows them to be added to advanced lighting scenes.. So really as long as you don't need a whole bunch of them (extra wifi congestion), and don't mind the other points already mentioned, they work very well in my experience so far.

Pushover works well for me unless you mean a completely local method. 

 off to on
	 
	 
	16/02/2020 19:23:59 - ReceivedFromProxy [5001] : CLICK_TOGGLE_BUTTON
16/02/2020 19:24:00 - Sending encrypted packet: {"smartlife.iot.lightStrip":{"set_light_state":{"on_off":0,"transition":1,"brightness":0}},"smartlife.iot.lighting_effect":{"set_lighting_effect":{"enable":0}}}
16/02/2020 19:24:00 - Sending packet: {"system":{"get_sysinfo":[]}}
��
	on to off

16/02/2020 19:25:20 - ReceivedFromProxy [5001] : CLICK_TOGGLE_BUTTON
16/02/2020 19:25:21 - Sending encrypted packet: {"smartlife.iot.lighting_effect":{"set_lighting_effect":{"enable":0}},"smartlife.iot.lightStrip":{"set_light_state":{"on_off":0,"transition":1,"brightness":0}}}
16/02/2020 19:25:21 - Sending packet: {"system":{"get_sysinfo":[]}}

On 2/9/2020 at 9:36 AM, alanchow said:

I'm overseas at the moment (Rome and then Amsterdam) but can look at this later on when i return to the office.

Having said that you are probably best to reach out via our official support means (phone, chat, ticket) as you will get through to either driverCentral support in the US or our own support team in Melbourne.

There's not really a rush since it's just at my house, but the C4 UI definitely doesn't respond to state properly (huge delay) even though issued commands from UI happen fairly quickly. 

The end result is, you press the light button, light strip responds about two seconds later, but UI doesn't respond to your press or physical state change for ~10 seconds. I have a bunch of HS200s in the house as well and both command and feedback happens nearly instantly. 

Get the roku ultra if it's for C4 because it has a lan port. 

On the KL430 I'm getting a different behavior than the rest of my Kasa stuff on power on/off. With the switches if I power on or off from C4 the C4 UI responds instantly and the light responds almost immediately after. If I turn off the light from the switch or from kasa for example, I understand that I have to wait for the set polling time to kick in for the C4 status to update.

With the KL430 when I turn on/off, I get zero response from C4 but I get an almost immediate response from the strip, and it seems like I have to wait the full duration of polling interval for C4 to catch up with what I pressed in the C4 UI. Is there any way to make it more responsive like the rest of your drivers or is this something to do with how the light strip communicates? I'm ok with status lights not updating instantly when state is changed from another source (as expected with wifi polling), but if I send the command through C4 I think it should react in the UI like the others if it's possible.

I have had 4 of them for a few months