MrBill

Go to Z-Wave > Z-wave version in the admin console Series 300 z-wave will show as version 4.55.00 the last compatible firmware is 5.0.16C (and you can order the upgrade to go to Series 500) Series 500 Z-wave will show as version 6.81.00 you can use the latest and greatest is 5.3.3 (even tho it's labeled 'test build' go ahead, it's been out for awhile and no one has reported major issues yet things have been fixed since 5.3.0)

(Note: in the text below, replace IP.ADDR.OF.ISY with the actual IP address of your ISY) you can go to http://IP.ADDR.OF.ISY/rest/nodes in a browser window to get a listing of all nodes. what is between the <address> </address> is the exact text you need for the red portion: ${sys.node.ZW002_1.BATLVL} (hint: this page can be huge... use browser search or 'find in page' to poke around for what you're looking for.) next append that to the URL in the browser: http://IP.ADDR.OF.ISY/rest/nodes/ZW002_1 that will list just the node with the included properties included, In my example we will use wind: http://WW.XX.YY.ZZ/rest/nodes/n007_wind <nodeInfo> <node flag="0" nodeDefId="wind"> <address>n007_wind</address> <name>Wind</name> <family instance="7">10</family> <parent type="1">n007_mbweather</parent> <type>1.11.4.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>n007_mbweather</pnode> </node> <properties> <property id="GV0" value="1208" formatted="12.08 mph" uom="48" prec="2"/> <property id="GV1" value="334" formatted="334°" uom="14"/> <property id="GV2" value="15" formatted="NNW" uom="25"/> <property id="ST" value="291" formatted="2.91 mph" uom="48" prec="2"/> </properties> </nodeInfo> so in this case: .ST is the wind speed .GV0 is the gust speed .GV1 is the wind direction in degrees .GV2 is the cardinal wind direction so ${sys.node.n007_wind.ST} is what I would use for wind speed.

@mango here's the body of one of my pushover messages: token=[redacted]&message=The Spa Temp is ${var.2.31}\nOutdoor temp: ${sys.node.n007_temperature.ST} Wind Chill: ${sys.node.n007_temperature.GV1} \nWind: ${sys.node.n007_wind.ST}/${sys.node.n007_wind.GV0} ${sys.node.n007_wind.GV2} \n is replaced with a new line character (a.k.a return key) making this a 3 line message.

Try looking at the Programs > Summary Tab. Usually you can find runaway programs by watching that tab. If you find one Disable it. If you don't know what you did wrong with it go back to the details tab and right click the program name and pick Copy to Clip Board and then paste it into a message here and tell us what it's supposed to do so we can help fix it.

Since you're asking this question I assume that the pushover is sending ${sys.node.ZWXXXX.BATLVL} instead of the value you're expecting. That probably means that ZWXXXX isn't correct, or there is not a BATLVL value for that node. (I don't have any Z-wave nodes to make a screen shot and circle things sorry) How is battary level expressed in the admin console as a % or volts? if volts try .CV instead of .BATLVL You could me a screen shot of the node details and post it and we might be able to help further.

i think they just use up a tiny drop of space on the SD card... doesn't seem to consume vital resources.

I use pushover and have MANY network resources so that I can have the message customized..... Hint... discover the copy button for programs or network resources... it makes it faster to set up repetive messages and programs, Copy, edit the copy, copy, edit the copy...etc..

Reading this thread from the top makes me wonder if the SD card might have died.

related: essentially you can proceed as bumbershoot suggested, or you need to create a 'message', either email or Network Resource with each users friendly name. then a program for each different notification. The ISY doesn't store strings as variables.

I read it to mean the ISY Event log... nodeservers do dramatically increase event log entries being written to the SD card. I recently adjusted some of my nodeservers and eliminated a couple that weren't really being used for automatons. My event log was recycling 64000 rows about every 20 hours, with my changes the log now recycles in just over 48 hours. On the topic of micro SD cards, I think the answer is just have a replacement on hand, and don't buy cheap off brands, and look for the newer A1 rating.

I'd just take the batteries out, they will appear "out of range", then you can disable any programs that use them. At the start of the cold season replace the batteries and re-enable any programs you have that reference them. Less to re-do.

I just turned off a bunch of tags because I upgraded them for more battery life. After you unpair the tags via the phone app or https://my.wirelesstag.net/eth/ then 1) first close the admin console (if it's open), then 2) on POLISY, go to Dashboard, Wireless tags, click the DETAILS button, then the Nodes Button, scroll down and find the tags you deleted and click the delete button on the far right of the line. (note you have to click "Details" button, before the "Nodes" button--even tho you can see the "Nodes" button 1 screen sooner) With the node deleted, you can now re-open the admin console and it will be gone. Another approach is just change the update interval on those 5 tags to "every 4 hours" which appears to the be the maximum and leave them paired. --- I'll tag @Jimbo since he wrote the nodeserver to see if he has anything to add.

open a ticket with UDI, email support@universal-devices.com

there was a bug where the log didn't display in the GUI. Try to check for Polisy updates and then update, then reboot again. my version is 2.2.13 and I have logs again.

Here is a link to UDI's direct store: https://www.universal-devices.com/store/ I suspect that if "it's not always happy" you need to do some troubleshooting. Could be lots of issues from communications, to poorly written programs, to network errors. We can generally help figure things out but we need a bit more information to get started. tell us what the issues are.

Last nights release to 0.0.9 is amazing. I worked with it for a little while the morning and the addition of favorites is my favorite so far!

The box on the first tab is greyed out because it's not just a tickbox anymore. if you click change location there is now a dropdown at the bottom of the page.

I like it, no one will see it tho ???

Don't forget to use the Invisible Bold Red ink !! ??

If the blue light is next to Port A it's part of the 300 series Z-wave board. the 300 series board is only compatible up to and including ISY firmware version 5.0.16C. For all firmware after that version you need a 500 series board. See this link for more info on special pricing if you need to upgrade. You may need to have the device closer to pair, there may also be a need for establishing repeaters.... if you're new to z-wave we should get @lilyoyo1 to link his post on creating z-wave networks.

It's chris's fault... he used that invisible bold red ink.

You have a series 300 z-wave board. The first lines of the first post of this thread state: its fairly simple to upgrade the z-wave board. see here for special pricing: https://wiki.universal-devices.com/index.php?title=Z-Wave:_Ordering/Assembly_Instructions If you do not upgrade the hardware you will need to stay on version 5.0.16C and not upgrade further.

Does your ISY have a BLUE LED on the back next to Port A (shine the flashlight on your phone on it if it's not lit).. If so it means you have a 300 series z-wave board and 5.0.16C is the highest version you can use. What version where you coming from when you got in trouble.

if you haven't opened a ticket yet email support@universal-devices.com

@Tedsan if you do have the blue light series 300 board that reports z-wave version 4.55 as mentioned by @DennisC then you should roll back to version 5.0.16c, that is the highest version number of ISY firmware that will work with series 300 z-wave boards.