jfh

I’ve moved all my Rollease shades/motors from the original pulse hub to the new version 2 Pulse hub and have the the new V2 drivers from Annex4 (free) running on OS 3.1
The design of the hub is beautiful and I don’t think anyone would have a problem with it out in the open.  The new drivers provide IP control (by 2.4 wireless or Ethernet) so you no longer have to connect the hub by RS485 serial.  The hub boots very quickly and individual motors can be set up very quickly in the ap without having to re-pair motors by physically pressing buttons on the shade/motor (though that is an option) - you just use the remote to initialize the motor with the ap.  (I did 14 motors in about 20 minutes).  Not being tethered to a serial port on a C4 controller has allowed me to move the hub to a more central location and discontinue use of the Rollease signal repeater.
There is one driver per hub and one driver per motor.  The hub driver will self discover motors which makes set up easy.  Motor names are now exposed making the bindings easy for the dealer.  The current versions of the V2 drivers (0.57 and 0.55) look/function like the v1 ones (the documentation hasn’t been updated though).   Note - if you use the C4 shade group drivers you will need new instances after the V2 motor drivers are installed or the selected group members will not “stick”.  Don’t know if this is a C4 or driver bug, but a simple fix (other than having to redo all the programming)
There are some small glitches on the early hub firmware (I’m reasonably confident the issues are with the hardware and the Pulse 2 ap and not the C4 drivers) that I’m working with Rollease support and development to understand and run down.  The Annex4 drivers still do not support calling defined scenes or fire event(s) on battery state (e.g. low/dead battery) which would be great functions to have and there is one issue I’ve found that could be either a hub hardware or driver issue (or maybe both) that comes into play if moving motors from a near open or near closed state.  I hope these can be identified/addressed quickly.
Some of my tests seem to show improved motor-hub communication over v1 but I’m not sure yet if that’s reality or my imagination though grouped motors seem to operate more smoothly together.

Useful if everyone uses a code to enter/exit each time.  Not so much otherwise.

Network Reset Instructions 1 - Unplug power
2 - Hold down Link\ID\Identify button
3 - Continue to hold down the button and plug in the power
4 - Hold link\ID button until Data and Link lights come on solid together (they will only be in this state for a couple of seconds). Let go before those lights turn off.
Note: In OS 2.10.1 and lower, the Caution LED appears solid blue during the network reset check. After updating to OS 2.10.2 and higher, the Caution LED appears orange during the network reset check.
Note: Performing a Network Reset on the controller running Director will also reset the password on the controller

Meta data sharing and feedback, mini apps, Apple Music control

‘Well, I’m mostly talking about local access but a criteria of “cameras in less than 30 seconds” for remote access makes remote access pretty much unusable for me.  I use C4 on my phone mostly to view cameras or trigger experience buttons after I’ve received a Pushover alert (usually after a doorbell or motion event) and I need to see cameras in a second or two, not just under 30.
But - even excluding cameras - overall OS3 is more sluggish than OS2 with the same project and EA5 from a performance standpoint running the system.  It’s just easier to notice when you are using an iPad.

Agree with everything in this post... except how much one uses Composer HE, I change and update things regularly (at least once a month and often 2 or 3 times a week).

And you can buy a driver from @msgreenf that will allow you to rename devices.  That driver plus Composer HE gives you a lot of flexibility.  Add in a good dealer and you can’t get a better system.

have a Little PDF which could be useful 
https://www.control4.com/docs/product/zigbee/best-practices/english/latest/zigbee-best-practices-rev-d.pdf
 

It’s pretty noticeable if you have any experience buttons on the main screen of a room or an active audio session.  Both take significantly longer to finish populating once the room is loaded. It’s pretty bad from an end user perspective.  I use an iPad for about 90% of my control interactions when I’m not using voice control with the rest on a T3.
 
 I’m considering buying a CA-10 and I’d be fine doing so if I knew that would be enough to overcome the noticeable sluggishness I’ve experienced since moving to OS 3.1.  It’s certainly not my wireless network (significantly improved); it has to be some combination of OS3 and the EA5.

Control4 is under new leadership and the feature is at the moment not looking good 
Hopefully they will see the light 

@South Africa C4 user You had me all excited for a moment ...

Yes of course. Only difference is you would be streaming over wifi rather than a hard wired sonos device (not that it really matters). Also you couldn't select the music from your T3s (again probably doesn't matter to you)

Oh and another reason for sonos is that is has great Alexa integration so you can just ask Alexa (or Google for that matter) to play whatever you want to listen to through the sonos.

