Bumbershoot

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.

You might write a program to increment a STATE variable by +1 at the top of every hour. Write a second program that fires when the STATE variable changes. Wouldn't that have a minimal impact on ISY resources?

I'm not sure that this is the same issue, but if you look at the 5.0.16B release notes, the issue with the leak sensors was fixed (and it was for me). My heartbeat program for leak sensors now seems to be operating as intended under 5.0.16C. A couple of my sensors occasionally miss a heartbeat, which have been correctly reported. The heartbeats resume the next day, and that also was correctly reported.

You might have a couple of things going on. If Polisy can't find the ISY (I assume that it was communicating with your ISY as some point), you might want to look into you network environment. Very likely something has changed -- maybe a new IP address for your ISY, new firewall rules/software, new router? IcedTea is a free, open source implementation of the Java platform, using OpenJDK. IcedTea-Web is a browser plugin. If you're running a Linux distribution as your desktop OS from which you launch the Admin Console, then you may very well run it using IcedTea. If you're not running Linux as your desktop OS (and even if you are), you will probably have better luck running the AC using Oracle Java. I have no idea how you would have gotten IcedTea on your machine if you're not running Linux. I have been able to successfully run the AC on Linux using the '--nosecurity' flag: If you can log into your Polisy vis SSH and ping your ISY, then I'd be looking at software (firewall, anti-virus, etc.) as the cause of the problems. If you can't ping your ISY, then I'd start looking at your networking setup.

I'm making a guess from looking at your error log, but it appears that you might have connected your ISY to the MobiLinc Portal (I think your screenshot suggests that as well). The ISY can only connect to one portal service at a time. If you're connected to the MobiLinc Portal, you can't connect to the UDI Portal, and you'll get the results you're seeing. You'll have to choose which portal you connect to. There are advantages/disadvantages to both, but the cloud based nodeservers are not available through the MobiLinc Portal, only the UDI Portal.

I'm running 5.0.16C, and I have three buttons on the bottom of the page that appears when you click on the "Network Resources" tab. It appears that the "Export" button will export all of your NRs into text files (XML), and the "Restore" lets you individually restore the files you select. I haven't ever needed this functionality, but I believe the answer to the question is, "Yes".

Yes, open a ticket with UDI. support@universal-devices.com Also, it occurs to me that you might un-link and re-link the UDI skill before you do anything wildly disruptive.

I just ran some tests, and I can use Alexa to control devices here with what seems to be a latency of approx. one second. I ran a ping test to my.isy.io and the average ping response was 74.5 ms. It appears that the portal is up and responding normally, at least for me. Are your ping times to the UDI Portal similar? --- portal-1452145500.us-east-1.elb.amazonaws.com ping statistics --- 15 packets transmitted, 15 received, 0% packet loss, time 35ms rtt min/avg/max/mdev = 72.558/74.580/79.807/2.097 ms I can only imagine that something is amiss between your ISY and the UDI Portal. If it's not too disruptive, you might reboot your ISY to see if things improve (admittedly a blunt force approach). The only other thing I can think of would be that the UDI Portal isn't resolving correctly by your primary DNS servers for some reason, which might increase latency.

It might be local to you're network or Internet provider. The device response times to my Alexa commands are snappy. I haven't had any recent performance problems in this regard.

This might be the source of all your issues. Use the ISY Launcher to get yourself on the proper version.

This might seem a bit basic, but these symptoms seem strange: are your ISY firmware and UI versions the same? Check the Help | About menu. If they aren't the same, then the fix might be easy. If they are the same, then I'd think about opening a ticket with UDI support. Reference this thread if you do.

Glad to help. ? However... The MobiLinc portal won't get you the networking module, but you can still purchase the networking module from UDI for a lot less than the cost of a Polisy. But, get a Polisy... There's a universe of devices out there!

Okay, so you'll need either the Pro ISY upgrade or the Networking Module/Portal apparently. Sorry, I don't know where the magic lies. I'd guess on both, if I had to.

I've switched to this (though not entirely) and it's very fast. I like it because I wear an Apple Watch and the notifications come to my wrist so I don't have to fumble with a phone. Much faster than email. I've never tried to quantify it, but sub-second notifications wouldn't surprise me in some instances. Others, certainly within two seconds.

No, under the Network Settings tab, there should be three more tabs, starting with "Wake On LAN". See screenshot. It's possible that you need to have purchased the ISY Portal or the Networking module to get these tabs, I don't know.

Yes, if you go to your ISY Configuration | Networking | Wake On Lan tabs, and enter the appropriate credentials for the machine you want to wake. Then you can write a program that uses the "Wake On Lan" resource you just created.

I've used these for quite a while, but note that they aren't made for outdoor use. I put a desiccant pack inside a plastic bag then tie wrapped the bag around the units, and they lasted through three seasons. As a test, I left one uncovered in the garden and it only lasted a few months before it succumbed. I'll get some new moisture sensors in the spring, and I'll wrap them up the same.

I use the nodeserver. I have and continue to use them in the following ways: Temperature monitoring in freezers, wine fridge, my humidor, equipment cabinet, the attic and crawl space Humidity monitoring and control in bathrooms Occupancy monitoring in locations where a motion sensors form factor is inappropriate (bathrooms) -- used to turn off lights that are left on Monitor door openings and closings in freezers, wine fridge, liquor cabinet and humidor Measure soil moisture in dry areas in my garden to supplement irrigation (summer use only, in conjunction with NodeLink and Rainmachine) I like the small form factor of these devices, as well as the multiple and diverse data points they provide. You have to be willing to change batteries every so often if you query them frequently, but the batteries are cheap and they otherwise last for many months, if not years (I got three years out of moisture sensors). I use the tag nodeserver in conjunction with the Push nodeserver to get almost instant notification of events on my Apple Watch. Works like a charm.