Chris Jahn

Yes, due to the leak sensor issue, we are planning on having 5.0.16B next week

Thanks guys, just wanted to verify the device types. We made a fix to triggerLinc's not reporting status, but looks like the fix broke leak sensor status updates.

Hi kstock, From a browser, can you please do the following for one of you leak sensors and send me the output. http://<isyAddress>/rest/nodes/<leakSensorAddress> (e.g. http://192.168.0.11/rest/nodes/6 3B 8A 1)

Hello Everyone, Build 5.0.16A is now available https://forum.universal-devices.com/topic/27669-release-5016a-rc1-is-now-available/

Hi Stephan, What ISY release to you upgrade from?

ONLY USE THIS VERSION OF FIRMWARE IF YOU HAVE Z-WAVE 300 SERIES CONTROLLER. IF YOU DO NOT HAVE Z-WAVE OR HAVE 500 OR 700 SERIES Z-WAVE PLEASE UPGRADE TO THE CURRENT RELEASE [for the ISY994] (5.3.4 - AS OF JULY 2021) Update 2020/01/26 - 5.0.16C 5.0.16C (RC1) is now available, it contains the following fixes in addition to the changes below 0000707 - Options button fails for Schlage lock (add delay between option queries) 0000730 - Open/Close sensors incorrectly change status when heartbeat message is received 0000731 - Z-Wave dongle not responding when electricity module installed 0000736 - Clients not notified when node notes are modified 0000737 - No query performed of Z-Wave device when issued from web browser (UDAjax) 0000738 - Nodes disappear from the ISY device tree Update 2019/12/19 - 5.0.16B 5.0.16B (RC1) is now available, it contains the following fixes in addition to the changes below 0000724 - Insteon Leak Sensor status no longer updating in ISY 0000725 - Admin Console strange behavior on Mac when changing scene links Update 2019/12/06 - 5.0.16A Note: 2019/12/08 - A bug was discovered in 5.0.16A causing Insteon Leak Sensors to not report status or create control events to trigger ISY programs 5.0.16A (RC1) is now available, it contains the following fixes in addition to the changes below 0000703 - Takes a few seconds for popup menu when right+click on Z-Wave node 0000705 - Increase text string storage used by ISY and node servers 0000706 - /rest/status occasionally returns incomplete XML 0000710 - Insteon TriggerLinc not updating status correctly 0000711 - Add more alarm controls for Z-Wave Yale Locks 0000715 - Support older Leviton Z-Wave devices that do not fully support Version Command Class 0000716 - Using Basic Set/Report Binary Switch Set/Report options do not work for some devices 0000719 - Support additional EMS Device classes 0000720 - Missing description for SOILT status 0000722 - Alllow multiple attempts to log into admin console 0000723 - Show progress bar in Admin Console when uploading Node Server profile files All links in this post now point to 5.0.16C Hello, The 5.0.16 (RC1) Release is now available. - New - Options have been added to Z-Wave nodes that allow you to control when the device is automatically queried and what Z-Wave messages are sent by the device when a button is pressed (or a sensor is triggered). - Upgrading from an ISY 4.x version to this version may require a lot of manual intervention including verifying scenes, programs and program settings are correct. The 5.x ISY firmware and the data files it uses has changed drastically from 4.x. - If you are upgrading from version 5.0.10 or earlier then Devices and programs are migrated in the current version. After upgrading: o Please ensure your device nodes and programs are correct; in some cases you may need to update them. o Wakeup your battery devices after the ISY has restarted and the initial query has finished - The old style of encoding node actions and conditions is no longer supported in the ISY, but these entries are automatically converted to the new format in the Admin Console. Developers, anything that creates programs using the old style of encoding must change to the new format, or, you must instruct your users to convert these programs by loading and saving them using the Admin Console. - Developers, we encourage you to support HTTP chunked transfer encoding as soon as possible because we intend to make it the default option when 5.X is officially released. - If you are upgrading from version 5.0.8 or earlier, you will have to manually update the Adjust Scene entries in all of your programs. - Starting in version 5.0.15A, the event value for the Low status of Insteon FanLinc Motor changed from 63 to 64 Important User/Password changes: - If your current version is 5.0.7 or earlier, then after installing 5.0.8 or later your userid and password will be reset back to the system default. - If you restore a backup created from 5.0.7 or earlier, your userid and password will be reset back to the system default. - If you downgrade from version 5.0.8 or later to version 5.0.7 or earlier then after installing version 5.0.7 or earlier, you will have to Factory Reset the ISY and optionally install a backup taken in that version or earlier. Java runtime memory (when Admin Console is very slow to respond) - If the admin console is slow to respond, it is likely you need to increase the amount of memory allocated to the Java runtime (JRE). - Open the Java Control Panel, select Java tab, press View button, then add or modify the Runtime Parameter -Xmx to the following: o -Xmx512m - Press Ok to close the window, then Press Apply to save the changes Please review the known/recreated bug list to determine if this build is suitable for your installation. If you are looking for stability, please continue using 4.6.x branch. Fixes in this build: 0000654 - No instant status in ISY for Z-Wave Inovelli NZW37 0000658 - ISY Assumes cool & heat setpoints are available when setpoints are supported by a Z-Wave device 0000669 - Add nwi/nwe learn mode options to ISY (only changes how ISY itself is added/removed from a Z-Wave network) 0000680 - Add inches/day and mm/day units of measure 0000681 - Cannot update node notes from portal 0000684 - Replace device doesn't work between Insteon RemoteLinc2 and Insteon Mini Remote 0000689 - Z-Wave ack not received when putting device back to sleep 0000691 - Cannot see device address when using high contrast in Admin Console 0000693 - Add missing uom conversions (e.g. KM/mile) 0000694 - Some Z-Wave devices send BASIC REPORT instead of BASIC SET for button press 0000696 - Add support for new Barrier Alarm events 0000697 - ISY only allows on/off for iBlinds control 0000698 - Support Z-Wave Aeotec Doorbell 6 (Sound Switch Command class) 0000699 - Make the automatic query of a Z-Wave node optional after a command is run for that node 0000700 - Support OpenADR load control for node server nodes Notes: - SSLv3 is now disabled. All models now support TLS1.2 and high grade cipher suites - 4.1.1 backups may corrupt Z-Wave configuration in case they are restored. 4.1.2 and above releases fix this issue - See our Wiki for additional information (e.g. Program Variables) Prerequisites: - You must use the 5.0.9 Admin Console or greater to upgrade to this release (5.0.16). - If you are migrating from 5.0.8 or older than in the Admin Console, you will have to manually close the Initialization progress bar - The latest release of Java must be installed - If you are using MAC Yosemite and Java 1.8.40, please follow these instructions - If you are using Z-Wave, see Z-Wave prerequisites below - If you have not already done so, reconfigure your Climate Module to point to HAM Weather Stations instead of WeatherBug. Without this configuration, ISY will not process Climate Information. This is especially important if your previous station didn't include a station close to you. Install: 1. Backup your ISY (File | Backup ISY) - Do not backup from a version 3.1.6, or 4.1.1 system (there were bugs in those versions that caused the backup to be corrupted) 2. Make sure you have done everything in the Prerequisites section 3. Download firmware - ISY 994i Series including Z-Wave support - ISY 994i ZW, Z, or ZS Series (Z-Wave/Zigbee and/or if you do NOT have a PLM) 4. Login to the Admin Console and choose Help | Manually Upgrade [the name of your system] 5. Choose the file downloaded in step 3 6. After the upgrade, You must clear your Java Cache 7. Launch the 5.0.16 Admin Console and/or Dashboard by going to the following link: - https://isy.universal-devices.com/start.jnlp Note: If you have version 5.0.8 or lower installed on your ISY, then use this link instead: - http://isy.universal-devices.com/994i/5.0.16/admin.jnlp Note: MAC 10.6.x users must use the following links instead - http://isy.universal-devices.com/994i/5.0.16/admin16.jnlp (Admin Console) - http://isy.universal-devices.com/994i/5.0.16/dashboard16.jnlp (Dashboard) 8. To launch the Admin Console directly from your ISY, go to the following link: - http://your.isy.ip.address/admin.jnlp 9. If you are using Z-Wave and upgrading from a 4.x.x or earlier version of the ISY, see Z-Wave migration from 4.x.x branch below 10. Backup your ISY (File | Backup ISY) Z-Wave prerequisites If you have not already done so, please ensure your Z-Wave firmware is 4.55 (Z-Wave | Advanced | Z-Wave Firmware Version). If not, you will need to upgrade the Z-Wave firmware to 4.55: 1. To preserve your existing Z-Wave network: - Shift primary control to a secondary controller (such as an Aeon minimote). - Exclude ISY from the Z-Wave network - Upgrade the Z-Wave firmware (Z-Wave | Advanced | Upgrade Z-Wave Firmware) - Include ISY back into Z-Wave network - Shift primary control back to the ISY - NOTE: Even with this procedure, you may have to exclude your door locks and add them back in 2. To do a fresh Z-Wave install: - Upgrade the Z-Wave firmware (Z-Wave | Advanced | Upgrade Z-Wave Firmware) Z-Wave migration from 4.x.x branch All Z-Wave nodes will be recreated when migrating from 4.x.x. to the 5.x.x branch (they will retain the same Z-Wave address). After the ISY has restarted with the new firmware installed: 1. Start the Admin Console and do a Z-Wave -> Tools -> Synchronize Nodes -> All - Do not open ‘Programs’ tab until step 2) - This will add back all of the ISY nodes that were deleted at startup. - If you have multichannel devices, you will see more nodes added - After sync is complete, restart the Admin Console and go to step 2) 2. Open the programs tab - Most old Z-Wave device actions/conditions are automatically converted to the 5.0 framework - Make sure to visually check all programs that contain Z-Wave device actions or conditions. - Programs containing nodes from multichannel devices will have to updated - Node addresses for multichannel devices change from ZW003_143 style to ZW003_002_143 (where _002_ is channel number) - If everything looks good, save the program changes made by the migration. 3. Make an ISY Backup 4. If you are missing any Z-Wave devices you may have to exclude/include them again. For battery devices, make sure they have communications turned on and try doing a synchronize again.

