V4.9 is the current official release in the version 4 branch. 

Version 4 was superseded by Version 5 firmware, which was beta for a long time.

in the v5 branch 5.3.4 is the latest and greatest.  It is labeled test build and not official release (without looking it up I think 5.1 is labeled “official”). 5.3.4 is what you should be using before you point fingers about long time bugs not being fixed.  

(in version 5 to be labeled “official” a firmware must go thru the Z-wave certification process which costs UDI a significant amount, that’s the only thing holding back all v5 release after 5.1 from being labeled “official”.)

The version you’re using 5.0.14 is a beta version released October 2018.  Yes it has lots of bugs.  

Your Z-wave version 6.81.00 tells us you have a series 500 Z-wave board, so move right up to 5.3.4.

48 minutes ago, MrBill said:

V4.9 is the current official release in the version 4 branch. 

Version 4 was superseded by Version 5 firmware, which was beta for a long time.

in the v5 branch 5.3.4 is the latest and greatest.  It is labeled test build and not official release (without looking it up I think 5.1 is labeled “official”). 5.3.4 is what you should be using before you point fingers about long time bugs not being fixed.  

(in version 5 to be labeled “official” a firmware must go thru the Z-wave certification process which costs UDI a significant amount, that’s the only thing holding back all v5 release after 5.1 from being labeled “official”.)

The version you’re using 5.0.14 is a beta version released October 2018.  Yes it has lots of bugs.  

Your Z-wave version 6.81.00 tells us you have a series 500 Z-wave board, so move right up to 5.3.4.

Exactly why it's important to provide information on the forums vs assuming things are simply bugs

6 hours ago, MrBill said:

V4.9 is the current official release in the version 4 branch. 

Version 4 was superseded by Version 5 firmware, which was beta for a long time.

in the v5 branch 5.3.4 is the latest and greatest.  It is labeled test build and not official release (without looking it up I think 5.1 is labeled “official”). 5.3.4 is what you should be using before you point fingers about long time bugs not being fixed.  

(in version 5 to be labeled “official” a firmware must go thru the Z-wave certification process which costs UDI a significant amount, that’s the only thing holding back all v5 release after 5.1 from being labeled “official”.)

The version you’re using 5.0.14 is a beta version released October 2018.  Yes it has lots of bugs.  

Your Z-wave version 6.81.00 tells us you have a series 500 Z-wave board, so move right up to 5.3.4.

I get where you're coming from. I did make an attempt to see if this issue had been resolved before making a single post. The two threads on it were closed resulting in:

• Those who'd previously posted about the issue not being able to report to the existing threads that a newer update fixed the problem. They would be unlikely to start a new thread just to report something had been fixed.
• Those who go searching for the problem previously reported can't post in the existing threads asking if the issue was ever resolved which would result in those who are already following the thread and had the issue fixed being able to reply as such if they hadn't already. 

18 hours ago, sorka said:

Those who'd previously posted about the issue not being able to report to the existing threads that a newer update fixed the problem. They would be unlikely to start a new thread just to report something had been fixed.

Closing old threads is a very new procedure in this forum.  In the past there were many threads that someone wouldn't even read the whole thread and tack a "me too" post on to the end of it.  98% of the time it wasn't the same thing that started the thread but just something that sounded close even if it was 5 years ago and completely unrelated to the new issue.

Only in the past few months have the old threads started getting closed, arbitrarily and purely by date of last post.  The purpose is to force people to start new threads and state there problem.  If they don't give the version they are using that should always be one of the first questions asked, for cases just like yours, where the issue was likely fixed since 5.0.14.

Another thing that the closure and unpinning of old threads seems to be helping is that users are no longer upgrading to weird versions.  Some get the idea somehow they they should install something like 5.0.2 to get used to 5 before they jump to the latest and greatest... the bottom line is there is no reason to install 5 year old beta firmware that's full of bugs.  There's only two version of 5 that people should be installing today... 5.0.16C if they have a 300 series z-wave board, or 5.3.4 if they have a 500 series z-wave board... all others versions of the 5.x branch should be considered exactly what they are... buggy beta versions.

Edited November 14, 20213 yr by MrBill

7 minutes ago, MrBill said:

Closing old threads is a very new procedure in this forum.  In the past there were many threads that someone wouldn't even read the whole thread and tack a "me too" post on to the end of it.  98% of the time it wasn't the same thing that started the thread but just something that sounded close even if it was 5 years ago and completely unrelated to the new issue.