I'm not suggesting that keeping sonos is a good idea, just trying to give you the information.

Sent from my SM-G975U using Tapatalk

Simplicity of just plugging a Sonos speaker into a power outlet and you have music. 

Agree 100%.   I understand the issues dealers might face but don’t have a lot of sympathy for the lack of disclosure argument given how little information C4 itself discloses (at least to end users).
 
Your “Wild West” point is key though and pretty much applies to any third party driver (hello Extra Vegtables, HouseLogix and others).  As an end user (and certainly as a dealer) you have to weigh the risks of “how long will the driver work?” against “I really want this function”.  I’ve had C4 almost 7 years now and seen enough to know this conflict isn’t going away anytime soon.
If I couldn’t have the function provided by many of the Chowmain drivers and those from other 3rd parties, I’d have a C4 system that was little more than a glorified remote control.  C4 either needs to step up and take ownership or make it a lot easier for 3rd parties to provide function through open APIs.
 
 

"Dumpster Fire" is a term coined by another developer for a driver that doesn't follow an official API. Their point being that sooner or later, it's going to have an issue, one side or the other will update and break the driver's control. The trouble is for dealers it's not always apparent if it's official API, snooped, or a hack, and the client just knows they paid for and it isn't working so it's the dealers fault. (Snooped referring to watching the communications by another app that's controlling it; as oppose to a hack which might mimic another device to fool a cloud server, ie pretending to be an iPad).
Control4 will always take the API road. Got to protect their brand, right thing to do.
Now, many dealers are also campaigning to always only use API drivers. For the good of the brand, industry and reliability for your customers.
But automation is still the wild west. What is the developer's responsibility to disclose, update, support? Is it a one time purchase with the expectation it will work and be supported through all updates? Is it a one time at this moment use at your own risk, it works today, and we can't control the future? 
I'd like to at least see a disclosure of: its from their official API, or there is no API and we reversed engineered it. And appropriate related pricing. If it's an API and you're going to support it, than that's worth much more than here use at your own risk works today.
And kudos to the brands that are paying developers for creating complimentary drivers.

I still don't feel this warrants hacking a controller without warning.

Sent from my BBB100-1 using Tapatalk

Or the ability to turn the automation on a button off and then program against the button...

I think it would be nice for the hard controls to take over for the navigation of the Neeo screen in certain situations.  Eg when I press watch, I almost always naturally move to using the hard controls (the ring) to try and navigate the watch menu... 
This could be an option if some people don’t want it...

https://drivercentral.io/platforms/control4-drivers/utility/modes-agent/

Yes

It's been pretty solid, not a lot of defects reported against it, and quite a few fixed from 3.0.
Worth the upgrade, IMHO (I'm biased, of course...).
RyanE

Don’t hold your breath.
Control4 has shown no interest in doing even basic additions like letting HE users print out programming.  I was told two, maybe three years ago by C4 that was a reasonable request that had been added to the development list but It’s still not in the code (nor is any of the new programming detail in OS3).   (Essentially the DS functions).
 
And the locking down Pro to a specific project wouldn’t bother me, but it seems a little disingenuous to say that dealers would be concerned that non-dealer Pro users would encroach on their territory when existing dealers already do the same thing by offering remote services outside their area.

Don’t hold your breath.
Control4 has shown no interest in doing even basic additions like letting HE users print out programming.  I was told two, maybe three years ago by C4 that was a reasonable request that had been added to the development list but It’s still not in the code (nor is any of the new programming detail in OS3).   (Essentially the DS functions).
 
And the locking down Pro to a specific project wouldn’t bother me, but it seems a little disingenuous to say that dealers would be concerned that non-dealer Pro users would encroach on their territory when existing dealers already do the same thing by offering remote services outside their area.

I disagree that its a slap in the face... Most dealers in my area don't give a rats a$$ about the client once the initial install is done, UNLESS they are doing a large upgrade. 
This attitude could change if the housing market takes a dump, my closest dealers whom I'm friends with are so busy on new home construction installs they want nothing to do maintenance or small adds like single dimmers, adding a Roku, etc. 
I've long thought Control4 should offer another dealer/partner level, lets call it Programming and Tech Support.  Your not a dealer but your an independent programmer and can offer maintenance contracts, etc. You are still licensed through Control4, still have to attend/pass training, etc.  Maybe this costs $5000 or some other number... 
I know this is different that what was originally discussed/asked for, sorry. 
 

Yes.  You will have to recreate all programming if you move to v2.