Hello, There is actually an option for showing the green/red icons in programs, and I suspect it was somehow shut off. In the Programs / Details window, right+click on the My Programs folder and select Status Icons -> Detailed

Hi Guys, The old RemoteLinc2 types are different than the Mini Remote types. For example the 8 Button Remote link 2 is type 00.12 and the 8 Button Mini remote is type 00.1A We don't currently show them as compatible for replace device but I think we should. I'll add this to the bug list.

Hi Bill, It looks like chart is working for us, so hopefully the following will help us recreate the problem: - Is this a problem for both Insteon and Z-Wave? - can you specify an example device type(s) that is giving you the problem (specific product/model number etc. would be most useful) - Please DM or post a screen shot of the chart Thanks!

You could try opening the event viewer to level 3 to see if ISY is sending out a LOCK command. Is it possible that you have an ISY program doing this? I'm not sure what you mean by "connecting the lock directly to the ISY", but If the ISY cannot see the other lock then you may have to exclude/include it again. FYI/ Even as a secondary controller, ISY assumes that it is the central controller and writes/rewrites associations to all the devices in the network.

Hi Asbril, Can you please try doing a restore to get all the nodes back, and then do a synchronize and see if the nodes disappear. If they disappear then it is because the Z=Wave dongle does not think that device is in the Z-Wave network and thus deletes the ISY nodes for the device. In this case, you will have to exclude the device and include it again.

