
Bumbershoot
Members-
Posts
2413 -
Joined
-
Last visited
Everything posted by Bumbershoot
-
The first link is the one you want. Here's an upgrade task list put together by forum member @hart2hart:
-
If you can open a terminal session to your Polisy, you can type in the following command, 'uname -a', and find out what the Polisy OS is: [admin@polisy ~]$ uname -a FreeBSD polisy 12.1-RELEASE-p5 FreeBSD 12.1-RELEASE-p5 r361000 POLISY amd64 [admin@polisy ~]$ Additionally, if you run this command in the terminal, you can see what the updates are: tail /var/log/messages On my Polisy this morning, the single update was: May 26 05:15:25 polisy pkg[76768]: py37-lxml upgraded: 4.5.0 -> 4.5.1 The updates come from the UDI FreeBSD package repository (I believe), and they're OS updates, not nodeserver updates.
-
Any issues with moisture ingress into the battery compartment? Thanks for the report.
-
Amen to that. Try driving around here at twilight... The sprinklers make a bit of a racket when they start up, and the nozzles really put out a lot of water. They lose interest fairly quickly and they just wander off. Incidentally, they're more afraid of a little sprinkler that they are of humans -- they just look at us, then go back to munching. They think our dog is a coyote, however, so she gets them moving... I'm delighted at how well the communications works. I've got a pretty big back yard (the MS is probably 60', line of sight, from any other Insteon device) and the communications seem to be reliable.
-
I've got a deer problem. To deal with it, I repurposed an old Insteon MS and placed it underneath a stone bench in the back yard (so it won't get irrigated -- I believe it was @paulbates who indicated that he uses them outside with just a little superglue to fill the plastic seams, so I did the same). During certain hours, if motion is detected, it's used to turn on an irrigation zone for a minute (my Rainmachine and the Rainmachine nodeserver come into play). I have an Insteon outdoor module plugged in on my deck that aids with communications. This is new this spring, so I'm still fiddling with the MS settings. I have no idea how long the MS will last. I occasionally irrigate the dog when I forget to turn it off.
-
Just speculation here -- if this is a dimmer outlet, then that might make some sense, as only the dimmer receptacle would respond to a fast on/off command appropriately. If it's an on/off outlet, then a fast on/off command wouldn't provide any change in function to either receptacle over an on/off command. I'll bet that Insteon (not UDI, as fast on/off are available out-of-the-box in Insteon devices) uses the same firmware for both outlets, understanding that users probably wouldn't use the fast off/on commands where they wouldn't provide any change in functionality. The fix should be simple: don't use fast of/off commands against the bottom receptacle on a dimmer outlet, and don't use fast on/off commands at all on an on/off outlet.
-
I suspect that since changes were made to the "Adjust Scene" functionality, any scenes/programs that use that functionality will have to be looked at and/or modified.
-
I might be very wrong, but I understood that at some future date, when the ISY code is ported to Polisy, that Elk support would come through a nodeserver as well. @Jimbo has stubbed out an Elk nodeserver in the NodeServer Store. Just speculation on my part, but this architecture might be not be much of a liability, with the ISY and Elk nodeserver running on the same hardware, and nodeservers in general may be deeply integrated into the ISY codebase. Time will tell...
-
Have you purchased either the Networking Module for you ISY or the UDI Portal? You'll need either one.
-
If you held the reset button for 30 seconds, then you factory reset your ISY. It's easy to recover, provided you have a good backup. If you don't have a backup you can restore, then you will have to reconfigure your ISY and start over. https://wiki.universal-devices.com/index.php?title=Resetting_Your_ISY
-
For a standard on/off outlet, I don't see how there could be a difference between off/on and fast off/fast on. What might be happening is that this outlet shares firmware with the dimmer outlet, which has a dimmer control on the top. There, a fast on/fast off on the top would make sense.
-
Another plus regarding the Venstar ColorTouch thermostats is that they're the only WiFi thermostats I know of that use an entirely local API. No cloud connection is necessary or needed by the nodeserver (but it's available if you want to use the mobile app/website). There are several other good WiFi thermostats, such as Ecobee, but they need the cloud. Avoid a Nest, as they no longer connect with your ISY, even though there's still a nodeserver available -- the interface was deprecated by Google.
-
In the very first post on this topic.
-
[admin@polisy ~]$ sysctl -a | grep temperature dev.cpu.3.temperature: 50.6C dev.cpu.2.temperature: 50.6C dev.cpu.1.temperature: 50.6C dev.cpu.0.temperature: 50.6C
-
The ISY Launcher is the preferred method of starting the Admin Console these days. Using it eliminates the issues with having ISY firmware and UI mismatches. Instead of admin.jnlp, you use start.jnlp.
-
I've got ten bulbs above the vanity in the master bath, so I'm a bit motivated to manage the lights, even though they're LED bulbs. I use a PIR Kumosensor to manage turning them off, specifically because it doesn't draw attention, both by it's design and where I've been able to locate it within the room. The light switch for this room in conveniently located by the entry, so there is no obvious automation used in this space, other than the fan being on a timer.
-
The menu item that says, "Z-Wave dongle not responding" is interesting. This looks to me that you might have one of these problems: the Z-Wave dongle is not properly seated in it's slot in your ISY the Z-Wave dongle is defective, or the Z-Wave dongle is missing It appears that you have purchased the Z-Wave module from UDI (firmware). Did you also purchase the Z-Wave dongle (hardware) when you purchased you ISY? If not, you can purchase one here. If you purchased one, you might check to see that it's properly seated in it's slot in your ISY.
-
It looks to me that it wouldn't be much of a stretch to control this TSTAT with Network Resources. If I was a Python developer, I would have written a nodeserver for it myself, but alas... https://developer.venstar.com/restcalls.html
-
There's an issue with conflicting OpenSSL versions, I believe. In know the version included with Polisy has been upgraded since it was shipped, but I don't know which version Dotnet requires/includes. I haven't heard anything about this for a while, so I'm unsure what the status is. I'm still running NodeLink on my RPi until this is resolved. See this thread:
-
Well, for me, it's the Venstar Colortouch T7900. I bought it used from a forum member, and it's working beautifully. NodeLink supports it just fine, and the API is entirely local. I've got two remote sensors, and have been very pleased. T7900_OM_Install_FINAL.pdf
-
Maybe this: With no Z-Wave, it's not that big of a deal. You might have to re-save some programs, and make sure you note which programs you have that are disabled before you upgrade -- the "disabled" bit doesn't seem to always survive the upgrade. Additionally, any programs that you have that use the "adjust scene" functionality will have to be rewritten, as that functionality went through a major improvement. After you upgrade, look for programs that have "yellow" icons. They'll need your attention.
-
That error I've never seen. You can let us know what Z-Wave version you have installed. Use the menu "Z-Wave | Advanced | Z-Wave Version". If you're running the same "Z-Wave Version" and "Bootloader Version" as is shown in this screenshot, then you're version is current and no upgrade is available. This means that the 500 series Z-Wave dongle is installed in your ISY, which is the latest available.
-
You can't replicate everything in programs without variables (such as doing simple math as @mwester explains above). I would simply say that variables allow me to write fewer, more capable programs. EDIT: a simple way to look at a variable is to imagine your checking account balance as a variable: you write a check, the variable (balance) changes, you make a deposit, the variable (balance) changes. It's really just about that simple.
-
It appears that you need to purchase either the Networking Module or the UDI Portal (not the MobiLinc Portal) in order to get the proper functionality in your ISY. In your previous screenshots, you appeared to have had accounts with both the MobiLinc Portal and the UDI Portal. Now, it appears that you've dropped at least the UDI Portal, since the "Networking" and "Portals" tabs have been removed from your ISY. If you still have the MobiLinc Portal, then you'll need to purchase the "Networking Module" from UDI. You can purchase the Networking Module using the "Help | Purchase Modules" menu on your ISY. If you dropped both the MobiLinc Portal and the UDI Portal, then you have three options: purchase the UDI Portal which will give you both the "Networking" and "Portals" tab on your ISY, which will give you access to your nodeservers on your ISY, as well as the ability to connect remotely and use vocal assistants (Google Home and Amazon Echo), among other things purchase the "Network Module" from UDI as described above, which will give you access to your your nodeservers on your ISY purchase the "Network Module" from UDI and the Portal from MobiLinc, which will give you the "Networking" and "Portals" tabs on your ISY, which will give you access to your nodeservers on your ISY, as well as the ability to connect remotely and use vocal assistants. The simplest choice may be 1, but it requires a small annual payment to UDI. This also gives you access to cloud based nodeservers that would otherwise be unavailable. The subscription to the UDI Portal is less expensive than the MobiLinc Portal. The MobiLinc Portal has advantages if you are a MobiLinc user, but you must also purchase the "Networking Module" from UDI to use it. You can still use MobiLinc with the UDI Portal, but some of the functionality of MobiLinc is limited. Be advised that your ISY cannot connect to both the UDI Portal and the MobiLinc Portal at the same time. You only get one...
-
I would just increment the STATE variable +1 at the top of each hour. New Program - [ID 010D][Parent 00A7] If Time is 1:00:00AM Or Time is 2:00:00AM Or Time is 3:00:00AM Or ... Then $s.HourlyIncrement += 1 Else - No Actions - (To add one, press 'Action') The second program could have a simple IF statement (which will only run when the variable changes): If $s.HourlyIncrement > 0 Then Run Stuff You could just let the variable increment forever. We'll never live long enough for that value to get too large. I have a variable set to Unix epoch time, currently sitting on 1581696060.