simplextech

By direct for Zooz or rather their consumer frontend TheSmartestHouse.com https://www.thesmartesthouse.com/collections/700-series-z-wave/products/zooz-usb-700-series-z-wave-plus-s2-stick-zst10-700 May not be helpful to those up north.....

Curious why you're not developing with the official Silicon Labs UZB7 USB Stick? The UZB7 stick is the reference standard for development and it's cheaper as than the Zooz stick. It's also in stock at Mouser.com and other distributors.

Z-Wave battery devices must be "awake" and listening for a query to function. On most Z-Wave battery devices their manuals provide directions for how to wake up the device. This is usually 1 or more presses of the button used to include/exclude them.

As in Missing In Action

I'm sorry I have not been to Miami. Wait was that correct? Umm???

Oh sure I see how it is.... I go MIA busy with work and I'm forgotten that easily.... fine

Might… need to find time to work on a lot of the nodeservers

Hubitat has a Z-Wave and Zigbee radio. Not a Lutron radio. Hubitat like everyone else integrates using the Lutron integration protocol aka telnet interface which is great, local and fast. Hubitat from inception has had very good Zigbee support and Z-Wave was secondary. Hubitat is like a SmartThings clone except it's all local control and apps. It's not a bad system it just has it's quirks like any system.

I think that's perhaps some other Wink or maybe the original. I have a Wink 2 hub (in a box) but it had a built in radios for: Z-Wave Zigbee Lutron It was a very complete package of radio's but had a very limited set of "supported" devices. However those devices worked as intended. The major downfall was that it was all cloud based just like SmartThings. Yeah they were trying and marketing moving to local automation but it really never materialized and they lost market fast to other systems when their cloud reliability had a lot of outages. To top it off they slapped on a monthly fee and without paying well nothing worked then. Honestly I'm surprised they still exist.

Same thing

Pretty app based interface. They are the first and only 3rd party that I know of that was ever able to license ClearConnect from Lutron for support of Caseta devices. I think Wink is still limping along but they lost a lot of customers when they switched to a monthly usage fee. I haven't heard much about them in the last year or so though.

Just gonna ask the "why" question. Why do you need, want or care about the RF specs? It's a proprietary licensed RF implementation. Nobody else is ever going to implement it especially after the Wink fiasco. I really doubt Lutron will EVER release the specs and allow anyone else to implement it. The flip side is that the controller API is widely available and open or rather it has been with the Lutron Integration Protocol known to most as the "telnet interface". This has allowed Lutron integration to all major control systems and lots of DIY integrations. Lutron is moving away from telnet and using SSH in their LEAP implementation for system integration. Access to the LEAP integration currently has been restricted to partners for implementation. I know RTI, Control4 have implemented it for the HomeWorks QSX processors. LEAP is not available on the Radio Ra 2 platform yet but I suspect it will be on the upcoming refresh.

I will stand corrected with your source of the Type X Clea Connect, however it's not for any of the Lutron control Systems but it is their branding of a implementation they acquired with the Ketra brand of lighting (bulbs and fixtures). Ketra integration is only available with HomeWorks systems at this point as well.

No Lutron is NOT Z-Wave. Lutron uses their own proprietary protocol called Clear Connect. This operates in a licensed spectrum range. Lutron has a few family products they are Lutron Caseta (entry level), RA2 Select, Radio Ra 2 and HomeWorks (high end). Secret? All of the tech specifics are available on the Lutron site. No Clear Connect operates in the 2.4Ghz band. Where are you pulling this from? Oh now that's funny. So the future is the cheapest branded garbage you can find on Amazon? Sounds about right. Tuya is made to make it easy for vendors to go to market quickly with a generic offering at the lowest possible price point. They are horrible to work with from an integration stand point and expensive. Not to mention nothing is local so if you don't have internet then it doesn't work. Using a phone/tablet for turning things on is not "Home Automation" and neither are voice boxes. They are just another "remote control".