Hi ChadS, Sorry for you troubles in migrating to 5.0.12. The ISY does create associations to all association groups supported by the device, and has always done so (in 4.X, 5.X versions), so I'm not sure why it you wouldn't have run into this previously. It does this so that it is updated whenever an alarm is triggered or a button is pressed for example. You can recreate the associations using ISY scenes and selecting the "association" option for the link if its supported between the Z-Wave devices. This is very similar to how we handle links for Insteon. There is currently no option to turn this off. You create an ISY scene, add the controller node as a controller to an ISY Scene, then add the target(s) as a responder(s) to the same scene. You then select "association" as the link type for each of the links. If a link supports on levels, and dimming durations it will show them as options for the link. Some devices allow you to send any command to another device, and in this case, it will give you the option to specify the command & parameters you want to send to the other device (minimote works this way).

All Thermostats supported by Isy (Insteon/Z-Wave/Zigbee) use 'ST' as the current temperature, hence the requirement for using 'ST' for Thermostats supported by node servers. Not sure of the quickest solution here. We have a "large" solution defined for all of this, but it won't be ready for some time. I think the simplest way to get around this for now is to allow the node servers to update the ISY Node Type directly. Maybe something like the following would make sense, where we could maintain a public list of specific node types for node server nodes. It doesn't need to be a complete list at all because most devices can just be undefined, but for those we need to know, they could be added to the list. e.g. Off the cuff possible node server node types of form <major>.<cat>.<subcat>.<level> 1.1.0.0 - Undefined (default) 2.x.x.x - Common Node Server Node Types 2.1.1.0 - Thermostat 2.1.2.0 - Temperature sensor ... 2.2.1.0 - Dimmer Switch 2.2.2.0 - Relay Switch ... What do you think?

