Techman

Yes, If Time is between sunset and 11 pm same day then turn on light Else turn off light

What Zwave dongle are you using the 300 or 500 series. If you're using the 500 series do you know if it supports over the air firmware updates for the sensor?

Apparently in 5.0.16B the heartbeat node signal is being interpreted as an open signal by the ISY. UDI is aware of this problem and it will be corrected in the next ISY firmware update which should be in a couple of weeks. Currently there's no workaround. What is the model and firmware version of your sensors?

Same problem using Internet Explorer and Microsoft Edge

Yes

It's most likely failing. If your PLM is more than 2 years old it's probably time to replace it. The current version of the PLM has updated hardware and firmware including an updated RS232 interface What's the firmware and date code on your PLM

As are mine. I've been able to track down the cause of the false on. The heartbeat node signal is being interpreted as an ON status in 5.0.16B. It's strange that your sensors are not affected.

What's the firmware version of your 2421 sensors?

UPDATED: my problem is with the 2421 sensor. I previously said it was the 2843 I replaced my open/close sensor with a new unit yesterday thinking that my existing unit was defective and I just got a false on signal again with the replacement device.. The open node shows on, the closed node shows off and the heartbeat status shows on. The doors is physically closed. If I open then close the door the sensor then displays the correct state There seems to be an intermittent issue with 5.0.16B and the 2421 v.43 sensor.

UPDATED: my problem is with the 2421 sensor. I previously said it was the 2843 I've had the 2421 v.43 open/close sensor recently trigger a couple of times. The ISY status will show the sensor as open when it's actually closed. I also tried doing a factory reset and replacing the battery. In my case it has only happened a couple of times and that was several days ago. No false outs since then. I've since replaced the sensor as a precautionary measure. I'm also running 5.0.16B You might try replacing your battery

The status window in the admin console will be blank until the device sends a status change for that node.

There is an issue in 5.0.16A with the leak sensors not being recognized by the ISY. This will be corrected with release of 5.0.16B which is due out this week.

Did you try using both the user name and password as admin (lowercase)?

It should work in the latest firmware release 5.0.16A Which ISY firmware version are you using

Be sure to follow the directions, especially "Do not open ‘Programs’ tab until step 2)" Everything should go smoothly. ------------------------------------------- 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.

Hi Chris Thank you. It would be great that if in your "spare time" both the Substitution Variables and the Error Code list in the Wiki could be updated. The only place I didn't look was in the developers section.

You're correct. No interaction is required.

What is the correct variable syntax to use in an email to display the LUMENS from an Aeotec Multisensor 6

An update, 5.0.16B, is supposed to come out next week and contain the fix for the leak sensors

Do you have an ETA on a fix?

Hi Chris, I'm running 5.0.16A. All my leak sensors have also failed. No device status is shown in the admin console. Heartbeat, wet, or dry not recognized in the ISY status windows. Attached is a print out from one of the sensors

Take a look at this troubleshooting link https://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Z-Wave_Communications_Errors The Aeotec Gen 5 recessed door sensors have been tested by Aeotec and confirmed that they are compatible with the ISY. You'll probably have to put them in the linking mode then do a Zwave heal.

If the 2441ZTH is running on batteries then there is no way to query it as battery operated devices go into a sleep state when not active to preserve battery life. They send out a temperature report when the temperature changes 2 degrees. What you can do is attach a dc power supply to it. In that case the thermostat will stay awake.

It's important to replace like for like, i.e. an 8 button with an 8 button. You can physically remove the old keypad, then install and link the new keypad in its place. The old keypad will still show in the admin console, just right click on the old keypad and click on replace with - click on the new keypad (which will show up in you device list with its address) After the ISY completes the replace procedure the admin console will shut down. When you open up the admin console the new keypad will have replaced the old one.

After you run your diagnostics you might want to do a factory reset on the KPL then a restore device. What is the firmware version of the KPL ( it will display in the admin console ) I have a large number of KPLs installed and occasionally have issues with their non-volatile memory becoming corrupted, especially with the older firmware versions. I've only noticed this with the KPLs and not with any other Insteon devices.