upgrade to new 1.7.583

Since the upgrade 3 days ago, my scenes no longer show “next run”. My lights turn on but not off.

yea… thanks. I read this post and checked my vera. The lights work fine however my scenes exhibit the same issue. No “next run” time. Gosh…and I thought I made it through this upgrade unscathed.

You guys should report them by opening a ticket. I am a bit exhasperated by the last two releases myself…

I did already open a ticket. Problem seems to be that the issue is randomized. Sometimes it works, sometimes it doesn’t. :frowning:

I applied this firmware update today and it bricked my Edge. Awesome. Pretty much what I expect at this point.

Unfortunately I rely on my vera a bit too much to afford such disasters and continue testing. I ended up downgrading. Hope they sort all of these problems out. I am not sure what they did to mess everything up. The last stable release for me was 7.0.5. After that they only fixed cosmetic items (units, icons) and broke a lot of fundamental zwave items, like scene assignments, behaviors, user associations. Heck even downgrading to 7.0.5 fixed an association problem between a leviton scene controller and a leviton switch which I thought was a Leviton problem when I set it up on 7.0.6.

Sorry, I should have mentioned that I had done this in my original post. I have opened a ticket.

Every upgrade has something that goes bump

I am set to finish a small cabin for vacations. My experience with Vera has me looking elsewhere. I want vera to be the option I go with but find myself wondering if there is something more stable in the same cost bracket. Looking at smartthings…just not sure which direction I should go. I apologize for the slight hijack.

Update

The Service noticed me that they did “some work” on my Vera and that it should work now. - It didn’t. The device hung. I needed to restart Vera and all devices, scenes, settings were vanished. >:(

I restored a backup and my device was back.

My original problem still isn’t fixed. Meanwhile I found out that only commands that are delayed by 20 minutes or more in a scene are not always executed. The problem is significant because it happens to every second or third command.