Only in the past few months have the old threads started getting closed, arbitrarily and purely by date of last post.  The purpose is to force people to start new threads and state there problem.  If they don't give the version they are using that should always be one of the first questions asked, for cases just like yours, were the issue was likely fixed since 5.0.14.

Another thing that the closure and unpinning of old threads seems to be helping is that users are no longer upgrading to weird versions.  Some get the idea somehow they they should install something like 5.0.2 to get used to 5 before they jump to the latest and greatest... the bottom line is there is no reason to install 5 year old beta firmware that's full of bugs.  There's only two version of 5 that people should be installing today... 5.0.16C if they have a 300 series z-wave board, or 5.3.4 if they have a 500 series z-wave board... all others versions of the 5.x branch should be considered exactly what they are... buggy beta versions.

 

This is an awful practice. It eliminates context and previous lessons learned. It also keeps those who have awareness of the issues being informed when something new related to it is posted since they are not following the new threads already. 

I totally agree that closing out threads that get off track is an occasional ok practice when it doesn't lock out awareness of valuable trouble shooting.

By closing these threads, folks who've had their problem solved can't post in the existing threads so it looks like the problem was never solved...as in this case. 

I did post links to the previous threads, but I was already so irritated by them being closed and preventing awareness of this issue already being solved, that it basically turned into a rant from me. 

Also, I didn't upgrade to a weird version. I updated to the version every said I should 3 years ago and haven't gotten a prompt in the UI since to upgrade that version to something newer. Prior to 5.0.14, I'd occasionally get prompted to update the firmware which I would do. Did upgrading to 5.0.14 eliminate that because I was on some funky version?

Edited November 13, 20213 yr by sorka

10 minutes ago, sorka said:

Also, I didn't upgrade to a weird version. I updated to the version every said I should 3 years ago and haven't gotten a prompt in the UI since to upgrade that version to something newer. Prior to 5.0.14, I'd occasionally get prompted to update the firmware which I would do. Did upgrading to 5.0.14 eliminate that because I was on some funky version?

The version 4 branch is the only place you get prompts to update.  That wasn't a part of V5 initially because everything was alpha, then beta... A year ago V5 had its first and only Official release.  It's been posted by UDI that any version they want to have go through the Z-wave certification process costs them around $10K each.  As such there is one officially certified version, after it are several more "test builds" but unlike early beta's like 5.0.14 these last few test builds after the official v5 release just have a few bugs quashed and are very stable releases.

In version 5, the user must watch the forum for new versions and update manually accordingly.  I wish that UDI would bring back the update flag in the UI in version 5, but for the time being it's been posted that they can't because of the z-wave certification process.

Only venturing into "ISY running on Polisy" hardware are there experimental alpha/beta releases.

Again I completely support letting old threads die, any thread that still has outstanding issues will be current and NOT get closed, only those that have died because they haven't been important for months will get closed... and they are NOT being removed, the information is still there for research purposes.

@all,

Closing old topics helps with support issues. Some, just point to a post from 10 years ago and expect us to read through everything.

With kind regards,
Michel

26 minutes ago, Michel Kohanim said:

@all,

Closing old topics helps with support issues. Some, just point to a post from 10 years ago and expect us to read through everything.

With kind regards,
Michel

You mean like what I did in the first post? How's that working out? Had they not been closed I wouldn't have done what you claimed closing the topics fixes.

9 hours ago, sorka said:

You mean like what I did in the first post? How's that working out? Had they not been closed I wouldn't have done what you claimed closing the topics fixes.

Please stop making mountains out of molehills. Yes, closing old threads worked out the way they intended. You did make a new post didnt you? Unfortunately, you chose to act entitled and ranted and raved instead of simply posting your issue and asking for help solving it. The same wouldve happened had the old threads still been up. The difference is that UDI and everyone else wouldve needed to go through all of the posts.

Those posts were 1 and 3 years old. If the authors were going to update them, they would have done so by now since they've been open until recently. Not only that, if they were still perusing these forums recently, they could have chimed in on your posts giving you an update (which they did not), which means they either aren't on here or didn't care enough to update you.

Either way, whether it was on this post or an old post, you would've been in the same boat.

