ILoveControl

On the Neo what would be really cool is to lock the screen. The screen sensitivity is so dam good but often find me opening my garage or front gate by mistake when the remote is next to me on the bed etc. Would really be cool if you could lock it and unlock by holding a key or code. #FeatureRequest.  

After having one pretty much since launch - DISCLAIMER *** my views based on  how I use a remote.
Pros:
Quality is excellent Great out of the box experience (nice little thoughts like the cable management) you feel like its a $600 remote. Usage is actually pretty good, glad they updated it some nice new features like volume indicator, locks and sensors and security. Screen is very responsive and good quality Navigation through the system is actually pretty easy and cool Not really a PRO but rather feedback. Often I have guests asking what is that remote and super impressed with it due to the quality and intergration so some "outsiders" non C4 views and perspectives are very positive. Great base station, next time add a USB port to the bottom to charge other devices. Chances are if you chilling watching TV  you have your phone with you and would be cool to plug in and charge  There is enough space and I would suspect most of the base is for weight.  Braided charging cable - nice touch. Cons:
Would be flamed if I didn't have these four but TBH none of these items bother me whatsoever. No back-light - I have gotten use to it so the button position I know and don't need to look down. Also most of the navigation I use the touch screen. Lack of some of the system functions i.e. Comfort, Intercom (not to use voice but to see camera) Lack of camera integration. The Screen is big enough to pick up if someone is being seen on a camera. No voice commands - again doesn't bother me as the common ones like Alexa, Siri, Cortana etc are tuned for American accents and don't really work that well where I live. The bottom part of the remote has a lot of wasted space could have done with putting a little track pad there to leave the screen open for any other bits of info. Tidal integration lacks a lot however I suspect this is a core Tidal driver issue and not the NEO. Overall will I be buying some more - Absolutely 
I am going to open the bugger up (yes don't care if warentee / guarantee is voided...) want to see what processor, flash and GFX they use. This will give us a good indication if the remote is capable of displaying cameras - then really there should be no excuse for camera integration. 

Thought I would post my leanings after a few months of subscribing to both and testing it with C4. Disclaimer:***** These are my views from testing, maybe different to other installations or experiences.
Off the bat - 
Integration into C4 - Tidal Note: it integrates but isn't that great. The interface is slow (well on T3 and Neo). Example when you pick up the T3 and if the screen is off the bottom bar where it shows you what A/C is on lags a bit to show it. Spotify - terrible, the reason its terrible there is no in navigators, navigation. You have to go to Listen> Spotify> then open Spotify and then connect to that device (which is your room). Choice of music - both really much of a muchness I did find though Tidal has a great selection of local artists (from where I live). Average for every 1 song I can't find on Tidal there are three or four I can't find on Spotify.   Ecosystem out of the C4 environment: Spotify win's with more integration into other systems, TV's, Car's, Fridge etc etc. Also where there is Tidal and Spotify on a device the Spotify app wins. Example, Apple CarPlay Spotify client allows you to add songs to your Liked list straight from the interface Tidal doesn't. Quality of music: No doubt here if you a audiophile then: Tidal Price: Spotify is slightly cheaper but then again it doesn't have the music quality (khz) that Tidal has. My decision between the two for every day music consumption: I actually don't know the two are so similar but yet have specific features that I need and one has it the other doesn't. For now I just have both and use a sync service in the cloud to keep my playlists the same. 
Anyway I know I was struggling with this so thought I would post this after some testing I did.

Apple have *never* done something unnecessary or stupid 🙂🙂 🙂 

The irony (and slew of rant posts from me on this) is that the DS2 is capable of this and much much more. It is for some unknown reason to man kind, that C4 insist that they will revert back to default any config you do via the web interface to the ds2. 
 
I have been doing a number of seriously cool configs and have researched the amount of 2N (manufacturer) modules etc for the door station we have. There are so many plug and pray modules from rfid, proximity Bluetooth for user access control to even pressure sensor pads for gate opening all of which, you can buy, connect and configure via the web interface ——- until the sync happens between C4 and the door station. It then reverts back to an expensive PoS.
You even have different choices of camera qualities as a plug and pray module into the door station. The setting for the camera exposure, motion capture etc is actually on the door stations web interface, just doesn't last past the sync between C4 and ds2 once configured (I had the same issue with light exposure from outside lights) 
 
The situation is so incredibly stupid from C4 I am almost finished with some linux code to block the sync between C4 and DS2 (happens once to d the config so you can get intercom etc then block the coms that does they sync). Then i can actually use he ds2 full capability and not be limited by C4 to 1% of the ds2 capability. 
 
Ok rant over as I know you feel the same pain. @msgreenf answer is most probably your best bet with Ring ..... the integration is not great but for now we at the mercy of one of the poorest design decisions by C4 since the inception of the system. 

Spot on man! Glad to see you using the best AI service  

Makes sense and good thinking with the beam sensor, you can get them for pretty cheap and you could even use the magnetic pressure sensor etc from 2N for the DS2 (if C4 didn’t insist on resetting your bloody settings all the time it syncs).

Would have to figure out how that would really work in my scenario but I am sure that is not an issue.

This is AWESOME question though is there an option to add more than 1000 requests a month? 

Thanks - I used to frequent SilentPCReview and Noctua fans were always highly rated on that site.

Noctua is frankly the gold standard at this point - though they tend to cost it as well.

@South Africa C4 user just checked my music services (tidal spotify) working perfectly on 3.1

@South Africa C4 user just checked my music services (tidal spotify) working perfectly on 3.1

So far so good on my side had to do a few reboots (c4 leaf matrix, triads etc but all good) HC 800 seems stable as well, but don’t have any IO on the HC800 all of them are on my EA5’s.
 

Ok so done extensive testing. 
BlueIris:
Works on all interfaces with all links that are applicable i.e. Snapshot, MJPEG, H264 and cameras that support H265 i.e. VLC i.e. Link in any browser ispy (like Blue Iris)
Works perfectly on all the interfaces as above (BI) Doesn't work at all generic driver Doesn't work of course in BI driver. Control4:
The Generic driver - doesn't work. However I think its an issue of how the driver builds the URL  The BlueIris driver - Works as we have been describing.  My View:
It is a driver issue Why It is either mincing up the URL or using the wrong URL Due to updates to Bl If all other interfaces work this points to BI. Unless we get a new driver that is well built and we can specify the URL we want to use and all it does is:
Uses the interface to specify the ip, port username and password.  Then allows us to specify which link for which type of view Then doesnt mash up the URL Shows us the URL it is creating (not like the BI driver - have NO idea why they encrypted the URL, this would of helped us trouble shoot better) Any dealer know the driver manufacture maybe he can update and unlock those fields Supports all the protocols - Snapshot url (then you could use these as well in the notification driver, the BI driver does not expose this) MJPEG H264 H265 (for cameras or BI) that supports this. For reference there is the URL's that I managed to get that the blueiris driver uses:
 

Thank you will do the testing today and revert. Just a note while we trouble shooting.

My wyze cameras with the dfang custom firmware work perfectly. The driver (from chowmain) talk directly to the cam stream not via BI.


Sent from my iPhone using Tapatalk Pro

Agreed have heard many times and on my post similar to this one on the ridiculous speed.

I am so glad they working on it and apparently fixes the connecting ..... issue.

I just don’t get why this specific issue is taking so long to publish. Being such a fundamental flaw, releasing a update for the app that just addresses this, would be a customer centric approach.

Only thing I can think of is that its a deeper issue that requires controllers to be updated etc ...

Same issue as the OSD it use to be so much faster in 2.x. I have two EA5s so its not like its a hardware issue ...


Sent from my iPhone using Tapatalk Pro

Oh cr@p sorry use tapatalk but was going from a bad gsm signal to a better one and the app just hung.


Sent from my iPhone using Tapatalk Pro

If I could offer some advise here as I have been quite busy w.r.t this specifically. So let me give you my situation:
I bought a Wyze Pan Cam when they first came out. I had updated the firmware as and when it came out. Then had the same question as you and was really interested. I checked out:
https://github.com/EliasKotlyar/Xiaomi-Dafang-Hacks 
Which is the site to download the firmware that unlocks quite a bit of features on the camera. The issue is and it has not yet been solved by the developers of this custom firmware, the Wyze developers changed something on the bootloader of the firmware to prevent custom firmware. The custom dev have not yet figured this out and the project was last updated 7 days ago. The update was small the majority of the files have only been updated 8 - 9 months ago.
All is not lost, I sacrificed a Wyze camera to do some testing (I am OCD and want to know how things work). There are some steps on reverting the firmware to the last known version that works. What does this involve?
If you know what you doing and have a linux preferably Ubuntu distro, you can install uboot-firmware-tools, there is a decompiled version of the last known firmware that you can compile to flash to the camera. This allows the custom firmware to then be loaded. There is really good documentation on this. If you want an already compiled version I have compiled one already. You can then try the traditional way of flashing the firmware (put the SD card in with the relevant files, hold setup and power on) once the camera starts doing its "turning" as it does normally when you turn it on, the firmware is flashed. Remove the SD card and power off and back on) if you get a blue light you good to go.  The success rate on this method varies. The best way and the way I did it, you open the camera up (two screws) you find the serial open pins on the board (good docs and pics on the site above) solder pin headers to it, then use a USB to Serial (with pins Ground, TX and RX) to the pins. Turn on the camera and use a program like putty to connect to the camera. You will see the entire boot sequence. Eventually you reach a terminal and  you can logon to the camera. When you see this again good documentation to flash the old firmware onto the camera and then repeat to flash the custom firmware on the camera. This works 90% of the time On the site (above) it states clearly that the custom firmware does not work  with firmware XX.XX.XX and above (you need to check the exact number on the site). 
The positive part, I bought 4 additional cameras from Amazon about two weeks ago. It was a chance I took as you never know what version of firmware is going to come on the cameras (you can check this with the Wyze app - be sure when asked to upgrade the firmware say NO).
All the cameras I bought had the old firmware. I did open all of them solder the pins and watch the bootloader while I flashed them to make sure nothing went funky. Also the serial interface is your best interface should things go wrong as it talks to the firmware chip directly.
I know this is a long post but I really did my research on this and went through a lot of learning to eventually make this work. 
To answer your question:
Does @alanchow driver work - ABSOLUTELY the caveat, it will only work on the custom firmware, so you have to check and follow the steps above.  This is not the fault of @alanchow driver more a move (to me sneaky) of Wyze changing the bootloader to prevent custom firmware. @alanchow I would add something like this to your driver page just to make sure customers know there is a risk.... I am more than happy to help (just can help with the soldering etc due to location) if you do choose to still go this way.
Just an additional note: there seems to be even more issues for some reason with the normal Wyze camera, the little square one, non pan version. They have no clue what the issue is yet. You can check the chinese sites like Alibaba etc as the exact same camera (same chips models etc) are available even cheaper.

