Bumbershoot

I got that one too, but I turned it off: Z-Wave | Detect Button Presses | Off

A couple of gotcha's with GoControl/Linear Garage Door Openers. I have two of these devices and they both operate similarly. They included fine, but the devices never showed up in the device list. They were excluded/included again, and this time with the "S2 Access" box unchecked (only S0 is checked), and the interview completed and devices appeared in the device list. They control the doors just fine, but the "Status" value never appears. I changed batteries a couple of times in the tilt sensors, but to no avail.

My six year old Schlage BZ 469 excluded/included from where it is installed, which was a nice surprise (the Polisy is probably 40' away, but with a few repeaters in between). It only uses S0, but it's fully functional, and so far, snappy and reliable. The exclude/include succeeded the first time I tried, and quickly.

I found an issue with Z-Wave that's new with this release/Z-Wave hardware. I have 2 Enbrighten 26931 in-wall smart motion switches (Z-Wave Plus). These switches have built-in motion switches, for which there is a node (Motion Sensor). With the current hardware/software, the Motion Sensor node never updates. It did with the two previous versions of hardware (ISY 500 board and Zooz 700 stick). EDIT: Nothing related to the motion sensor "ZY003_155" shows up in the Event Viewer, FWIW. Here's the node info from Z-Wave X-Ray: <nodeInfo> <node flag="0" nodeDefId="ZY003_155"> <address>ZY003_155</address> <name>ZY 003 Motion Sensor</name> <family>12</family> <parent type="1">ZY003_1</parent> <type>4.16.1.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZY003_1</pnode> <rpnode>ZY003_1</rpnode> <sgid>155</sgid> <custom flags="384" val1="0"/> <devtype> <gen>4.16.1</gen> <mfg>99.18765.12338</mfg> <cat>155</cat> </devtype> </node> <properties/> </nodeInfo>

My version and date stayed the same in the About menu. I've added a couple of switches/dimmers from different suppliers, and it's worked. I also cold booted my Polisy before adding any other devices. The last device was probably 40' away from the Polisy, but I moved the Range Extender into that room.

Looks like it's working here as well, so indeed, thanks for the hard work with getting this update out. Curious though, an Aeotec Range Extender 7 doesn't produce a node in the device tree - not that I care as long as it works.

You can certainly restart PG3, but I don't think you have control over individual node servers. If you can SSH into your Polisy, you can enter this command: [admin@polisy ~]$ sudo service pg3 restart I don't know of any other way, unless you have port forwarding turned on.

I factory reset the Z-Wave dongle, and added an Aeotec Gen 7 Extender as well, along with an Embrighten Z-Wave Motion Sensor Switch, and neither show up as devices in the AC device tree. I had to add the devices twice to get them to include, however, as on the first inclusion, the inclusion times out in the interview process. The second inclusion was almost instant. EDIT: When I attempted to Z-Wave | Synchronize | New & Deleted with Interview the interview would not complete on the two included devices.

This means that process 17542 is still running. The process might be hung, or just busy. If it continues, you might consider giving your machine an orderly shutdown/restart -- I wouldn't pull the plug on it: sudo shutdown -r now

For now, this update is for Polisy only. For the ISY994i, the last version of firmware available is the version you're on, 5.3.4.

I'm in a similar boat as @gviliunas, @mwaite75 and @csteenwyk. The exclude completes quickly, but the include times out in the interview. I cold booted the Polisy, so there might be something missing from file early in the startup. EDIT: I'm going to do what I probably should, and that's factory reset the Z-Wave dongle and rebuild my Z-Wave network. It's not so big and cumbersome that it'll take that long, and I'm interested to see how it looks with a fresh start. Once in a while it's good to let my OCD impulses run... 😁 MYLOG.TXT

A comment I'll make is that switching from Polisy to eisy won't likely result in a dramatic performance improvement in the IoX software. As it is, even when IoX is busily chugging away, the Polisy CPU/RAM combination is basically loafing. I suspect that big improvements in performance will likely happen as the IoX software changes, not so much as the hardware it runs on improves. That said, faster CPU's and more RAM are always better. last pid: 60652; load averages: 0.48, 0.42, 0.36 up 3+20:00:34 07:16:42 47 processes: 1 running, 46 sleeping CPU: 0.6% user, 0.0% nice, 0.5% system, 0.2% interrupt, 98.8% idle Mem: 161M Active, 598M Inact, 96M Laundry, 2797M Wired, 267M Free ARC: 2259M Total, 1359M MFU, 657M MRU, 28M Header, 169M Other 1854M Compressed, 2190M Uncompressed, 1.18:1 Ratio Swap: 4093M Total, 4093M Free

Sorry, I can't answer any of these with authority. I can guess, though 😀 Yes I can't imagine why not, as data throughput likely isn't an issue I'd think so, yes See 3 above Yes Remotely locating the ZMatter dongle in a high, central location (away from your Polisy) might work very well. I'm considering this, as I'd like to have my Polisy in an accessible location, but I could put the dongle in the attic. I doubt that the data rates from the field to your Polisy through the dongle would be sufficient to swamp a modern USB device. The only advantage I see is that inserted in the Polisy, it's out of harms way. BUT, check with UDI first!

I'll jump in here. I don't know of any compelling reason for UDI to officially support HA on their eisy, but who knows, maybe they will. Barring that, you can install HA on a FreeBSD box, and I'm sure it will run beautifully. Here are some instructions to get HA running on FreeBSD: https://www.sysadsim.com/2021/03/running-home-assistant-on-freebsd.html Unless you're reasonably comfortable as a *NIX sysadmin, then I'd stick with the Yellow Box. Even if you get HA running using the instructions above, you'll still have to manage the software onboard your eisy, and that management will very likely involve the command line interface. If that doesn't sound appealing, then the Yellow Box might be way, way easier to manage.

I think you just need to get one of these: https://www.universal-devices.com/product/zmatter-usb-enclosure/

Right you are! I never bothered to look, so thanks for this tip.

Looks like this vulnerability was corrected in the repositories last month, so it's very likely your Polisy OS is fixed if you've clicked on the "Upgrade Packages" button after the correction date below of 2022-11-29: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 ============================================================================= FreeBSD-SA-22:15.ping Security Advisory The FreeBSD Project Topic: Stack overflow in ping(8) Category: core Module: ping Announced: 2022-11-29 Credits: Tom Jones Affects: All supported versions of FreeBSD. Corrected: 2022-11-29 22:56:33 UTC (stable/13, 13.1-STABLE) 2022-11-29 23:00:43 UTC (releng/13.1, 13.1-RELEASE-p5) 2022-11-29 22:57:16 UTC (stable/12, 12.4-STABLE) 2022-11-29 23:19:09 UTC (releng/12.4, 12.4-RC2-p2) 2022-11-29 23:16:17 UTC (releng/12.3, 12.3-RELEASE-p10) CVE Name: CVE-2022-23093 EDIT: For what it's worth, from a quick look at the files on my Polisy at '/usr/local/etc/pkg/repos', it appears that my Polisy is getting updated files from both the FreeBSD project and UDI specific repos. My guess is that UDI maintains a FreeBSD mirror as well as having a repository for their own software. This should mean that any updated packages from the FreeBSD maintainers should be passed along to Polisy users in relatively short order, provided users update their machines.

You need a DB9 <--> RJ45 cable, such as this: https://smartenit.com/shop/plm-serial-cable/ One of these cables shipped in the box that your PLM came in. The ports on the back of the polisy are for ethernet communications, not serial.

The current practice for updating packages is to click on the "Upgrade Packages" in the AC (screenshot):

Looks like you're not the only one to notice that today:

Send them an email: support@universal-devices.com

I have a similar setup, and nothing Z-Wave is "mission critical". I put the ZMatter card in my Polisy yesterday (along with leaving in the Zooz stick) and discovered that I couldn't communicate with Z-Wave devices at all. I don't know what to attribute that to other than having two Z-Wave controllers, both competing for the same RF, that the ZMatter card is stomping all over the Zooz stick. I deselected Z-Wave Support in the Configuration tab, restarted IoX and all is well again, minus Z-Wave. In my installation, the ZMatter card and the Zooz stick don't seem to get along... I'll probably wait until Tuesday for the migration utility, and if it's not available, then I'll remove the Zooz stick, re-enable Z-Wave Support, and exclude/include the devices with the ZMatter card. It'll be some pain to do it that way, but with a Polisy Pro, I can use WiFi and move it close to devices that don't support NWI.

It's simply another nice little box running FreeBSD. The value is in what UDI builds on top of the OS. FreeBSD is a rock solid UNIX variant OS, and there are basically no license restrictions to it's use, may be why UDI chose to use it, other than *did I mention* it's rock solid. Way back when, in my professional life, I ran a few FreeBSD machines in mission critical applications, and I might reboot them once a year, whether they needed it or not. It was always a panic to find the root password for those machines every year... Here's a rabbit hole: https://en.wikipedia.org/wiki/Berkeley_Software_Distribution

Polisy is running ZFS, a 128 bit filesystem. [admin@polisy ~]$ dmesg | grep ZFS ZFS filesystem version: 5 Windows isn't going to know anything about a ZFS file system, natively.

@simplextech, I don't know if this is a node server issue or a general PG3 issue, but restarting the node server does not perform the upgrade from v1.0.5 to v1.0.6. Several restarts of the node server, and no joy...