Most people don't update their posts when something gets fixed or works out for them. Using one of your old posts for example, UDI, added what you asked for when it comes to notifications and you didn't bother to go back to it with an update. 

You were using 3 year old software, ranted about a bug and when I tried to help you, you refused the help. Had you simply put your pride aside and asked for help or responded to my request, i would have given you the needed information a long time ago. Unfortunately you chose a different path and now you're still here doing the same. You're the one stuck with issues but instead of setting pride aside, calming down and asking for help, you double down which lessens the chance of anyone bothering to help you now and in the future

Edited November 14, 20213 yr by lilyoyo1

4 hours ago, lilyoyo1 said:

The same wouldve happened had the old threads still been up. The difference is that UDI and everyone else wouldve needed to go through all of the posts.

False. Had the the old thread been up still I simply would have ask "was this ever solved for anyone"? . If no answers, I would have started a new thread posted all the details as if it had never been asked. But that's NOT what would have happened. Every member in this forum who posted this issue has already had it solved and one of them would have replied. 

 

 

Since this thread is now completely off topic, I've asked the mod to either retitle and move it or split it.

1 hour ago, sorka said:

False. Had the the old thread been up still I simply would have ask "was this ever solved for anyone"? . If no answers, I would have started a new thread posted all the details as if it had never been asked. But that's NOT what would have happened. Every member in this forum who posted this issue has already had it solved and one of them would have replied. 

 

 

I highly doubt that someone would have commented being that Kush (original author from your 1 year old post) hasnt been on here since July and jca001 has been on but didnt even bother replying on here, you probably would not have gotten a response.

Had your approach been much different, I wouldve given you the answers from the start. YOU chose to be difficult and act entitled which is why you had to go through all of what you went through over the last few days.

Think what you want. You are the one with issues. You were the problem every step of the way. Those willing to help you have working systems and the knowledge you lack. This is all on you and you alone.

Edited November 14, 20213 yr by lilyoyo1

7 minutes ago, lilyoyo1 said:

I highly doubt that someone would have commented being that Kush (original author from your 1 year old post) hasnt been on here since July and jca001 has been on but didnt even bother replying on here, you probably would not have gotten a response.

Had your approach been much different, I wouldve given you the answers from the start. YOU chose to be difficult and act entitled which is why you had to go through all of what you went through over the last few days.

Think what you want. You are the one with issues. You were the problem every step of the way. Those willing to help you have working systems and the knowledge you lack. This is all on you and you alone.

Given that this thread solved my issue in about an hour, I think it worked out for me just fine ?

16 minutes ago, sorka said:

Given that this thread solved my issue in about an hour, I think it worked out for me just fine ?

Given that you've had additional posts about other stuff and were still posting the next night about other issues (including on this thread) that cropped up, I doubt it solved it in an hour. And if it did...then closing old threads accomplished exactly what it was intended to do.

Edited November 14, 20213 yr by lilyoyo1

1 hour ago, lilyoyo1 said:

Given that you've had additional posts about other stuff and were still posting the next night about other issues (including on this thread) that cropped up, I doubt it solved it in an hour. And if it did...then closing old threads accomplished exactly what it was intended to do.

Actually just one new issue also solved and it was the same night, not the "next" night. My thanks to @techman in this thread for solving the 1011 issue. The other one I solved myself. The Leviton plug I bought does not support reporting its status. I'm not willing to use the hail program work around. I have multiple additional brands coming in the next few days and will report in the other thread which ones do and don't report their status. 

44 minutes ago, sorka said:

in the next few days and will report in the other thread which ones do and don't report their status. 

In principle all Zwave Plus devices should report status.

15 minutes ago, asbril said:

In principle all Zwave Plus devices should report status.

Newer devices (zwave plus) do report status for the most part. Whether it can be used as a controller is a different story

2 hours ago, sorka said:

Actually just one new issue also solved and it was the same night, not the "next" night. My thanks to @techman in this thread for solving the 1011 issue. The other one I solved myself. The Leviton plug I bought does not support reporting its status. I'm not willing to use the hail program work around. I have multiple additional brands coming in the next few days and will report in the other thread which ones do and don't report their status. 

You never answered my question as to the UI version your running. In the admin console click on help | about and let me know what it shows.  Having the incorrect UI will cause unpredictable problems.

You may want to take a look at the Aeotec Zwave devices. They've been tested with the ISY994 and the manufacturer issues firmware updates in the event of a bug.