openHAB 3.0 Release Candidates discussion

Joda time is deprecated and no longer supported in oh3.
Please use java time. There are already many posts here about this change.

2 Likes

A post was split to a new topic: Outlets in OH3

After upgrading to RC2 my rules are still not firing.
Since I seem to be the only one with this issue I assume there might be something wrong with my installation and need to do a clean install.

A post was split to a new topic: Failed to upgrade due to frontail

A post was split to a new topic: Generic advice on OH3

Models are just item tags which are restricted to certain values. You can add those to your files.

1 Like

Compared to M1 and M3 - didn’t test M5 - the RC1 has again become very RAM hungry. Where there any changes and is this addressed in the final release?

On RC2 this UI rule

triggers:
  - id: "1"
    label: Às 08:00
    configuration:
      cronExpression: 0 0 8 ? * * *
    type: timer.GenericCronTrigger
conditions: []
actions:
  - inputs: {}
    id: "2"
    label: Desligar aparelhos eléctricos
    configuration:
      itemName: gPower
      command: OFF
    type: core.ItemCommandAction
  - inputs: {}
    id: "3"
    label: Desligar ar condicionado
    configuration:
      itemName: gAirCon
      command: OFF
    type: core.ItemCommandAction

triggered twice @ 07:59:59.949 and 08:00:00.949

2020-12-20 07:59:59.949 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'gPower' received command OFF
2020-12-20 07:59:59.951 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'gAirCon' received command OFF
2020-12-20 07:59:59.952 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'AN_Cellar_Light' received command OFF
2020-12-20 07:59:59.959 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'GF_LivingDining_Power' received command OFF
2020-12-20 07:59:59.966 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'GF_Office_Solius' received command OFF
2020-12-20 07:59:59.973 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'GF_LivingRoom_Stove_Power' received command OFF
2020-12-20 07:59:59.975 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'OU_Terrace_Light' received command OFF
2020-12-20 07:59:59.981 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'AT_Attic_Light' received command OFF
2020-12-20 07:59:59.989 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'FF_Bathroom_Power' received command OFF
2020-12-20 07:59:59.995 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'FF_MasterBedroom_Power' received command OFF
2020-12-20 08:00:00.008 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'GF_Kitchen_AirCon' received command OFF
2020-12-20 08:00:00.026 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'FF_MasterBedroom_AirCon' received command OFF
2020-12-20 08:00:00.038 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'GF_LivingDining_AirCon' received command OFF
2020-12-20 08:00:00.055 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'AN_Cellar_Light' predicted to become OFF
2020-12-20 08:00:00.060 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'GF_LivingDining_Power' predicted to become OFF
2020-12-20 08:00:00.066 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'GF_Office_Solius' predicted to become OFF
2020-12-20 08:00:00.073 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Lareiraligar_Input' received command 0
2020-12-20 08:00:00.079 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'OU_Terrace_Light' predicted to become OFF
2020-12-20 08:00:00.104 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'AT_Attic_Light' predicted to become OFF
2020-12-20 08:00:00.109 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'GF_LivingRoom_Stove_Power' changed from ON to OFF
2020-12-20 08:00:00.111 [INFO ] [hab.event.GroupItemStateChangedEvent] - Item 'gPower' changed from UNDEF to OFF through GF_LivingRoom_Stove_Power
2020-12-20 08:00:00.112 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'Lareiraligar_Input' predicted to become 0
2020-12-20 08:00:00.949 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'gPower' received command OFF
2020-12-20 08:00:00.951 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'gAirCon' received command OFF
2020-12-20 08:00:00.953 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'AN_Cellar_Light' received command OFF
2020-12-20 08:00:00.960 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'GF_LivingDining_Power' received command OFF
2020-12-20 08:00:00.965 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'GF_Office_Solius' received command OFF
2020-12-20 08:00:00.970 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'GF_LivingRoom_Stove_Power' received command OFF
2020-12-20 08:00:00.978 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'OU_Terrace_Light' received command OFF
2020-12-20 08:00:00.986 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'AT_Attic_Light' received command OFF
2020-12-20 08:00:00.989 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'FF_Bathroom_Power' received command OFF
2020-12-20 08:00:00.991 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'FF_MasterBedroom_Power' received command OFF
2020-12-20 08:00:00.997 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'GF_Kitchen_AirCon' received command OFF
2020-12-20 08:00:00.998 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'FF_MasterBedroom_AirCon' received command OFF
2020-12-20 08:00:01.000 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'GF_LivingDining_AirCon' received command OFF
2020-12-20 08:00:01.001 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'AN_Cellar_Light' predicted to become OFF
2020-12-20 08:00:01.019 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'GF_LivingDining_Power' predicted to become OFF
2020-12-20 08:00:01.024 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'GF_Office_Solius' predicted to become OFF
2020-12-20 08:00:01.025 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Lareiraligar_Input' received command 0
2020-12-20 08:00:01.028 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'OU_Terrace_Light' predicted to become OFF
2020-12-20 08:00:01.029 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'AT_Attic_Light' predicted to become OFF
2020-12-20 08:00:01.033 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'Lareiraligar_Input' predicted to become 0

