# 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:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kai](https://community.openhab.org/user_avatar/community.openhab.org/kai/32/116281_2.png) [@Kai](https://community.openhab.org/u/Kai)\
**Post date:** [December 14, 2020, 7:41pm UTC](https://community.openhab.org/t/openhab-3-0-release-candidates-discussion/110200/1 "2020-12-14T19:41:39Z")

</div>

This topic can be used to discuss problems/experiences/questions on the openHAB 3.0 Release Candidates.

---

<div class="post-metadata">

**Author:** ![ranielsen](https://community.openhab.org/letter_avatar_proxy/v4/letter/r/c5a1d2/32.png) [@ranielsen](https://community.openhab.org/u/ranielsen)\
**Post date:** [December 14, 2020, 7:53pm UTC](https://community.openhab.org/t/openhab-3-0-release-candidates-discussion/110200/2 "2020-12-14T19:53:02Z")

</div>

`events.log` doesn’t contain events after upgrade from M5 to RC1. This can be fixed by editing `userdata/etc/log4j2.xml` and changing all occurrences of `smarthome.event` to o`penhab.event`.

---

<div class="post-metadata">

**Author:** ![MikeJMajor](https://community.openhab.org/user_avatar/community.openhab.org/mikejmajor/32/25283_2.png) [@MikeJMajor](https://community.openhab.org/u/MikeJMajor)\
**Post date:** [December 14, 2020, 8:14pm UTC](https://community.openhab.org/t/openhab-3-0-release-candidates-discussion/110200/3 "2020-12-14T20:14:32Z")

</div>

One of my rules failed to load:

 ![Screenshot_20201214-201011](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/1/1/11217fd9100e6100289369e206e5430a481a24da.jpeg)

---

<div class="post-metadata">

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

</div>

**Error during upgrade**  
I have tried to upgrade from M5 to RC1 using “sudo openhabian-config”, master and option 2 : Upgrade System - but I get the following error:

 ![image](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/2/5/25cb966f437e66265e125348dd81e2921b4d652e.png)

**Solved**  
After running “sudo systemctl stop frontail.service” I can now upgrade to RC1.

---

<div class="post-metadata">

**Author:** ![jensflorian](https://community.openhab.org/user_avatar/community.openhab.org/jensflorian/32/54039_2.png) [@jensflorian](https://community.openhab.org/u/jensflorian)\
**Post date:** [December 14, 2020, 8:37pm UTC](https://community.openhab.org/t/openhab-3-0-release-candidates-discussion/110200/5 "2020-12-14T20:37:28Z")

</div>

1. The startup wizard sets Country/Region in Regional settings but does not set the Country setting in Ephemeris (remains empty by default).

2. NEATO binding: Account is online but scanning fails.

> 2020-12-14 21:22:23.557 [DEBUG] [internal.handler.NeatoAccountHandler] - Attempting to find robots tied to account  
> 2020-12-14 21:22:25.630 [DEBUG] [internal.handler.NeatoAccountHandler] - Authentication Response: {“message”:“Not allowed”}

Manually adding the robot however works.

> 2020-12-14 21:34:34.289 [DEBUG] [.neato.internal.handler.NeatoHandler] - Will boot up Neato Vacuum Cleaner binding!  
> 2020-12-14 21:34:34.290 [DEBUG] [.neato.internal.handler.NeatoHandler] - Neato Robot Config: NeatoRobotConfig [refresh=60, secret=_REMOVED_]  
> 2020-12-14 21:34:34.290 [DEBUG] [ab.binding.neato.internal.NeatoRobot] - Will get STATE for Robot _REMOVED_  
> 2020-12-14 21:34:34.290 [DEBUG] [.neato.internal.handler.NeatoHandler] - Start automatic refresh at 60 seconds  
> 2020-12-14 21:34:34.291 [DEBUG] [ab.binding.neato.internal.NeatoRobot] - Calling Neato WS with body: {“reqId”:“1”,“cmd”:“getRobotState”,“params”:{}}  
> 2020-12-14 21:34:35.473 [DEBUG] [ab.binding.neato.internal.NeatoRobot] - Result from getRobotState: {“version”:1,“reqId”:“1”,“result”:“ok”,“data”: {},“error”:null,“alert”:null,“state”:1,“action”:0,“cleaning”: {“category”:4,“mode”:1,“modifier”:1,“navigationMode”:2,“mapId”:“”,“spotWidth”:0,“spotHeight”:0},“details”: {“isCharging”:false,“isDocked”:true,“isScheduleEnabled”:false,“dockHasBeenSeen”:false,“charge”:96},“availableCommands”: {“start”:true,“stop”:false,“pause”:false,“resume”:false,“goToBase”:false},“availableServices”: {“findMe”:“basic-1”,“generalInfo”:“basic-1”,“houseCleaning”:“basic-4”,“IECTest”:“advanced-1”,“logCopy”:“basic-1”,“manualCleaning”:“basic-1”,“maps”:“basic-2”,“preferences”:“basic-2”,“schedule”:“basic-2”,“softwareUpdate”:“basic-1”,“spotCleaning”:“basic-3”,“wifi”:“basic-1”},“meta”: {“modelName”:“BotVacD7Connected”,“firmware”:“4.5.3-189”}}  
> 2020-12-14 21:34:35.477 [DEBUG] [ab.binding.neato.internal.NeatoRobot] - Successfully got and parsed new state for REMOVED

---

<div class="post-metadata">

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

</div>

I’m having the same issue here..  
using master of openHABian config tool and tried with option 40-41 | openHAB testing and 40-42 | Upgrade to openHAB 3

---

<div class="post-metadata">

**Author:** ![hmerk](https://community.openhab.org/user_avatar/community.openhab.org/hmerk/32/56432_2.png) [@hmerk](https://community.openhab.org/u/hmerk)\
**Post date:** [December 14, 2020, 8:52pm UTC](https://community.openhab.org/t/openhab-3-0-release-candidates-discussion/110200/7 "2020-12-14T20:52:25Z")

</div>

There is another process running as user openhab, @Erling screenshot shows it as 413.  
Identify this process, stop it and upgrade again.

@Benjy What does the usermod do here? Is it really needed for updates ?

---

<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 😝)

---

<div class="post-metadata">

**Author:** ![Christian\_Brosius](https://community.openhab.org/user_avatar/community.openhab.org/christian_brosius/32/73683_2.png) [@Christian\_Brosius](https://community.openhab.org/u/Christian_Brosius)\
**Post date:** [December 14, 2020, 9:03pm UTC](https://community.openhab.org/t/openhab-3-0-release-candidates-discussion/110200/9 "2020-12-14T21:03:05Z")

</div>

After migration from MR5 → RC1 my rules triggered on Item-State-Changes did not fire. Manual execution of the rules worked fine.  
After an additional reboot, the problem went away without doing other changes.

---

<div class="post-metadata">

**Author:** ![thewiep](https://community.openhab.org/letter_avatar_proxy/v4/letter/t/e68b1a/32.png) [@thewiep](https://community.openhab.org/u/thewiep)\
**Post date:** [December 14, 2020, 9:09pm UTC](https://community.openhab.org/t/openhab-3-0-release-candidates-discussion/110200/10 "2020-12-14T21:09:23Z")

</div>

Thanks, in my case it’s PID 553:

`openhab 553 0.8 1.2 144004 49088 ? Ssl 21:33 0:11 node /usr/bin/frontail --ui-highlight --ui-highlight-preset /usr/lib/node_modules/frontail/preset/openhab.json -t openhab -l 2000 -n 200 /var/log/openhab/openhab.log /var/log/openhab/events.log`

when I kill this process it starts again with another PID and then I get the same message but with the new PID.  
Upgrade errors out with the same message.

---

<div class="post-metadata">

**Author:** ![hmerk](https://community.openhab.org/user_avatar/community.openhab.org/hmerk/32/56432_2.png) [@hmerk](https://community.openhab.org/u/hmerk)\
**Post date:** [December 14, 2020, 9:12pm UTC](https://community.openhab.org/t/openhab-3-0-release-candidates-discussion/110200/11 "2020-12-14T21:12:50Z")

</div>

Don‘t kill the process, do a clean

```auto
sudo service frontail stop

```

or whatever command it takes on your system.  
I normaly stop frontail before upgrading, as I also delete the logs.

---

<div class="post-metadata">

**Author:** ![thewiep](https://community.openhab.org/letter_avatar_proxy/v4/letter/t/e68b1a/32.png) [@thewiep](https://community.openhab.org/u/thewiep)\
**Post date:** [December 14, 2020, 9:24pm UTC](https://community.openhab.org/t/openhab-3-0-release-candidates-discussion/110200/12 "2020-12-14T21:24:24Z")

</div>

ah perfect, thanks!  
After stopping the frontail service the upgrade passed fine.  
Weird as it’s the first time I needed to do this.

---

<div class="post-metadata">

**Author:** ![Wolfy](https://community.openhab.org/letter_avatar_proxy/v4/letter/w/e9a140/32.png) [@Wolfy](https://community.openhab.org/u/Wolfy)\
**Post date:** [December 14, 2020, 9:43pm UTC](https://community.openhab.org/t/openhab-3-0-release-candidates-discussion/110200/13 "2020-12-14T21:43:03Z")

</div>

Hi All!  
Tried to upgrade from M5 to RC1 in docker by replacing with new image. It got stuck in endless loop as it says “You are already on Openhab 3.0.0.M5” and restarts up upgrade process. If I put M5 image back it boots properly.

---

<div class="post-metadata">

**Author:** ![Benjy](https://community.openhab.org/letter_avatar_proxy/v4/letter/b/eada6e/32.png) [@Benjy](https://community.openhab.org/u/Benjy)\
**Post date:** [December 14, 2020, 9:46pm UTC](https://community.openhab.org/t/openhab-3-0-release-candidates-discussion/110200/14 "2020-12-14T21:46:27Z")

</div>

> [@hmerk](#):
>
> @Benjy What does the usermod do here? Is it really needed for updates ?

When the upgrade detects that the home directory is still `/var/lib/openhab2` it changes it to the correct path. I hadn’t realised that openHABian still uses the `openhab` user for frontail (it shouldn’t do (cc @mstormi)). I’ll release a workaround.

---

<div class="post-metadata">

**Author:** ![wborn](https://community.openhab.org/user_avatar/community.openhab.org/wborn/32/55946_2.png) [@wborn](https://community.openhab.org/u/wborn)\
**Post date:** [December 14, 2020, 10:00pm UTC](https://community.openhab.org/t/openhab-3-0-release-candidates-discussion/110200/15 "2020-12-14T22:00:26Z")

</div>

> [@Wolfy](#):
>
> It got stuck in endless loop as it says “You are already on Openhab 3.0.0.M5” and restarts up upgrade process

It’s probably the Portainer issue described in the README:

> **[GitHub - openhab/openhab-docker: Repository for building Docker containers for...](https://github.com/openhab/openhab-docker#portainer)**
>
> Repository for building Docker containers for openHAB

---

<div class="post-metadata">

**Author:** ![Christian\_Brosius](https://community.openhab.org/user_avatar/community.openhab.org/christian_brosius/32/73683_2.png) [@Christian\_Brosius](https://community.openhab.org/u/Christian_Brosius)\
**Post date:** [December 14, 2020, 10:09pm UTC](https://community.openhab.org/t/openhab-3-0-release-candidates-discussion/110200/16 "2020-12-14T22:09:25Z")

</div>

@Wolfy  
Yes, when using portainer you have to delete the ‘OPENHAB\_VERSION’-Environmentvariable of your OpenHAB-Instance before doing the upgrade.

---

<div class="post-metadata">

**Author:** ![mstormi](https://community.openhab.org/user_avatar/community.openhab.org/mstormi/32/55857_2.png) [@mstormi](https://community.openhab.org/u/mstormi)\
**Post date:** [December 14, 2020, 11:00pm UTC](https://community.openhab.org/t/openhab-3-0-release-candidates-discussion/110200/17 "2020-12-14T23:00:56Z")

</div>

> [@Benjy](#):
>
> I hadn’t realised that openHABian still uses the openhab user for frontail (it shouldn’t do)

Right it shouldn’t and I’d think it doesn’t on fresh installs in quite a long time. If you have installed openHABian/frontail before this got fixed though you’ll still have the old user. Re-installing frontail via menu might help there.

---

<div class="post-metadata">

**Author:** ![mstormi](https://community.openhab.org/user_avatar/community.openhab.org/mstormi/32/55857_2.png) [@mstormi](https://community.openhab.org/u/mstormi)\
**Post date:** [December 15, 2020, 8:06am UTC](https://community.openhab.org/t/openhab-3-0-release-candidates-discussion/110200/18 "2020-12-15T08:06:18Z")

</div>

6 posts were split to a new topic: [Migration question](https://community.openhab.org/t/migration-question/110244)

---

<div class="post-metadata">

**Author:** ![RGroll](https://community.openhab.org/user_avatar/community.openhab.org/rgroll/32/44346_2.png) [@RGroll](https://community.openhab.org/u/RGroll)\
**Post date:** [December 15, 2020, 12:53am UTC](https://community.openhab.org/t/openhab-3-0-release-candidates-discussion/110200/21 "2020-12-15T00:53:31Z")

</div>

The ‘RC1-2’ might be the version with the fix, that @ysc mentioned above, already applied (but I’m not 100% sure)

In that case your commands would be:

```auto
wget https://openhab.jfrog.io/openhab/list/openhab-linuxpkg/pool/main/3.0.0~RC1/openhab_3.0.0~RC1-2_all.deb
sudo apt install ./openhab_3.0.0~RC1-2_all.deb

```

If you do a fresh install anyway, I would try it out and having a look in the logs after install - if anything looks good, you’re probably good to go. 🙂

---

<div class="post-metadata">

**Author:** ![Benjy](https://community.openhab.org/letter_avatar_proxy/v4/letter/b/eada6e/32.png) [@Benjy](https://community.openhab.org/u/Benjy)\
**Post date:** [December 15, 2020, 2:26am UTC](https://community.openhab.org/t/openhab-3-0-release-candidates-discussion/110200/25 "2020-12-15T02:26:29Z")

</div>

> [@RGroll](#):
>
> The ‘RC1-2’ might be the version with the fix,

The ‘-2’ at the end is just for the `.deb` packaging, it fixes the following install error.

> [@Erling](#):
>
> have tried to upgrade from M5 to RC1 using “sudo openhabian-config”, master and option 2 : Upgrade System - but I get the following error:

The content after the install is identical and is now given to anyone who uses the milestone/testing repository. Unfortunately that does mean the same issues are present.

[Next page](https://community.openhab.org/t/openhab-3-0-release-candidates-discussion/110200.md?page=2)
