I was running 1.0.979 for some time with decent results. When I saw the announcement of 1.0.987 yesterday I updated to that version. I have rebooted Vera multiple times including unplugging and waiting. Regardless, it seems like Vera cannot communicate to the dongle. The dashboard just sits with “ZWave: Configuring Z-Wave” indefinitely (well, at least for a few hours).
Anyone else have success with 1.0.987?
\pat
I upgraded from 1.0.985 → .987 last night and have not seen any problems. The rebooting issue also seems to have be resolved.
Unfortunately, I’m seeing the same thing with 1.0.987. “ZWave: Configuring Z-Wave” indefinitely
When I look at the log it is continuously repeating the Init successful cycle
I went ahead and upgraded to 1.1.228 which did solve the problem but… I’d rather use UI2. If anyone knows how to fix the 1.0.987 problem, please post here.
Something fairly similar, filed trouble ticket #1888 with Verbose logging and activations of some of the devices.
In some cases, pressing on/off (Appliance module) would activate the device, but would not be reflected in the UI. In other cases it would do nothing.
In one case, it rebooted Vera, I upgraded 5 hours ago, and this was the first reboot. That occurred after trying to turn on/off my Appliance Module via the HTML UI.
I’m in the same boat as mdconnelly. I could not get past the Configuring Z-wave with 987 so I upgraded it back to UI3 which works. I just received my Vera2 yesterday.
I needed to have Vera back working so I rolled back to 1.0.979 and things are fine again. That makes me suspicious of the 1.0.987 update since I did not have to do anything special to get Z-Wave back with 1.0.979.
\pat
I experienced the same issue upgrading from 1.0.979 to 1.0.987. “Configuring Z-WAVE” just kept spinning and I could not control any of my devices from the dashboard. After reading these posts, I also downgraded back to 1.0.979 and everything is back in working order. Thanks to others in this forum that posted this issue, I did not waste hours trying to determine why the upgrade did not work.
Same problem here. I still don’t know why these updates are being released to everyone without testing properly. 979 has been very good and stable so I don’t know why MCV is screwing it up so bad. Both .985 and now .987 have had big issues.
They’re looking at mine right now. Folks who are experiencing problems may want to submit tickets also (with Verbose logging, and the Support-Code) just in case there are different issues going on.
Extra data points can never hurt.
Mine seems to be related to the UI layer not “updating” after the ZWave event is sent out, and I don’t have the spinning “Configuring ZWave” message going on.
The problem is I don’t have time to just leave the bad firmware on and have it not working until they have time to get around to looking at it. I just get it working again by reverting. They (MCV) should be testing these things out with all the possible devices and make sure they work for at least a few days before releasing it to us. This just seems to be happening over and over and over. Or they can give me an extra Vera for free with a few things thrown in and I’ll test it for them. If they just did that with a few people it would help a lot. I have two already so it’s buy two get one free.
My own problems:
I had no issues that I could see with 985. I updated to 987 and I lost use of my handheld controllers. My web pages would also not show accurate status for each device (temperatures frozen on thermostat, light showing as on when it was turned off – all even after refreshing, and “repairing” the network).
I too can’t wait days for MCV to check out the problem when I have my wife complaining her heater button doesn’t work on her remote. I too reverted back to 985 and it seems to be stable for me (and the problems with 987 gone), but have identified my back up for 979, just in case I need to factory reset and reload.
Using UI3 is not an option for me, as I’m eagerly awaiting the release of Apple iPad, for a truly “Flash-less” experience.
I’m really sorry about the problems with 985/987. 979 remains our last official stable UI2 release, but we needed to rush through an unscheduled UI2 build (985) for the Square Connect iPhone app beta testers who didn’t want to use UI3. It was unexpected because we were expecting all of them to use the official UI3 release. Anyway, we discovered this morning a small issue in the .987 build preventing the UI from updating, which was caused by a small API change that was written for Square Connect for UI3 which hadn’t been tested with the UI2. I will ask our testers to test this 988 build on Monday, but, in the meantime, it’s been reported that it solves the issue: [url=http://download.controlmyhouse.net/betafirmware/ftp/wl500gP_Luup_ui2-1.0.988-1.trx]http://download.controlmyhouse.net/betafirmware/ftp/wl500gP_Luup_ui2-1.0.988-1.trx[/url]
I have an unrelated problem that I have sent to tech support 3 times over three weeks and though I recived a message after a couple weeks that it would be forwarded to someone to look at I’ve heard nothing yet, how long are we supposed to leave things alone without correcting so tech support can see them?
Paul, Your issue with HSM100 sensor reliability is on my desk. The problem we’ve got is this isn’t a problem with Vera – it’s the other devices – and debugging this sort of stuff is very, very hard – you’d need a ZWave Zniffer, and those are only available to registered ZWave engineers. Understand, Vera just talks to the ZWave chip using the ZWave Serial API. We don’t have the ability to tell it what neighbors there are, how to discover them, etc. All that logic is provided by Sigma (who makes the chip) and is built into the chip. In verbose logging mode, Vera records every bit of data that is exchanged between Vera and the ZWave chip in your dongle. So, in your case, when we send the dongle a message “How many neighbors does node 4 have?” and the chip responds “1”, there’s nothing Vera can do to figure out why that node is only reporting 1 neighbor and doesn’t see the other nodes. Vera only knows what goes on between Vera and the ZWave chip, and has no control over what goes on between 2 ZWave chips. A ZWave Zniffer is a special dongle which monitors all ZWave traffic and logs everything, so you can debug what’s going on between chips. But there are 2 problems: 1) Sigma doesn’t want end-users to have this device since it would allow a hacker to take over a zwave network, and 2) We’d have to pull our low-level ZWave coder (me) off all development for probably 1 week to work on resolving this, which we’d happily do if it were a bug in Vera, but is difficult to justify since it seems to be a bug either in the chip or in the HSM100, so, either way, we’d allocate a week’s worth of resources to identify the problem, but wouldn’t be able to fix it regardless since it’s not in our code–we’d only be able to pass the info on to either Sigma or Express Controls and hope they could fix the problem.
I’ve asked Sigma for a way to send customers Zniffers since you’re obviously not the first one having such issues. I’ll bring it up again on Monday and try to escalate finding a solution.
Your reply, and your effort to address the problem, is greatly appreciated, it is crucial for folks struggling with issues to have at least this sort of intermediate response so as not to feel ignored, and makes it much easier to live with the ambiguities of those devices that don’t “just work”. I will cut you some slack as my request happened to coincide with (I would imagine) an unusually high volume of tech support problems, I chose Vera because I believed it was the product closest to filling the promise of cost effective home automation, and still believe it is so, mostly (technical frustrations aside) I am quite happy with the product and like many here I am rooting for MCV’s success, I applaud all efforts to improve problem resolution and perhaps most importantly communication, keep up the good fight, and again Thanks
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules