simplextech

Oh that's interesting. It's not loading for me in FireFox (CloudFlare error page) but it does load in Chrome just fine.... hmm.

Anyone have any info on CocoonTech and why it's been down?

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.

Can you expand on this question a little more? What HA boxes are you asking about? I'm still catching up....

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

The range of a plugin device/repeater is always going to be greater than a device inside a wall.

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.

Isn't that normal for SmartHome?

When I had Insteon KPL's I tested this "feature" with HomeSeer. It does exist and it does work. It's also documented in the Insteon developer documentation. Not many ever implemented the feature.

First thing that stands out is you have a broken mesh. You don't have any powered devices that act as repeaters. This would explain the hit/miss of query information and intermittent issues.

This I understand. That piece of information gets left out. It's not the reliance on a PLM it's the poor history of longevity of the PLM.

This rational never made sense to me. No matter the protocol a "controller" is required. Whether it's a PLM or Z-Wave board, USB stick or external bridge some controller to interface with the protocol is required.

Go ask alarm.com or their support site.

Although the hub can be used with HomeSeer it is NOT recommended nor preferred from either plugin. The PLM is really important and vital to lots of system integrations HomeSeer, Indigo both prefer PLM OR ISY integration for Insteon RTI, CQC, MyServer all prefer to integrate with ISY which also requires the PLM. What about control4 @lilyoyo1??? I'm thinking Crestron integration likely requires ISY or PLM. Long term if the ISY994i as we know it goes away and the new Polisy doesn't support Insteon.... well me thinking that Insteon is going to die soon afterwards.... hmm... sounds like more Lutron sales... LOL

I've seen supply issues with many vendors. Want another one that has buzz about discontinued products just look Logitech Harmony and everyone speculating their discontinuing the remotes. Highly unlikely but that's the "rumor" that's being repeated.

This would be the very first thing I would do.

There are options. However floor t-stats usually also have a temp probe to ensure you don't melt/burn the floor. So keep that in mind of adding a temp probe if going with relays.

The NuHeat nodeserver for Polisy is published. It does use their cloud API however the NS itself runs local. There is a PGC version available as well which is using a different API version. As some point they are supposed to converge and I'll likely combine them. For floor heat thermostat's the Nuheat and Sinope are the only one's I'm aware of that have integrations. Sinope is not integrated with the ISY because it is a Zigbee thermostat and I've not (yet) started on adding Zigbee functionality directly to Polisy. Sinope does also offer a "bridge" interface which I looked into but they only work direct with vendors not 3rd parties so they won't give me the API. I don't know if Venstar offers a floor heat thermostat or if one of their models would work or not. You might contact them and ask.