Try RC2.
Shouldnât manual installed bindings be visible in the Settings -> Bindings view? I installed an homematic binding manually to verify a fix. Itâs visible when I add new things but I canât see the binding in the settings.
Good question. But that was the same in PaperUI. I guess this is because you install a single bundle while installing via UI (or config-file) installs a feature.
Until this, this did not worked? What scripting languages supported right now?
How does these work? And what about the migration of Jython/Javascript rules from openHAB 2?
No, unless somebody writes a binding for it.
Is there a way to use weatherbit.io 1 in OH3? In OH2 I used for it the Weather-Binding-V1.
Run it in openHAB2 and use the remoteopenhab
binding in OH3 to get the Items available in OH3.
Jython has just been ported to openHAB3 in RC2. The addon installs without issues, and the folder structure seems to follow that from openHAB2. After restarting openHAB service it complains about joda (I think I have read something about joda somewhere). So I guess that there is still some work to do before it is integrated. But for now the most important part is that installing the addon is as easy as any other addon
Joda time is deprecated and no longer supported in oh3.
Please use java time. There are already many posts here about this change.
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.
Models are just item tags which are restricted to certain values. You can add those to your files.
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
Did RC2 resolve this?