Hi Steve, Whether searching for raw text, node, variable, programs, etc., the Find/Replace searches the contents of your programs, not the actual names of the programs. I'll add a feature request to the list to search for the actual program by its name rather than its content (i.e. find the program itself, not the set of programs that reference it).

Hi io_guy, You can use the SOAP command GetAllD2DStatus to get the status of all the programs at once (we use this in the Admin Console).

We had to add custom support for other FortrezZ devices, so its quite possible we'll have to do the same for the mimo2+

Hi Jimbo, If it happens again then use 'Undo Changes' to load the programs again and get the new key.

Hi Jimbo, If the command itself cannot be sent then it will return an error, but the only way to be sure the value is updated as expected is to query it afterwards because some devices just fail silently when processing the config command. I suppose we could add an optional "verify" parameter to the command that would cause us to automatically do a query after the set (its a low priority though).

Hi Gerry, I don't know why this would be happening, and why splitting into two programs seemingly fixes the problem. The conditional logic processing is the same code for both cases. Not that it should matter, but what are all the ways you updating the state variable? Do you have programs that run based on the status of your Humidifier Override Switch?

Hi, The additional users are only for Node Servers, and not for general use. They allow you to install a node server without having to give the node server full access to your ISY, instead, the node server only has access to certain REST API's that affect the nodes that it owns/controls.

Hi Teken, The teal color indicates that the folder does not have a true/false status (yet), but it does contain conditions. A plain folder icon indicates the folder has no conditions.

Yes, you can use an e-mail address as a username on the ISY

This is the direct link to the substitution variable page, Michel posted the page containing various related links, including this one. http://wiki.universal-devices.com/index.php?title=ISY-994i_Series:EMail_and_Networking_Substitution_Variables

Important User/Password changes - After installing build 5.0.8 or later from firmware 5.0.7 or earlier, your userid and password will be reset back to the system default. - If you restore a backup created prior to 5.0.8 your userid and password will be reset back to the system default. - If you downgrade to a version earlier than 5.0.8 after installing version 5.0.8 or greater, then after you downgrade to the earlier version, you will have to Factory Reset the ISY and optionally install a backup taken in that version or earlier (you do not have to factory reset the Z-Wave dongle). We'll document the full details of the rules prior to official release, but they are generally: Userid - 1 to 32 characters Password - 5 to 20 characters Cannot contain & :

If Step 5. fails then there is either something wrong with the communications between your PLM and the 2411T, or there is something wrong with devices themselves (defective or possibly wrong firmware level). Not that it helps you with your immediate problem, but we've tested this again this morning, and everything links correctly here. The firmware version of the 2411T we tested is v.4A