What to go with depends. Is Insteon going away? Unlikely. Are they slow to deliver. Yup. So if you want a lighting system that's been around a long time and will continue to be around for a VERY long time then go with Lutron. Lutron did invent the dimmer after all. You won't have appliance plugs (15A capable) unless you go with Radio Ra 2, but you can always use Z-Wave for those purposes. Z-Wave sucks for lighting (My opinion, shared by many) but it's great for aux devices like power plugs and such. If you have a decent controller and a good mesh then it's good for some sensors too depending on requirements. The old ISY994i is long in the tooth and is getting a much needed update with the Polisy. It takes time to port a system and work out all of the issues and make it as stable as the predecessor but it will get there. I'm hoping with some much needed improvements along the way (string support!!!!, increased node name length, etc) you know little things

You should spend some time on their forum reading about the z-wave issues... just saying.... their Zigbee implementation for ZHA is pretty good.

It's a in-between of Caseta Pro and Radio Ra 2. You get most of the capabilities of RR2 but none of the advanced devices such as the keypads, embedded modules or HVAC controls. From a programming aspect some of the sensors like occupancy are not exposed via the LIP (Lutron Integration Protocol) aka telnet interface. To program a RR2 system you must use the Windows software (requires training/certification to access the download) but with RA2 Select you use the mobile app. Now the plus of RA2 Select is that the devices are the same for full RR2. Which means there's a easy upgrade path from Select to full RR2 which only requires replacing the main repeater. RA2 Select also has native "cloud" functionality such as voice assistant integration and remote functions through the mobile app. To get the cloud functions and such with RR2 you have to use the extra Connect bridge. Happy to help with any Lutron questions or issues.

That's the RA2 Select https://www.lutron.com/TechnicalDocumentLibrary/3691062_ENG.pdf RA2 Select does not support keypads. They have Pico's listed as "keypads".

Black hub? That's either a Lutron Connect box that provides integration to voice assistants (Alexa, Google, Siri) or that's a Lutron RA2 Select system. RA2 Select does not support keypads which may be why there's none in the house.

kldload: can't load uftdi.ko: No such file or directory Looks like the USB FTDI kernel module/driver is gone.

Mass market with Zigbee and upcoming Matter is targeting the low end DIY hub systems and especially the Amazon Echo and Google/Nest trying to evolve into "hubs". Amazon tried with the Echo Plus several years ago and is now expanding the zigbee functionality into their other Echo devices as the mass consumer market are adopting things. It's also cheaper to manufacture a Zigbee device and have it certified through the Zigbee Alliance as each vendor doesn't have to pay for the full certification cost. They can piggy-back the certification by using the "pattern" of an existing device such as a light switch/dimmer and using the "verified" chipset and ZCL (Zigbee Command Library). This significantly reduces cost of development and manufacturing of devices. Zigbee is actually a great protocol to use for lighting which is why the majority of "bulbs" use it. The commands can be grouped and sent to give the synchronous lighting like Insteon does with multicast messaging. Z-Wave just can't do this as it's not a protocol level functionality (yet). Continuing to produce devices for Z-Wave is to keep security panel vendors and for semi-professional and professional systems that support Z-Wave (most of them). I don't think there will be any "new" innovation from Inovelli in regards to Z-Wave devices though or at least not for a while until they fill the coffers with funds from the mass market (consumer) sales.

I don't think I ever published it. It was a work in progress that I'll have to revisit.

You did? Sorry I didn't see anything. Yes I have developed a Withings NS. It's been a while since I worked on it but it is functional even in Beta quality.

I may have some ideas. The best option would be to develop a Control4 driver to interface directly with the ISY. I've always been interested in developing Control4 drivers. I don't install Control4 currently but I've been interested in it. Alternatively there is a Control4 driver for integrating external systems via TCP and HTTP commands. There's another driver that can be used for sending HTTP and TCP commands. Perhaps there's a driver that combines both. I believe drivercentral has them available to your installer. Using those drivers a crude setup could be done using the ISY network resources. With some effort it would also be possible to develop a Polisy NodeServer for a tighter bi-directional interface between the ISY and Control4.

Depending on how much vibration or rather how little vibration you're trying to detect you may look at "Break Sensors". There are Z-Wave versions of these as they are designed for security for glass breaking. Such as detection of someone breaking a window. Which is why I asked depending on how much or little vibration detection will determine if these would meet the requirements.