I have asked several times for these to be included, but hueemulation and zwave were never added to the official list. These are regressions since 2.5M1 and should be fixed before 2.5M2.
I don’t use mqtt enough to know if the open issues are critical. There’s also a new one for zigbee devices being marked as offline after the bump to 1.2.1, but I expect that will be fixed very quickly.
I just want to add a couple comment here and take this first comment’s worth for what you paid for it
I ‘think’ Chris has a running IDE (finally, although not with out ongoing issues) and is currently pushing snapshots and addressing all recent zwave issues. The heal issue is maybe not a regression, just a recently uncovered shortcoming. Disabling nightly heal is a work around IF and ONLY IF nightly heal is causing issues. Otherwise I again ‘think’ zwave is in good shape but Scott if you know otherwise please feel free to correct me. Anyhow, Chris is on holiday and he may chime in but the guy deserves a break
David does seem to have abandoned hueemulation and it has outstanding issues. if interested see this post
I’ve reopened #1178, since I had incorrectly thought that #1195 was related and would address the issue.
What I’m experiencing appears to be the same as what is described by @digitaldanhere. I’ve also seen posts in the forum that seemed as though they could also be related.
If 2.5M2 is released on Wed with things still broken, anybody…
using zwave should disable the daily heal, which can lead to routing issues not getting fixed,
using zigbee should expect their devices to randomly drop offline,
using using hueemulation should remove it (before upgrading!) and use the jar from 2.5M1 (which also has issues) or find a jar from before 2.4 (which is what I’ve done)
There is no set number of releases. We will have milestone 2.x releases until we are ready to introduce breaking changes to the APIs at which point we will move to a 3.0 releases. If we follow the same process as we did for 2.0, there will be an extended period of alpha and beta testing before there is a full release of a 3.0.
A little late to the game, but this seems to be a regression issue. Just filed the bug a few minutes ago.
The Neeo binding/IO works with no issues on M1. It will not load properly on the M2 nightly. The only way I can get this working properly is to extract the two .jar files from the M1 addons, wait until OH is fully started, and then put them into the addons folder. At that point everything seems to work as normal.
For zwave, @chris decided that it should not be considered blocking for M2.
Can anyone comment on hueemulation? I see that @cweitkamp did a few fixes these days - do we have to deal with anything further or could we still plan M2 for tomorrow?
I would be surprised if he feels the same about 1178. Please review this comment. It would be great if @digitaldan could test again to see if he is still experiencing this too.
To summarize the issue, after a daily heal kicks off on a snapshot build of OH, the zwave network response is very slow and devices drop offline. The only remedy I’ve found is to restart OH and disable the daily heal.
This may also be one to get cleaned up… [basic] Frame visibility in sitemap ignored until refresh github. There was a related issue in Android, but that should be resolved in the next build.