Bumbershoot

Polisy is running FreeBSD and not Linux, so the package manager is 'pkg'. I don't think there's a C compiler available in the UDI 'pkg' repositories.

The MS II have quite a few more options. In the Options window, Motion | Report has an "On Only" selection. Use that, and your MS "Status" value will always read as "On". You'll turn your lights off with a program. It works...

The light I'm controlling here is in a scene with the motion sensor acting as a controller. Set your motion sensor to "On" only and use a program like this: Office Desk Off - [ID 0090][Parent 000A] If 'Devices / dirOffice / msOffice-Sensor' is switched On Then Wait 5 minutes Set 'Devices / dirOffice / lmpOfficeDeskLamp' Off Else - No Actions - (To add one, press 'Action') The "Timeout" value isn't used when the "On commands only" value is checked (screenshot shows options for an original Insteon motion sensor).

RTFF? Times have changed...

https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages I don't know about the device, but the error indicates that there's a problem with this particular file on you ISY. You may be able to delete this file through a telnet session, but if your devices are working okay, I wouldn't sweat it. It may be a sign of problems with your SD card, however. That said, if this indeed refers to your device 20, then an Exclude/Include may correct this. If it's inconvenient to do this, I wouldn't wait until the device functionality actually appears to be broken. Below is the definition of the error code: -110022 OPEN FILE FAILED This message below doesn't appear to be a big deal: Maybe this is random noise from one of your devices that the ISY ignores: -251001 UZW_MSGCODE_COMM_RXU_IGNORED Z-Wave: Unsupported unsolicited response message ignored I wouldn't sweat this one below, as this appears to be a normal network function:

It sounds like you may have decided against these, but there are two nodeservers of the ISY that can manage Flair vents: one Polyglot nodeserver, and NodeLink. I don't use these, so I can't say anything about them other than to make you aware that there are options. There may be others (other than the nodeserver authors) who have experience on this forum, so maybe some information will turn up. I'm sure that with a full deployment of these things and some clever programming of the ISY you could do some interesting things, but I have no idea if the ROI or comfort benefits warrant the expense/effort. Good luck!

There's probably no way anybody here can answer that. Are you installing it to use the portal for MobiLinc connectivity, or are you connecting locally? Also, can you give us an idea of what went wrong for you? Was it an ISY configuration problem, a local network problem?

We're not talking about the ISY having an open port, but your network device (cable modem, DSL modem, or whatever it is you use to connect to the Internet). You might be getting clobbered by a denial of service attack through an open port. Also, without a DHCP reservation for your ISY, your ISY IP address could well have changed. Have you unplugged your Google WiFi equipment for 30 seconds, as well as your cable modem (or whatever modem you use that connects to your cable, phone line, fiber connection)? You might just be dealing with scrambled routing tables in one of your network devices, somewhere upstream from your ISY. You might consider restarting all your network gear, giving the network 10 minutes to stabilize after everything is restarted, then retry to connect to your ISY. Your networking equipment may reinitialize upon restart and then be good to go. And you should really think about about a DHCP reservation for your ISY and Polyglot server, so you'll always know their IP addresses.

@asbril, I'm beginning to agree with @Jimbo and think that you've got something happening on your network. I don't know if you use IP reservations in your router, but the fact that your Polyglot server changed IP addresses and that you have trouble with the AC and that your ISY isn't communicating with the portal indicate that something is amiss there. Have you changed anything with regards to your router or your network settings? Have to tried to reboot your router?

Hi @asbril, I found this post from a user showing the same symptoms. It appears that there might be a some sort of authentication issue involved with the error. EDIT: Maybe you should reset the Username and Password back to defaults: Reset Username and Password to Defaults Use a sharp object to push and hold in the Reset Button till the RX, TX, Mem, Error lights start blinking (every second) Continue holding for another 5 seconds till the RX, TX, Mem, Error lights turn on/off consecutively (RX -> Tx -> Mem -> Error) Release If that does nothing, I might factory reset my ISY and restore a known good (and hopefully recent) backup. https://wiki.universal-devices.com/index.php?title=Resetting_Your_ISY

FYI -- One thing to keep in mind about using REST to get the value of variables: if you're using the 5.x.x series of ISY firmware and you have a precision value set for your variables to anything other than 0, you'll get a return value that you'll have to additionally parse. If the value of the variable in the ISY is '45.1' (precision 1), then REST will return a value of '451'.

I've never written Python, so I'm of no help there. I did find this handy little tutorial for using the XML ElementTree library in Python, however. It doesn't look too daunting at all.

You may have to wait more than 24 hours for a heartbeat to come in from you leak sensors before any status data shows. All mine now show status values of Wet = Off, Dry = On, Heartbeat = On, whereas nothing appeared in the status values under 5.0.16A. As for the Motion Sensor II's, if they're battery powered you'll either have to activate the "Set" button and query them, or have a program query them immediately upon sensing motion for the data fields to populate. If they're on USB power, they should be awake and populating periodically. Example program to query a battery powered MS II below. MSIIQueryLaundry - [ID 008D][Parent 00DF] If 'Devices / dirLaundry / Laundry Room Motion Sensor.1 ' is switched On Then Set 'Devices / dirLaundry / Laundry Room Motion Sensor.1 ' Query Else - No Actions - (To add one, press 'Action')

First of all, do your firmware and UI versions match? If they do, then I think you can just resave those programs. If they don't match, use the ISY Launcher to start the Admin Console.:

I didn't mean your ISY error log, but the individual Polyglot logs. You'll probably need to fix the certificate issue, in any event. As you migrate to Polisy (especially if you recreate your nodeservers instead of doing a backup/restore) this might not be an issue.

