Page 1 of 1
Posted: 19 Dec 2016 05:51
Noticed this build (dated Dec.12th) today when checking to see if a build was released that addressed the issue of having to re-interview a device that just stops responding to commands.
Anyone know anything about this build ?
Posted: 19 Dec 2016 10:43
Only use release candidates if advised by the developers. In general users should definitely stay away from releases that have a "funny" part in the name like this one
Posted: 23 Dec 2016 00:22
I certainly agree with avoiding RC versions, I was just curious if perhaps anyone knew anything about this build. I'm seriously upset (selected nice word) about having to re-interview specific devices in order to get them actively participating again. I'd settle for any fix if one existed but no one has identified why this even occurs. It's not predictable, it can occur in an hour, a day, a week or weeks but when it happens. BAM !
Posted: 05 Jan 2017 05:36
I'm having the same problem
Posted: 06 Jan 2017 19:43
Please do not use our intermediate commits. We use them to exchange between us different development versions. Certainly not a good idea to play with unless you want to become upset.