If I could offer some advise here as I have been quite busy w.r.t this specifically. So let me give you my situation:
I bought a Wyze Pan Cam when they first came out. I had updated the firmware as and when it came out. Then had the same question as you and was really interested. I checked out:
https://github.com/EliasKotlyar/Xiaomi-Dafang-Hacks 
Which is the site to download the firmware that unlocks quite a bit of features on the camera. The issue is and it has not yet been solved by the developers of this custom firmware, the Wyze developers changed something on the bootloader of the firmware to prevent custom firmware. The custom dev have not yet figured this out and the project was last updated 7 days ago. The update was small the majority of the files have only been updated 8 - 9 months ago.
All is not lost, I sacrificed a Wyze camera to do some testing (I am OCD and want to know how things work). There are some steps on reverting the firmware to the last known version that works. What does this involve?
If you know what you doing and have a linux preferably Ubuntu distro, you can install uboot-firmware-tools, there is a decompiled version of the last known firmware that you can compile to flash to the camera. This allows the custom firmware to then be loaded. There is really good documentation on this. If you want an already compiled version I have compiled one already. You can then try the traditional way of flashing the firmware (put the SD card in with the relevant files, hold setup and power on) once the camera starts doing its "turning" as it does normally when you turn it on, the firmware is flashed. Remove the SD card and power off and back on) if you get a blue light you good to go.  The success rate on this method varies. The best way and the way I did it, you open the camera up (two screws) you find the serial open pins on the board (good docs and pics on the site above) solder pin headers to it, then use a USB to Serial (with pins Ground, TX and RX) to the pins. Turn on the camera and use a program like putty to connect to the camera. You will see the entire boot sequence. Eventually you reach a terminal and  you can logon to the camera. When you see this again good documentation to flash the old firmware onto the camera and then repeat to flash the custom firmware on the camera. This works 90% of the time On the site (above) it states clearly that the custom firmware does not work  with firmware XX.XX.XX and above (you need to check the exact number on the site). 
The positive part, I bought 4 additional cameras from Amazon about two weeks ago. It was a chance I took as you never know what version of firmware is going to come on the cameras (you can check this with the Wyze app - be sure when asked to upgrade the firmware say NO).
All the cameras I bought had the old firmware. I did open all of them solder the pins and watch the bootloader while I flashed them to make sure nothing went funky. Also the serial interface is your best interface should things go wrong as it talks to the firmware chip directly.
I know this is a long post but I really did my research on this and went through a lot of learning to eventually make this work. 
To answer your question:
Does @alanchow driver work - ABSOLUTELY the caveat, it will only work on the custom firmware, so you have to check and follow the steps above.  This is not the fault of @alanchow driver more a move (to me sneaky) of Wyze changing the bootloader to prevent custom firmware. @alanchow I would add something like this to your driver page just to make sure customers know there is a risk.... I am more than happy to help (just can help with the soldering etc due to location) if you do choose to still go this way.
Just an additional note: there seems to be even more issues for some reason with the normal Wyze camera, the little square one, non pan version. They have no clue what the issue is yet. You can check the chinese sites like Alibaba etc as the exact same camera (same chips models etc) are available even cheaper.

Maybe you never hear anything on Unifi as people don't have problems?
Your previous statements are strong, but without details.  Unifi can provide a stable infrastructure, both wired and wireless. When thats in place there should be almost no connection with application layer programs, period.
Do note I said STABLE. Most problems are simply caused by network instabilities and flakey features of the infrastructure (I do know Unifi has some features that cause instability on wireless connection when turned on, but at the same time they care beta features) or human error.  Almost never have you heard someone claim vendor XX's implementation of ethernet worn't work with my app.
 

You could always get a autonomics mms1e and play Spotify directly through c4 without the need of Spotify connect.  Very similar to old Sonos driver from 2-3 years ago. This would give you seemless Spotify integration.

They need to release this like asap


Sent from my iPhone using Tapatalk Pro

The old app use to load really quickly, the 3.0 app takes ages to connect (and no it's not my wireless). 
 
Anyone else experience this?

Yeah i think then you would have a really cool complete driver profile. Also remember a lot of users have work outlook and Office 365 is the biggest office platform on the platform. You would have a bigger user base this way.
 
i am happy to beta test for you if you would like

This looks insanely good! Well done! Now for the outlook calendar please