Bumbershoot

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:

I'm not entirely sure what you're asking for here, but in version 5.x.x of the ISY firmware, you can save temporal data to variables (see screenshot). As for this, there are two Polyglot nodeservers, Holidays and HolidaysGoogle. I don't use either one, but I do know that the HolidaysGoogle nodeserver uses the calendar of your Google/Gmail account. You'll need to be on the 5.x.x series of firmware to use Polyglot

I wouldn't downgrade. I had problems with my Schlage BE 469 deadbolt as well. A couple of things you can try: delete it from your ISY (not Exclude) and try a "Z-Wave | Tools | Synchronize Nodes" and see if it comes back with it's proper functionality. I eventually had to perform an "Exclude | Include" on the lock to get it to work properly, but I was able to do that with the lock still in place, and that's due to my having the 500 series Z-Wave board installed in my ISY. I'm not sure if everyone can get this result, as the signal might need Z-Wave + devices all the way to your lock for this to work, I don't know. It worked for me, however.

I have a Z-Wave Water Cop valve and it has always shown up as a binary switch. In my setup, the status of On = Closed and Off = Open. It does, however, operate very reliably.

Okay, I've got it and connected to the portal. Looks like that piece works just fine. In iOS, it appears that it uses "pull to refresh" to get a current sync of system state, but it appears that can only be done from the home screen? BTW, nice job of parsing the folder names and adding an appropriate picture for the folder.

@io_guy is, though I don't think he's released an install script for the Polisy as of yet:

You really should be using the ISY Launcher instead of 'admin.jnlp' See this thread: I believe the devices shown in red can be scene controllers, whereas the devices in blue can only be responders.

This iOS app controls my camera just fine. https://apps.apple.com/us/app/foscam/id924381688

I believe those have been gone for some time, but I’ve never shopped for them so I could easily be wrong.

I just bought some last month in light almond. They were a bit hard to find on their website, but they were there.

If this new PLM actually sees the light of day, then I think Smarthome might be indicating that they’re up to something interesting with Insteon. My hope is that they’re not simply placating the UDI/Indigo crowd with this device, but that they’re releasing it as a prerequisite for something new on their end. Ensuring the loyalty of HA early adopters like the folks here is important, but this crowd is also wedded to UDI. I’ll bet that they would like to grow their own ecosystem as well, which the current hub probably can’t manage. https://forum.universal-devices.com/topic/28097-advanced-iot-bridge-interface/

I don't think it is. You can control Foscam cameras using MobiLinc, however. For that you'll need a portal or use port forwarding through your firewall. See the MobiLinc website or visit the MobiLinc forum on this website for more information.

The portal has nothing really to do with this. You'll need to run Polyglot on a secondary device, such as a Raspberry Pi, and you'll need to be running the current 5.x.x ISY firmware.

FWIW, here's a screenshot from the Camera nodeserver. I believe the only control you'll have is to send your camera to preset positions (I don't use that feature, so I can't report on how well it works).

Good catch. I just got my email notification that all my leak sensors had a missed heartbeat, and likewise, all the values for leak sensors in the AC are blank. I'm running this set of programs: I just re-ran the "then" stanza of the "Leak Startup" program in case it didn't get started properly on startup. I'll be out of town for a couple of days, so we'll see what it looks like when I return. Fortunately, then house will be occupied.

You can do this easily using the REST interface of your ISY and the utility 'curl'. Try something like this: curl -u USER:PASSWORD http://192.168.x.xx/rest/vars/set/1/3/16 This will set the value of variable type 1 (INTEGER), variable number 3 to the value of 16. If you were changing a variable of type 2 (STATE), the script would look like .../rest/set/2/3/16. Put that into a script and you're golden.

You'd think that the ISY would be very tolerant, being event driven. The PLM has to be at least somewhat tolerant, given the uncertain/unscheduled nature of the i/o environment it deals with. We're not running polled SCADA systems here. Stuff happens with it happens. I would think that this might come down to something as simple as the availability of buffers in the PLM (just speculation, I have no idea how the PLM actually works). This could be an interesting experiment for someone with the right resources.

Currently, I don't think so, but I don't know, and with the current PLM, it's impossible to know. But, there's a Polisy out now, and I understand that UDI wants to migrate the ISY to it. More system resources equals more links?