Techman

Some of the earlier generation LED bulbs incorporated a driver circuit which, in some instances, responded to fluctuations in the line voltage, thus the flicker. The newer generation led bulbs, especially some of the FEIT bulbs, no longer use driver circuits, just an LED element. Not only do they run cooler but they also weigh less as they don't require a heat sink.

Did you go through all the troubleshooting tips in the attached video? https://www.youtube.com/watch?v=NMx5yHTU2g4 Have you added any new electronics lately?

5.3.0 is incompatible with the 300 series Zwave board. If you're not sure which board you have take a look at the Zwave firmware version. If it's not 6.8.1 then you have the 300 series board and will need to update to the 500 series board.

5.3.0 does not support the 300 series board. For now you're OK to stay with 5.0.16C If you decide to add some Zwave devices later on then it's best to upgrade to the 500 series board and the 5.3.0 ISY firmware. For more information read the release notes for the various versions.

It's not unusual to end up with unexplained nodes. To clean up the device tree I created a folder and put all the unused nodes in it. I noticed that you have a pending write for ZW038, Right click on that node and then write updates.

The Zwave dongle does not support an external antenna, and has an effective range of about 25 feet depending on walls etc. To get the best coverage you should install a zwave repeater / extender such as this one within about 25 feet of your ISY. https://www.amazon.com/Aeotec-Range-Extender-Z-Wave-repeater/dp/B01M6CKJXC/ref=asc_df_B01M6CKJXC/?tag=hyprod-20&linkCode=df0&hvadid=167135357001&hvpos=&hvnetw=g&hvrand=4740950404248099910&hvpone=&hvptwo=&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9030974&hvtargid=pla-343932047164&psc=1

Yes, 5.3.0 is the final official release. Read the release notes before you update.

The 300 series zwave dongle is not compatible with ISY 5.3.0 firmware. . You'll need to purchase and install the 500 series dongle You can buy it here: https://www.universal-devices.com/product/z-wave-module/

What's your ISY firmware and UI version? Do you have the 300 or the 500 series Zwave board in your ISY?

Unlikely you were compromised. Try rebooting the ISY. It appears that the ISY reverted to the default email configuration rather than your own email server. If the reboot doesn't help then remove power from the ISY and then remove and reseat the SD card.

thank you

I don't yet have a portal account. When I try to log into the temporary portal option using my admin console credentials It's rejected.

Never received the notice. Is there a replacement other than the node server?

When I log into the admin console I get the following message. Has the climate module been discontinued or is a bug that's related to the earlier firmware version 4.8.0 I've been running 5.0.16C for quite a while.

It's probably best to use two programs Program 1 If light is off and door is opened and time is xxx then turn light on -------------------------------- Program 2 If light if on and door is opened then turn light off

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