The arguments (discussions or discourse?) going back and forth towards the end of this thread reminds me of the old adage âyou are entitled to your own opinions, but not to your own factsâ 
Glad we are all working towards the same thing (i.e., exchange of knowledge for a better HE experience).
2 Likes
Yes, but in this discussion I see the validity (truth, if you will) of both points. "Mesh Network" is a term that is used by many manufacturers and it means different things in different contexts. Look at all the companies that manufacturer routers and wifi devices (access points, wifi repeaters, wifi extenders, etc...). So many of these companies call a wireless backhaul implementation of access points to be a "Mesh Network". I would argue it is not, or at least it bears little resemblance to a mesh network such as my zwave network. But who am I to say what they are allowed to call a mesh network. It is true that Lutron does not consider their Clear Connect to be a mesh network, but they are hardly the final authority as to what is and what isn't a mesh network. These days it is hard to pin down exactly what the definition means.
It's almost funny to view some of the diagrams of companies that are advertising their "Mesh" wifi products (Google for one). They look a lot like what Lutron calls a "fixed network" and not what Lutron calls a "Mesh Network".
So maybe Lutron is correct and Google, Ubiquiti, TP-Link and others are incorrect in calling a wireless backhaul implementation of access points to be a "Mesh". Or maybe its the other way around. I don't know, but I do know that the term Mesh, means different things in different contexts and to different companies.
Actually, on second thought, the only true implementation of mesh network topology is this one:
https://docs.hubitat.com/index.php?title=Hub_Mesh every other company's implementation is just a misunderstanding of what mesh network topology actually is. 
3 Likes
@Stephan.J , I understand your point (which I think is the actual answer/resolution to the discussion) and I also understood the perspective of each of the participants (which was the point of my perhaps weak attempt at humor). But that was my point, not quite as eloquently stated as your explanation, but my attempt to summarize the crux of the discussion with what I feel is a humorous saying (one which is even more apropos nowadays in this politically binary environment. . .I am a moderate that sees good and bad in both parties BTW). Again, my point was that sometimes (thankfully rarely in this community) some discussions are centered more on proving another person âwrongâ and another âfactual or rightâ when both may be the case. âAgree to disagreeâ is just a polite way to say âI am right and you are wrongâ and (to bring in another humorous saying) âOpinions are like a$$h0le$, everyone has one and I do not want to hear yoursâ, . Anyway, I will shut up on this matter as my attempt at humor was perhaps not so on target. No offense to anyone intended.
3 Likes
I can empathize what @silverton38's saying, but in his particular case, those details matter... As I understand it, he installs (and manages?) smarthome setups for clients...
Let's say he has a middling savvy client and he mentions that Caseta is a mesh system... Like it or not, the average joe's understanding of mesh boils down to believing the farthest out thing will extend everything, so that believing that could be troublesome if that client starts adding Caseta stuff themself later.
@silverton38 is most certainly entitled to his own thoughts on mesh-or-nay for how Caseta works, but I would just caution him to not use that term (mesh) to with his Caseta clients.
3 Likes
Don't forget we have hub mesh as well.... or is it 
3 Likes
I totally agree with your opinion. It is how the word "mesh" is interpreted. If a WIFI network can be mesh then the Lutron network can also can be a mesh network. If the meaning of mesh is that all or most devices have repeaters than Lutron is not a mesh and neither are WIFI mesh networks. I contend that the word "Mesh" is a word and companies use it as they interpret it or market it.
My only point in the conversation was that Lutron had repeaters available to it and I believe that is a Mesh of some kind as much as WIFI Mesh network is also a Mesh.
Hey guys, I believe the mesh debate has run its course. Let keep on topic regarding Lutronâs new Caseta dimmer and switch. Thanks!
7 Likes
I do keep my customers on the benefit and product level and I never discuss the technical.
2 Likes
Agreed!!!
1 Like
Another nice feature of the new line is the LED control. You will not have control from Hubitat but you can make those decisions in the Lutron app. It is a really nice feature.
1 Like
@ogiewon , Thanks for directing my thread back on topic! My original intent was to let everyone know of the new Caseta options and to have a discussion of some of itâs benefits especially given those (including myself) that were not so happy with the older switch/dimmer button design and operation (e.g., lack of pre-set dim level when turning on physically, etc.).
3 Likes
Man, I wish I hadn't seen this... I can't switch all my existing Caseta gear for these. Just... can't... justify!
Only thing saving me here is that the picos I've set up for multi-way lights don't match. Yeah, we'll go with that.
2 Likes
Keep in mind you can sell your old devices for about 75% of retail on E-bay.
1 Like
Anyone hear anything concerning a possible motion sensor that will work with Caseta and HE. Would be nice if they came out with a caseta switch with built in motion sensing and it all worked over telnet.
IIRC, the Home Assistant teamâs latest Caseta integration uses Lutronâs new Leap protocol. I believe the Caseta motion sensors are included in this integration. Thus, you could then use the Home Assistant Device Bridge (HADB) to bring those motion sensors back into Hubitat Elevation.
There has been some discussion about Hubitat eventually adding support for the new Lutron RadioRA3, which only supports Leap. If this comes to pass, then perhaps there will be a native solution for Hubitat as well.
3 Likes
My son was thinking of Lutron for his new home, but didn't like not having the last on setting. I wrote a rule that saved the setting to a hub variable when it was turned off and then a 2nd rule that set the light to that variable when it was turn back on. So problem solved.
4 Likes
Hi @Stu_The_K , so just so I understand (since I have over 40 dimmers in my home), you have two rules for each and every individual Lutron dimmer (original Caseta type) in use? Can you please post a screen shot example of your rules for one of your dimmers as I would like to implement your technique for at least some of my dimmers. Thanks for your help!
I tried this but when the light came on it would briefly go to full brightness, blinding you in the night, then go down to the level stored in the variable. Do yours not do this?
1 Like
This is why I asked for the screenshot of @Stu_The_K âs rules, as this was also my experience.
I donât have any Lutron devices. I created rules using an Inovelli Red dimmer to show him it could be done. He hasnât bought a Hubitat hub yet so I donât know about the bright flash.
