simplextech

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.

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.

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.

Amazon hasn't released any API or method of directly interacting with Alexa. There are some hacks but only for devices so nothing I'm aware of for triggering a phone call. Google has a more open API and developer program however I'm not aware of anything that can trigger a phone call. Interesting though. Now if you had a SIP system say Asterisk or something that's more probable.

I'm not sure I'm understanding what you mean by this. The Nanomote is a Z-Wave button device. As long as the device is supported on the ISY you can use the buttons to trigger programs to do something.

Tell me when 3.0 comes out

Well that makes two of us as I was replying about "new" and you posted about a PLM v2.5 which is not "new". Either way doesn't matter. Glad there's new stuff coming out someday.

I'm not questioning them continuing business as usual. They will get more stock that's just a supply issue. I know there's "new" stuff talked about and some "new" stuff coming but so far there's nothing real about a "new" PLM with improvements. Wouldn't it be amazing if they made the RF part of dual band actually USEFUL?

Anything out there besides hidden filings? Any PR or announcements or physical product yet?

Z-Wave device range is typically fairly small inside a building/home due to many factors. Z-Wave overcomes this by using a mesh network design where the messages can be repeated by their neighboring nodes until the message gets to the correct destination. For a Z-Wave network to work properly and efficiently it takes multiple nodes to form the mesh. Most if not all Z-Wave Plus Powered devices (plugin modules or hard wired) are all repeaters and help form the mesh. Battery operated devices do not repeat messages and do not help with building a mesh. Insteon uses it's own distributed network topology where every powered node will rebroadcast messages and the destination will then respond. Insteon also uses the powerline as a network connection as well as RF for dual band devices. In a clean power environment Insteon is absolutely great.

Here. I just tried this one and you can download the JRE with no logins or problems. https://www.java.com/en/download/manual.jsp

I work with RedHat a lot at work but Fedora is more common at home https://www.oracle.com/java/technologies/javase-jre8-downloads.html I always use the tarball and then adjust my PATH as I want/need. There's deb and rpm's if you prefer those.

Which is debian If you had problems with the Oracle JRE you probably used too new of a version as Oracle removed Java Webstart (javaws) from the bundle. Stick with 1.8 and it works well on all of the distros I've used recently (Arch, Manjaro, Ubuntu, Ubuntu variants)

I wasn't very clear. The 5.0.16 FW does not support the new S2 security that everybody is touting. Most controllers don't support it and those that claim they do well don't support it very well. However I'm gonna have to recruit @Eric_Inovelliso answer why the switch won't include without security.