lilyoyo1

I don't know what you backed up so I can't say. Whichever had the last working configuration

After restore Plm do restore devices. Ensure your firmware and ui matches

He posted the directions because many times people will replace their Plm saying they did it properly.....turns out they didn't. Does the Plm that shows in the isy match the Plm you are using? What were your steps in exact order? Firmware and UI?

Its not a mesh issue. I have about 30 zwave devices in my home. Different sensors and outlets that are in the same area work perfectly everytime. It's an issue that started with 5.3 and got worse with 5.3.1. Go back to 5.0.16 it works great again. It's also an issue in other homes that I use for testing as well. 5.0 16 works fine, 5.3.1 doesn't at all. All other devices are great otherwise... Just locks

Ive had nothing but problems with 5.3.1 and yale locks. I don't know what's changed but communication sucks. It was bad with 5.3 and only got worse. Hopefully @Michel Kohanimand Udi can get it back to where it used to be

As always, clear your Java cache after an update and use the launcher from the update download page

Does your UI match your firmware

Philips has a warm glow version as well. https://www.amazon.com/dp/B017RX1JES/ref=cm_sw_r_cp_apa_fabc_SUKbGb263JRJ2

I use warm glows as well in all my homes without issue. They dim lowest of any led bulb I've tested over the years and I like the way they become warmer. Obviously it's far from being like an incandescent bulb but the effect makes them much more enjoyable than standard led bulbs when you dim them. I have found their b12 bulbs that looks like a crown inside works better than the other style. Other than that, they've been spot on across the line in regards to performance

That wouldn't help. They know people want them and they want them in stock. Just having a hard time with it.

You aren't the only one in need. Posting on a forum is a bad place for technical support. The time it takes going back and forth (along with dealing with a multitude of other stuff) is time consuming. A forum is good for quick support but when undivided attention is required, yes you need to call it in. By using the proper support channels, UDI can keep track of issues and possible fixes. They also can take the necessary time to get you where you want to be. It's akin to having a complicated conversation over the phone or via text. If you pick up the phone and call, you can accomplish in 10 minutes what it may take an hour to do if you text

The forum is not the place to go to UDI for help. That's why they have a support page to submit a ticket. This is a peer to peer forum. The place to go for your peers to help. While UDI does chime in from time to time, help from them on here is not a guarantee.

Ge devices work great with the ISY. How close was it to your ISY? Does your firmware and UI match?

5.0 and 4.0 are different firmwares. By using a UI for 4.0 branch, there will be conflicts. While, your switch may be having other problems, the mismatch will add to the problem as well

As always, your firmware and ui has to match. Clear your Java cache and use the launcher

It works for us, because I don't want the lights cycling on/off and there's no delay in reporting. If it happens to get too dark, the delay is overridden

I guess we have our answer

Did you read the Instructions on the download page prior to upgrading and follow them correctly? I'm order to go right, you must be methodical with the upgrade as well as use the launcher

It would be easier to help if you'd provide more info. A switch could be anything from any company as could whatever it's attached to and other devices. The more detail you give the better the response.

On the very first page of this subforum.

you need to create a separate scene and configure the devices to be what you want in it. Then control the scene itself not the individual device

Mine adjust when the light falls below a certain point. it doesnt trigger right away but waits about 10 minutes as it could be a passing cloud that makes temporarily dark. The same for turning off. A temporary moment of "enough light" will not trigger it to turn off.

MS's are great for a lot of things. I use zwave and Insteon sensors. Speed has never been an issue even though i use programs for everything. I have them hidden to turn the underbed lights on late night. Late night, they will turn lights on to a very dim level just enough so you can see. If you need more light, you can hit the switch which will turn them on to 50% if you need more but not full on (unless you double tap) I also use my sensors to turn lights and stuff off in rooms/areas that are unoccupied. For example, if no motion is sensed on my patio for an hr and the tv or music is on, itll automatically shut everything down. This only happens at night as we could potentially be in the yard away from the sensor during the day. My zwave MS's have lux sensors built in. I use this to adjust lighting in occupied rooms vs using only sunset +/- to trigger stuff. On a cloudy or rainy day, those options do not work well which can leave you sitting in the dark or needing to physically turn on the lights (whether its remotely or by touch). By looking at the amount of light in the room, the lights will turn on by themselves. Sometimes it

If its only the ISY changing the lights in a scene, then using multiple scenes instead of adjust makes perfect sense. If you want to change how the lights work at the switch manually, then you would want to use adjust scene. For example, my front porch and garage lights dim to 40% after 11. If motion is sensed, it'll turn full on and then go back to 40%. I just use multiple scenes for this with everything in them as responders. With my livingroom lights, I use adjust scenes. If you manually turn on the lights from any of the switches during the day/evening, they turn on 100%. Late night, they'll only turn on 50%.

Nothing's changed. What were the steps that you took?