# openHAB 3.0 Release Candidates discussion

**URL:** <https://community.openhab.org/t/openhab-3-0-release-candidates-discussion/110200>\
**Category:** News & Important Changes\
**Created:** [December 14, 2020, 7:41pm UTC](https://community.openhab.org/t/openhab-3-0-release-candidates-discussion/110200 "2020-12-14T19:41:38Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![ysc](https://community.openhab.org/letter_avatar_proxy/v4/letter/y/e480ec/32.png) [@ysc](https://community.openhab.org/u/ysc)\
**Post date:** [December 14, 2020, 8:54pm UTC](https://community.openhab.org/t/openhab-3-0-release-candidates-discussion/110200/8 "2020-12-14T20:54:36Z")

</div>

If your logs are full of warnings like these

`Field 'firmwareStatus' could not be eliminated: Can not set final org.openhab.core.thing.firmware.dto.FirmwareStatusDTO field org.openhab.core.io.rest.core.thing.EnrichedThingDTO.firmwareStatus to null value`

when you go to the settings in the UI, that’s my fault and a fix is on the way: [[REST] Add firmwareStatus to things in summary mode by ghys · Pull Request #1932 · openhab/openhab-core · GitHub](https://github.com/openhab/openhab-core/pull/1932)

If you’re so annoyed and can’t wait to get rid of these messages, do a  
`bundle:update org.openhab.core.io.rest.core https://github.com/ghys/openhab-core/releases/download/rc1-rest-fix/org.openhab.core.io.rest.core-3.0.0-SNAPSHOT.jar`  
(disclaimer: in theory you shouldn’t update untested bundles like this 😝)

---

_[View the full topic](https://community.openhab.org/t/openhab-3-0-release-candidates-discussion/110200)._