RyanE

I'd try doing a FTUE restart first.
NOTE: You will have to re-connect the Wifi and to the controller if you do this:
Power off the remote, by holding the power button Turn on the remote, by pressing and releasing the power button, and as it's booting, press and hold the 'back' button. Continue to hold the 'Back' button until the remote comes up with the greeting screen. When you get to the 'greeting screen', you can then go through the first-time user setup.  If you choose the same room as the remote was setup in previously, it should attach to the same driver as previously, and settings should be saved.
RyanE

Upgraded locks, strikes, door protection etc. would be a first step, keep them out long enough that you could respond.
Obvious web-enabled off-site recording Camera on outside of garage, with an obvious sign, and two-way audio would be my second step.  If you could get notified and tell them the police are on the way before they get in, it may deter them.
Security panel in the garage itself, with door sensors, motion sensors that you arm when away, etc., with siren, and remote notification on alarm.
Moot point if you aren't close enough to respond when it's being hit...
RyanE

Most things you do there will just alert you to the smash and grab sooner.
You need to make it harder for them. Take longer. Attract attention, if you're in a location where that even matters.

I never got hte impression it was rushed - they bought the company and the rights to the remote, boosted it, made a matching software for it and done. Hardware wise the product was 'done' (now if it was was the 'right' remote is another discussion)
 
I'm no fan of the Neeo, then again I'm no fan of ANY touchscreen remote.
It just feels utterly unnecessary to me. A full colour screen with feedback (such as icon media display, permanent volume feedback) is nice and would be welcome, but I would MUCH rather have an SR250/260 style remote with a touch PAD (for swipe and gesture control) than a touch screen. I don't want, need or in any way care to have to look at a remote while using it.
I could sort of see a use for a screen that allows setup of specialty buttons/icon. But to me, that could be the home screen on a feed-back screen as described above with 3-4 hard buttons on the side to activate that (in other words, if room is off, have a few 'quick actions' to start: Cable box, Netflix, Disney+, 3 favourite radio stations/playlists....) Again, once you get the remote's muscle memory, I don't want to have to look at the remote to use it....
 
But to each there own.
Oh and yes I have a Neeo. Even my kids (who grew up knowing touchscreens on phones, tablets and indeed C4 screens) don't use it unless the other remotes are not (easily) found.

C4 isnt perfect but its a bold move moving off the platform just for a better remote control.  The SR260 may not be pretty without a cool color screen but how is it antiquated tech?  What can’t it do that a remote should do to cover 90% of required scenarios?
and for what its worth I am all for a better version of the NEEO with some 0-9 buttons, backlighting, etc. But getting rid of C4 for another platform just for a remote?  Unless you are only using it to control a theater room set up and not your whole home

I think that is highly unlikely, given how difficult/cumbersome it is to try to navigate cable boxes, Rokus, and many other devices via voice (even when voice is working perfectly).  Control4 IS investing in remotes, not sure where/how you determined that they aren't?

This is fine as well as the hardware makers continue to have open APIs, but you can get burned following this strategy.  We have seen it a few times - Sonos and MyQ are two that come immediately to mind and I am sure that there are others.

Yawn.  All was well until someone here decided to revive a 2yr old thread.

Not really a valid point, there's no irony to the base OS being Linux, because Linux has nothing to do with Director, which is a completely custom and *not* open source, and Director runs the home automation project, and other non-open source daemons on the controller handle audio, I/O, etc.
Director could just as well run on Windows or on a different or real-time OS.  It's literally even compiled and shipped for Windows (virtual Director).
RyanE

Not really a valid point, there's no irony to the base OS being Linux, because Linux has nothing to do with Director, which is a completely custom and *not* open source, and Director runs the home automation project, and other non-open source daemons on the controller handle audio, I/O, etc.
Director could just as well run on Windows or on a different or real-time OS.  It's literally even compiled and shipped for Windows (virtual Director).
RyanE

LOL

It's just giving a name to the audio streaming architecture. No technical changes.

The answer to this thread is no, Control4 is not getting lapped by open source solutions. But to think that a community based project couldnt eventually do it is silly.
The community based projects biggest strength and weakness will be that it tries to do too much because it needs to fit so many people's use cases. So in the end it will do a lot of things pretty good but none great. Control4 and other commercial products strength and weakness will be that it only supports a sub set of devices and integrations but will do them very well. I have always felt that Control4 has done the best of the home automation companies at trying to create really good 3rd party support for popular devices.

Anyone making an obsolescence argument against Control4 in favor of Home Assistant or open source platforms in general sounds like a cult member. It's a perfectly viable hobby, but I don't come from my woodcarving retreat and ponder aloud, "what are furniture stores going to do when this catches on!?"
Get a hold of yourselves.

I do want to add, something is obviously not working right here - not denying that, nor am I pointing to the hub, the devices, the mesh etc.
I CAN tell you that I trigger half a dozen HUE lights and other '3rd party' devices daily, numerous times a day even, and don't see what you're seeing. Hence looking into the way things are programmed is the first thought, even after the added info you've given.

Glad to hear at least they're consistent now... 
RyanE
 

As Cyknight says above, the Neeo and the imageserver daemon on the controller both cache images, and if you don't clear them out, and they get updated in a driver, any 'new' neeos won't necessarily have the same icons as ones that have cached it.
To ensure all the neeos are showing the same icons, your best bet is to:
Restart the imageserver daemon on the controller Perform a partial 'FTUE Reset' on each Neeo.  Steps: Power down the Neeo (press and hold power button) While pressing and holding the 'back' button, power on the Neeo (keep holding 'back') When the Neeo comes up to the screen with the 'Hi, nice to meet you', and the 'SET UP' button, power down the Neeo (press and hold power button) Power on the Neeo.  When it comes back up, it shouldn't ask for setup, and should use the previous setup, but will have cleared image cache. RyanE
 

Business case == "Naw, it'll be fine".

RyanE

As the 800 can run OS3.3 (hasn't been deprecated for that, as far as I know), it should run the colo(u)r wheel just fine.
RyanE

As the 800 can run OS3.3 (hasn't been deprecated for that, as far as I know), it should run the colo(u)r wheel just fine.
RyanE

OK, so that did change the icons on my older Neeo to the smaller versions (same as my new Neeo).  At least I now understand the issue… I really hope Blackwire update their Neeo images on the emoji driver and make them bigger again as the bigger icons work much better on the Neeo! 

We have a pyjama drawer.  It's self contained, rather than open plan, but it is immediately adjacent to the underwear drawer.

For anyone reading - turns out I had plugged a rogue airport express that was still configured as a router a couple weeks back on my network. I was planning to use it for an airplay2 streamer, but hadn’t turned off the routing configuration for it yet. Doh! Unplugged it and everything came back to normal. 

As Cyknight says above, the Neeo and the imageserver daemon on the controller both cache images, and if you don't clear them out, and they get updated in a driver, any 'new' neeos won't necessarily have the same icons as ones that have cached it.
To ensure all the neeos are showing the same icons, your best bet is to:
Restart the imageserver daemon on the controller Perform a partial 'FTUE Reset' on each Neeo.  Steps: Power down the Neeo (press and hold power button) While pressing and holding the 'back' button, power on the Neeo (keep holding 'back') When the Neeo comes up to the screen with the 'Hi, nice to meet you', and the 'SET UP' button, power down the Neeo (press and hold power button) Power on the Neeo.  When it comes back up, it shouldn't ask for setup, and should use the previous setup, but will have cleared image cache. RyanE
 

Not sure if Kevin Costner's blind faith is a good business strategy.

RyanE