Should have triggered just once

Problem after upgrade from M5 to RC2 (openhabian):

tail -f /var/log/openhab/openhab.log /var/log/openhab/events.log:

Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve org.openhab.core.automation/3.0.0.RC2: missing requirement [org.openhab.core.automation/3.0.0.RC2] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.openhab.core)(version>=3.0.0)(!(version>=4.0.0)))" [caused by: Unable to resolve org.openhab.core/3.0.0.RC2: missing requirement [org.openhab.core/3.0.0.RC2] osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=11))"]

at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343) ~[org.eclipse.osgi-3.12.100.jar:?]

at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343) ~[org.eclipse.osgi-3.12.100.jar:?]

at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343) ~[org.eclipse.osgi-3.12.100.jar:?]

at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343) ~[org.eclipse.osgi-3.12.100.jar:?]

... 12 more

Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve org.openhab.core/3.0.0.RC2: missing requirement [org.openhab.core/3.0.0.RC2] osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=11))"

at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343) ~[org.eclipse.osgi-3.12.100.jar:?]

at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343) ~[org.eclipse.osgi-3.12.100.jar:?]

at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343) ~[org.eclipse.osgi-3.12.100.jar:?]

at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343) ~[org.eclipse.osgi-3.12.100.jar:?]

at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343) ~[org.eclipse.osgi-3.12.100.jar:?]

... 12 more

RC2 - same problem with expiration as reported here

Did RC2 resolve this?

I have a question regarding connecting OpenHAB3 to my openhab.org. I have been running OH2 with my openhab.org for almost 2 years and no issues. I have now created a new account with myopenhab.org and connected OH3 RC2 to my openhab.org and can receive Notifications to my iOS devices as was the case with OH2. However I am not able to view the OH3 Dashboard remotely using my openhab.org, nor do my iOS OpenHAB apps allow me to see my OH3 Sitemaps when I am off my LAN. Further my OWNTracks client is unable to connect through myopenahb.org as it did when I was using OH2. my openhab.org shows that I am ONLINE, and as I said I receive Notifications, so my question is: Is this expected behavior at this point for OH3 and myopenhab.org or do I need to look closer to home and focus on my setup? I don’t want to be wasting time chasing something that is know to be an issue at this point the development of OH3.

1 Like

You need to login to
home.myopenhab.org and then click on the link to your dashboard. That‘s all.

As a second choice, you can still use BasicUI with sitemaps and this is working with iOS App and openHAB 3.

1 Like

Ok. Thanks for ur reply. I have tried login to home.myopenhab.org but I can’t get the dashboard to load nor do my iOS apps load the the basicUI. If it is working for you and others then it must be something with my setup so I will focus there.

Once you logged into home.myopenhab.org, does it indicate your openhab instance as online ?
If so, you should find a link below to show your dashboard .

first impression is yes, RC2 seems to be less RAM demanding for now (after 6 h)…

1 Like

RC2: When you create a equipment and change it from group to contact, the “Add to model” option is no longer displayed. Is this intentional? I usually need to create points to this equipment, to make door badges in location widgets visible. As a workaround I leave the equipment as group, create the points and then change the equipment to contact.

Sorry for asking a stupid question…

How to upgrade from M5 to RC2?

M5 was installed as follows (fresh install):
wget https://openhab.jfrog.io/openhab/list/openhab-linuxpkg/pool/main/3.0.0~M5/openhab_3.0.0~M5-1_all.deb
sudo apt install ./openhab_3.0.0~M5-1_all.deb

Do I just do the same with RC2 after backup and stopping the openhab service?
wget https://openhab.jfrog.io/openhab/list/openhab-linuxpkg/pool/main/3.0.0~RC2/openhab_3.0.0~RC2-1_all.deb
sudo apt install ./openhab_3.0.0~RC2-1_all.deb

… then restore the backup?
… or is there an upgrade command? (sudo apt upgrade ./openhab_3.0.0~RC2-1_all.deb)

Why did you not use the repo package (apt) install? Then you would have upgrade commands available. Currently apt knows nothing about your non-package installation.

I had troubles connecting to the repo and followed the recommendation below.
+++
Troubleshooting

If you have trouble connecting to the repo with an error that looks like:

Unknown date format Bad header data [IP: XX.XX.XX.XX 443]

then in place of the install command, you can use the file directly e.g.:

wget https://openhab.jfrog.io/openhab/list/openhab-linuxpkg/pool/main/3.0.0~S1919/openhab_3.0.0~S1919-1_all.deb
sudo apt install ./openhab_3.0.0~S1919-1_all.deb

For later versions than the example above, the list of versions can be found here 272.
+++

I was unaware of the implications of that install…

How do I best get on to RC2 and further?
Remove M5 and do a new fresh install from the repo? then restore backup?