Techman

I noticed that after setting the backlight for a device and then exiting the admin console, the backlight setting reverts to 0/0 next time I open the admin console even though the updated setting is saved in the device. Will this be corrected in a future release?

Did you put the sensor into the linking mode before you tried to update it? What version of the ISY firmware and UI are you running?

You should have the motor control nodes in 5.0.16C. Try doing Zwave network heal. If that doesn't work then you may have to remove and reinstall the ZRTSI

I'm using Somfy with ZRTSI and the only option you need to use is the Motor Control node. The mulstilevel switch node does correctly display in 5.0.16C. However I'm having issues with the Aeotec Smart Switch 6. The ISY sometimes incorrectly displays its status, and a device query doesn't seem to correct the displayed status. I'm curious if anyone else is seeing this problem.

Disable your firewall and then try the update. Let me know if that works.

The 6 button and 8 button keypads are basically one of the same. Their firmware can be reconfigured for a 6 to appear as an 8 and visa versa. Smarthome has, or had, button kits available to change one for the other. If you had first reconfigured the keypad to a 6 button then done a "replace with" it would have been a seamless replacement.

When you do a "replace with" it must be like for like. You'll probably have to uninstall it then reinstall it as a new 8 button keypad.

It's possible that the device's memory got corrupted. Do a factory reset on the device then a restore device.

Was you "A" button in your scene added as a controller? If not then remove it from the scene and then re-add as a controller

I don't believe so, but I'm not sure. What happened is that I had an on/off module that I hadn't assigned a unique name to so it displayed only it's Insteon address. The module appeared at the top of my device list. Later in the day I noticed one of several programs weren't functioning. When I took look at the programs I noticed that an IOLinc had been replaced by the on/off module. I have a large number of programs and haven't checked them all but so far this seems to be isolated to one set of programs that were controlled by the IOLinc

All my 2843 sensors are now working correctly after updating to 5.0.16C

PROBLEMS with 5.0.16C after upgrade 1. Upon opening admin console I got an Zwave error message showing an Insteon address. I have no idea what the message is referring to. 2. On several of my programs an Insteon address was replaced by another Insteon address ( IOLinc was replaced with an ON/OFF module address)

You're correct, but you can put "From ISY" in the subject line.

On what type of device do you want to receive your notifications on? SMS is push, therefore faster than non push email. Not sure about Poly

The old Zwave dongle used the 300 series chip, the newer dongle uses the 500 series chip. Take a look at this link for more info.. https://aeotec.com/z-wave-500-series-module-chip/

5.0.16B fully supports the motion sensor II. However there are a few minor bugs, one affecting the open/close sensor. All in all it's a stable release. Be sure to follow the update instructions.

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.