Have you written any new programs lately that might go into a tight loop? Can you open the "Programs" tab on your ISY to see if any programs are busy?

I guess the first thing I would do is shut down Polyglot then reboot your ISY. If your ISY functionality returns, then it's likely Polyglot. If it does turn out to be Polyglot, you may need to go spelunking through the nodeserver logs to see if there's any trace as to which nodeserver is causing the problem. Or, you could uninstall and reinstall the nodeservers to see if that fixes it. I don't understand how MobiLinc connected to the portal would effect the ISY, but you could shut off the devices that are running MobiLinc and reboot your ISY to see if anything good happens. If neither of these have any effect, then I'd restore from the last known good backup, leaving Polyglot and MobiLinc off while you do that.

Look at all the data the nodeserver provides. This tag is in my garage in a metal freezer, probably 75 feet from the wireless controller, with no line of sight (the usual walls, doors, etc.) between the freezer and the controller. These things are awesome.

This seems to take care of it: admin@polisy /var/udx/logs]$ sudo pkg install mongo-c-driver Password: Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. The following 2 package(s) will be affected (of 0 checked): New packages to be INSTALLED: mongo-c-driver: 1.8.1 cyrus-sasl: 2.1.27 Number of packages to be installed: 2 The process will require 3 MiB more space. 579 KiB to be downloaded. Proceed with this action? [y/N]: y [1/2] Fetching mongo-c-driver-1.8.1.txz: 100% 350 KiB 358.3kB/s 00:01 [2/2] Fetching cyrus-sasl-2.1.27.txz: 100% 229 KiB 234.5kB/s 00:01 Checking integrity... done (0 conflicting) [1/2] Installing cyrus-sasl-2.1.27... *** Added group `cyrus' (id 60) *** Added user `cyrus' (id 60) [1/2] Extracting cyrus-sasl-2.1.27: 100% [2/2] Installing mongo-c-driver-1.8.1... [2/2] Extracting mongo-c-driver-1.8.1: 100% ===== Message from cyrus-sasl-2.1.27: -- You can use sasldb2 for authentication, to add users use: saslpasswd2 -c username If you want to enable SMTP AUTH with the system Sendmail, read Sendmail.README NOTE: This port has been compiled with a default pwcheck_method of auxprop. If you want to authenticate your user by /etc/passwd, PAM or LDAP, install ports/security/cyrus-sasl2-saslauthd and set sasl_pwcheck_method to saslauthd after installing the Cyrus-IMAPd 2.X port. You should also check the /usr/local/lib/sasl2/*.conf files for the correct pwcheck_method. If you want to use GSSAPI mechanism, install ports/security/cyrus-sasl2-gssapi. If you want to use SRP mechanism, install ports/security/cyrus-sasl2-srp. If you want to use LDAP auxprop plugin, install ports/security/cyrus-sasl2-ldapdb. [admin@polisy /var/udx/logs]$

Not quite done, however: [admin@polisy /var/udx/logs]$ sudo tail -f debug.log Password: ld-elf.so.1: Shared object "libmongoc-1.0.so.1" not found, required by "udx-freebsd-x64" ld-elf.so.1: Shared object "libmongoc-1.0.so.1" not found, required by "udx-freebsd-x64" ld-elf.so.1: Shared object "libmongoc-1.0.so.1" not found, required by "udx-freebsd-x64"

Yep, I just did. [admin@polisy /var/udx/logs]$ sudo pkg install libbson Password: Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. The following 1 package(s) will be affected (of 0 checked): New packages to be INSTALLED: libbson: 1.8.1 Number of packages to be installed: 1 142 KiB to be downloaded. Proceed with this action? [y/N]: y [1/1] Fetching libbson-1.8.1.txz: 100% 142 KiB 145.6kB/s 00:01 Checking integrity... done (0 conflicting) [1/1] Installing libbson-1.8.1... [1/1] Extracting libbson-1.8.1: 100%

Looking at the udx log in '/var/udx/logs' I'm seeing this error: [admin@polisy /var/udx/logs]$ sudo tail -f debug.log ld-elf.so.1: Shared object "libbson-1.0.so.1" not found, required by "udx-freebsd-x64" ld-elf.so.1: Shared object "libbson-1.0.so.1" not found, required by "udx-freebsd-x64" ld-elf.so.1: Shared object "libbson-1.0.so.1" not found, required by "udx-freebsd-x64" ld-elf.so.1: Shared object "libbson-1.0.so.1" not found, required by "udx-freebsd-x64"

There's a new Polyglot version available this morning (2.2.8) which provides some interesting new items under the "System" menu. I don't know if these items are hooked to anything yet.

Have a look in the Wireless Sensor forum for ideas. I've used three methods to integrate tag data into my ISY: URL Calling, Kumoapps and finally the Polyglot nodeserver to manage my sensors. All three ways work; you just need to determine which way best suits your needs and skillset. For my 2¢, the Polyglot nodeserver offers the most utility, as the tag data is fully native and available to ISY programs.

On second thought, if you're okay with running a nodeserver, then NodeLink provides "ISY Data" that makes it pretty easy to program date related things. The program below would probably get you Memorial Day, every year: New Program - [ID 00C1][Parent 00A7] If 'Devices / dirNodeServers / ISY Data / ISY Data' Month is September And 'Devices / dirNodeServers / ISY Data / ISY Data' Week is 1 And 'Devices / dirNodeServers / ISY Data / ISY Data' Day of Week is Monday Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') Here are screenshots of the data as presented in the ISY: