Two requests

[mike]

Two requests, one is a feature request. The other will help the community.

1. Community Request: When updating the platform where it breaks some currently working features - such as the Xiaomi sensors, or where there is a significant likelihood of breaking something, can we please have some advance notice. There are already people wanting to roll back until some of these features are fixed.

2. Feature Request: When updating or creating a device driver, any coding errors cause the text of the device driver to be removed from the page, and an error pops us. Previously, the driver text remained on screen for editing, along with the errors. Makes it difficult to debug when this occurs.

[bertabcd1234]

@mike

When updating the platform where it breaks some currently working features - such as the Xiaomi sensors, or where there is a significant likelihood of breaking something, can we please have some advance notice.

You mean like this notice towards the beginning of the release notes for 2.0.5 that you surely read before applying the optional update whose installation you are in total control of to your hub?

@bravenel

please note this update will create some temporary issues for Xiaomi sensors,

(It was also mentioned well before release in the Xiaomi driver thread by author, who was contacted by Hubitat staff during beta testing of 2.0.5 after your friendly neighborhood tester[s] discovered the issue.) That being said, if you haven't applied two or more hotfixes in 2.0.5 yet, a 2.0.4 build should still be available in the port 8081 interface for you to roll back to if you want. See: Rollback to 2.0.4? (and if it's too late for you and the Xiaomi drivers don't get updated before then, Support can probably manually make an older version available to your hub if you ask nicely, or at least I think this is something they've been able to do in the past).

@mike

any coding errors cause the text of the device driver to be removed from the page, and an error pops us. Previously, the driver text remained on screen

Just tried on both my hubs and the "old," expected behavior is still happening for me, so I wasn't able to reproduce this. Firefox 65 on macOS 10.14, for what it's worth.

[mike]

@bertabcd1234

You mean like this notice towards the beginning of the release notes for 2.0.5 that you surely read before applying the optional update whose installation you are in total control of to your hub?

No, i dont mean that. I have not yet upgraded, because I read the release notes. I mean giving us a week or so notice so we can update the device drivers beforehand.

Not all of us are coders, and we need time to figure out what to do.

[destructure00]

@mike

I mean giving us a week or so notice so we can update the device drivers beforehand.

Not all of us are coders, and we need time to figure out what to do.

You already have as much time as you need or want...

[jasonbalsor]

This makes no sense, why would you need a weeks notice for an optional non-critical update!?

If anything I prefer to wait a week after an update and let others be beta testers, LOL

[srwhite]

@mike

Feature Request: When updating or creating a device driver, any coding errors cause the text of the device driver to be removed from the page, and an error pops us. Previously, the driver text remained on screen for editing, along with the errors. Makes it difficult to debug when this occurs.

This would be nice, although I've only noticed this when pasting other peoples code. Pressing the back button on the browser at least brings the code back.