NYInstallers

2 hours ago, msgreenf said:

The Facebook app causes it. Google it 

I have, we tried it.  It didn’t work.  Still same issue

I have one customer that continuously gets the attached prompt.  I’ve turned off everything except for IP control.  
does anyone else have this issue on SAMSUNG? Or know what causes it and how to prevent it?

I’m using a ubiquity edge router and ipv6 is turned off.  I have the same setup at multiple locations and have never seen this before.  It’s very odd.  

May not be the apple TV- any help would be appreciated. 

This is what i get on a release/renew via windows 

   IPv6 Address. . . . . . . . . . . : fd41:7a35:d2cb:454e:d4c7:39e3:5ade:7343(Preferred)
   Temporary IPv6 Address. . . . . . : fd41:7a35:d2cb:454e:a898:7342:852a:748d(Preferred)
   Link-local IPv6 Address . . . . . : fe80::3030:7ac7:16e9:eadc%15(Preferred)
   IPv4 Address. . . . . . . . . . . : 10.0.1.172(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Tuesday, September 5, 2023 1:57:05 PM
   Lease Expires . . . . . . . . . . : Wednesday, September 6, 2023 1:59:52 PM
   Default Gateway . . . . . . . . . : 10.0.1.1
   DHCP Server . . . . . . . . . . . : 10.0.1.1
   DHCPv6 IAID . . . . . . . . . . . : 234888386
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2B-C4-52-F6-8C-17-59-55-17-A7

and on the c4 controller (I X'd out some pf the info below.)

eth0      Link encap:Ethernet  HWaddr X:XX:XX:XX:XX:XX
          inet addr:10.0.1.XX  Bcast:10.0.1.255  Mask:255.255.255.0
          inet6 addr: fd41:7a35:d2cb:454e:20f:ffff:feXX:XX/64 Scope:Global
          inet6 addr: fe80::20f:ffff:feXX:XX/64 Scope:Link
          UP BROADCAST RUNNING ALLMULTI MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:333417 errors:1138774 dropped:7 overruns:0 frame:1138774
          TX packets:27083 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:175746887 (167.6 MiB)  TX bytes:14209221 (13.5 MiB)

I tried setting a static ip. It worked for ipv4, but ipv6 address still populates. 

Here’s what got me there.  
 

https://discussions.apple.com/thread/252823422

I've been having an issue with my EA-5 playing Amazon Music. When I got on the phone with a technician from C4 they looked at the project and told me the EA-5 will have issues playing music if they are assigned an IPV6  address. I didn't even know that my network was handing out IPv6 Addresses. 

So began the hunt and the Wire Sharking and the unplugging/plugging and a bunch of wasted time. 

Turns out the IPv6 Addresses are being handed out by the AppleTV4k devices via the Thread Network Protocol. 

So a few Questions

- Can(should) i disable IPV6 on my Controllers? If so how?

- Does anyone have a link to an article or tech bulletin discussing the EA-5 and IPv6 issues

- Is there a way to disable thread on the AppleTV 4K device?

- Does anyone have any luck working around the Thread network issue. 

Thanks

9 hours ago, Amr said:

Some pple will always complain regardless of the brand!

I don't think its a complaint as much as it is a critique. Capturing first impressions of a product is vital to UI/hardware design. The first impressions usually captures the intuitiveness of the design. When we layout light switches in a home - our goal is not to engrave anything- the experience we like to hand over is one that when a child walks into the room they know which button to press without thinking. We attempt to capture the first impressions and make the changes to the switches accordingly.

Being a NEEO user I did not find this to be a smooth transition- I felt that with the NEEO you turn on the TV this way and with the Halo you turn on the TV that way. Completely different experiences and I found the NEEO to be dummy-proof. And in general i am not fond of the icon changes they recently made. Control4 was on to something with the older icons, and ill repeat that i think it was a poor choice to attempt to conform to others. 

And i agree that they will obviously make improvements but I'm sure(i hope) they're looking at these sites and other for input on what changes are important.

Overall C4 is the best system on the market- the simplicity and stability is amazing. I've troubleshooted and work with many systems- none are this good. 

4 minutes ago, CTMatthew said:

My reaction was similar - especially given how great OS3 has been and how fresh it still looks.

Agreed- that is, pre- the new icons.

@CTMatthew Completely agree. OS3 was amazing in my opinion. It drew a lot of customers in. But the key of that success was mainly that the interfaces fell into 90% uniformity, so it was an easy sell to customers who run at the mention of a smart home.

Consistent design will keep C4 moving up. 

But its very possible its an OS4 preview that they're attempting to iron out.

25 minutes ago, South Africa C4 user said:

It sounds like waiting a few months before getting a Touch will result in a more pleasing first time experience.  At least most of the problems sound not serious or a software issue (unlike backlighting on the Neeo which was a serious issue and no software could fix that omission!)

Absolutely. 
 

And the backlight I agree, but after a month we could pretty much use it without needing to look at the remote. 

2 minutes ago, msgreenf said:

purposeful so you don't accidentually hit it

That’s why you have the room off confirmation.  
 

id rather two clicks than a total hand position change. But that’s just me.  

6 minutes ago, dinom said:

How often are you pushing the power button anyway?  It’s the same way on the regular Halo that a lot of us have been using for a while. To me it was unusual for a remote, but no big deal. Just like the power button on an iPhone. 

I barely use the power button on an iPhone.  The power button the remote turns off everything in the room so I need it every time I’m going to sleep, after watching in my den, when I’m carrying a load of dishes from the backyard and trying to turn everything is  off.  

8 hours ago, Topspin14m said:

My impressions so far.  I do miss the smaller, slimmer form factor of the Neeo.  That said, my wifi problems have disappeared and I love that the Halos have 5ghz.  The extra button presses are annoying but I assume they'll iron those out in future firmware releases.  Overall, I'm a fan.  If there were some way in the future to get voice working with Roku (I know this is a partnership issue) that would really be next level.

I’m hoping they’ll iron it out.  The only thing that worries me is the power button at the top of the remote cannot be moved that would require a retooling. I don’t understand where that came from.  

The power button being at the top forces you to completely change your hand position on the remote. That is already a big complaint when I’m showing this thing to customers. 

On 8/2/2023 at 11:37 AM, anon2828 said:

Agree.  The 3-line hamburger does not bother me as it is now a standard design element.  What bothers me is the horrible icons under the hamburger menu that are totally inconsistent with the rest of the UI in Control4.  In fact, I have not updated my system software because of this.  Really bad.

I will say that updating my system was great.  I was on 3.3.1 (I think) and there were some funky bugs.  The 3.3.3 ironed out a lot of them.  It was worth the UI change that will only affect the touch screen and app   

I got the halo touch, eh.  Not that thrilled with it.  I loved the neeo interface, size, feel and simplicity.  The halo touch is larger, the battery drains quicker (I did hear there are some workarounds), there are A LOT more buttons and the buttons are in completely different places  

Below is my list    If I am wrong on anything or you have a workaround please let me know   

- the power button is on the top edge of the remote.  Very weird.  

- mini apps require you to press watch after you select the app your want.  For example, if you press Netflix under Roku Apps and then you have to press one more button to start watching.  Very very annoying.  

- to get to things other than watch and listen you have to go to a submenu.  Very very very annoying when you’re waking up and just want to turn on the coffee maker or in the middle of the night you want to lower the AC.  

- changing rooms used to be done from the top of the screen but now it’s in a sub menu.  

- ok maybe the 5ghz compatibility is worth the battery issue.  But at least give us wireless charging capabilities if we need to charge it every night. I don’t want to give the impression that the battery runs out after an hour.  But if you’re going to drain the battery faster there should have been more ways to charge.  

- the NEEO was ultra responsive.  This remote is even more responsive.  

- I’m not crazy about the new interface on the remote. The interface is inconsistent with the new 3.3.3 icons. Even though I hate the new interface icons. I have no beef with using the hamburger instead of the logo.  But I think that was a silly branding mistake for C4.  They should have kept the logo. 
 

- when you goto list of lights.  You need to click into each light to turn them off instead of just turning them off down a list.  
 

and finally 

I realize the neeo took C4 in a new direction. So they weren’t able to maintain the interface consistency on the neeo as their other OS3 devices like touch screens, controllers, apps.  But why did they go even further on the halo touch. I happened to love the NEEO interface I think it was almost perfect. 
 

again please let me know if any of the above can be worked around or changed.  

On 7/10/2023 at 9:34 PM, PumpUpVolume said:

Now that we are solidly into Q3 2023, is there an update on the pre-order/release date for the Halo Touch?

I got my halo touch.   
 

I am willing to bet though that you will experience the same or other issues you did with the NEEO. There is definitely some underlying issue causing this and it won’t end until you sort that out   I realize you’ve very well documented everything above, if you’ve swapped out neeos and still have the issue then it’s definitely networking. I hope that I’m wrong though   C4 is amazing but when something like that doesn’t work it really ruins the experience  

regarding the halo touch I’m going to post some items about it.  In another post. 

On 6/20/2023 at 8:37 AM, lippavisual said:

Are you leaving any AV settings on the Roku set to Auto?  If so, don't do that.  Set them to what your system is capable of.

My guess with your MOIP setup is an EDID issue.

This seems to help so far. Funny enough though, the auto display settings on my roku seems to sit at 1080p even though the tv is capable of 4k it’s a brand new Samsung.  Don’t recall the model, but similar to the frame

Just wanted to add my findings on this.  I know it’s an old post but for those having issues here’s the end result.  
 

os 3.33

Araknis 310 for MoIP

Araknjs 310 for Wi-Fi, Zibee Controlers and doorbells 

Araknis 210 x 2 for general network 

EdgeRouter 

No special configs on routers or switches (aside from MoIP switch)

Ubiquiti UAP-AC-HD Access Points 

we had the same issues mentioned in these post originally  we went down all the rabbit holes mentioned and we were just chasing a ghost   Turned out we had a network issues related to a configuration on the Moip side   Once fixed everything works perfectly   
 

The Access points are configured on high power for 2.4 and medium for 5ghz   
 

smoothly operating   

Any questions I’m happy to help if I can   

On 6/14/2023 at 7:40 PM, msgreenf said:

Are you on the latest firmware? 

Am I the only person using Moip or is everyone’s Moip working perfectly?

Yes we are- I know that there were new updates a couple of weeks ago.
 

Majority of the customers are on Samsungs.  
 

I spoke to snap. They had me change HDCP to 2.2 instead of pass through.  I should also mention that we are on mostly ROKUs as well. 

We have Binary MoIP setups (at least 10) on an Araknis 310 Switch.  
 

every so often(varies 1-4 weeks) a device in a specific room may go out, meaning the screen is black but you can hear sound.  

restarting the receiver in that room gets everything going again.  

can anybody share if they have or had the same experiences.  And what they do to prevent them or giving the customer the ability to reset.  We have ovrc setup, watt boxes etc.  

Thanks

Resolved

2 minutes ago, Cyknight said:

in and of itself, there's no real difference between the mini and the full AKAIK. It's just that the full doesnt have the added space for keypads etc. As I've always understood it, the internal hardware is the same.

That’s what I understood as well, which is why this is so weird.  

Install was fresh.  And it’s now completed. Just troubleshooting the issue. 2 full sized DS2 Retain the call group setting with no issue.  And the two minis revert back to default all group- stays for a couple of days and then reverts back.  Everything’s been rebooted, updated etc.  

that’s the only real issue with the system.