I agree, selecting a trigger could be much nicer. But I think fixing that would be a lower priority to fixing the Blockly problem and fixing the list of binding actions in the actions list (either make them work or remove them, I’ve not checked in awhile I don’t know if there has been any movement on the issue for that on openhab-core). The list of triggers is basically fixed. So with a little bit of docs and a little bit of experience even basic users can become comfortable with it. The Blockly problem and list of binding actions is already causing problems for users.
We need to cover Blockly and script actions better in the rules part of the tutorial anyway so we might just need to cover it in the docs if we can’t fix these before the release. So long as we remember to go back and fix them later.
I also had that issue.
Then, after burning the image and updating openhabian.conf (for my WIFI), I also increased the log level, setting debugmode=on in that same file.
When I then started the upgrade to Openhab3, I noticed all of a sudden I got prompts about overwriting files. Did not see that with minimal logging and I guess this is why it was hanging and never continued.
Answered every question with Y (overwrite), and the installation is now continuing.
Not up and running yet though but that is another discussion
Finally got my head straight(er) and used the configuration tool to do the work. Dealt with the issue that Bucofski noted (by hitting ‘Y’ 5 times), enabled and started the service, got the web page up, created the user and set the location. Tried to add 2 add-ons (basicUI and z-wave) and got the following
2020-12-09 02:08:42.633 [INFO ] [org.openhab.ui.internal.UIService ] - Started UI on port 8080
2020-12-09 02:09:19.738 [INFO ] [.core.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2020-12-09 02:09:37.110 [INFO ] [p.auth.internal.AuthorizePageServlet] - First user account created: derek
2020-12-09 02:09:43.006 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Time zone set to ‘America/Denver’.
2020-12-09 02:09:43.011 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Locale set to ‘en_US’.
2020-12-09 02:10:27.689 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Location set to {removed}.
2020-12-09 02:11:14.366 [ERROR] [t.core.internal.addons.AddonResource] - Exception while installing add-on: null
EDIT: Page refresh took me back to the start-up. I didn’t add location or add-ons. Main screen came up. Tried to add any add-on through the settings menu gave the same ‘null’ message in the log.
I’m trying to upgrade to M5 via openhab-config, following above instruction in the documentation but installation of openHAB3 ‘hangs’ at ‘Installing selected openHAB version …’ and never finishes.
Is this supposed to work currently at all or am I missing anything?
Thanks.
I’ve just started playing with OH3 M5, and stumbled above the following (not sure if there’s a GIT issue)
After installing the AVM Binding and configuring all of the data, the FritzBox jumps to “ONLINE”:
I assume you mean addons.config I thought that was a cache file maintained by OH. I have only edited that to remove invalid addons cached after an upgrade.
sorry for my bad english, but what i was trying to say was. You can add you’re binding in that file and test if the binding is active and works… it is not something you have to do every time, but for testing reasons you can
yes that’s true, but then you only know that the manual config works. Then you still don’t know if the file is corrupt, missing or for whatever reason it doesn’t work… It is only a test.
Some bad stuff happened in "read ephemeris files": java.lang.IllegalArgumentException: 2021-03-27T20:37:19.154840+01:00[Europe/Berlin] is not in a valid format.
Hello,
Yannick mentioned in the Meetup 2020 Demo the setup and configuration of MQTT broker.
I tried to follow his steps in my brand new MS5 test installation but I haven’t had the success of autodiscovering (Inbox items).
I tried that with my existing OH2 Mosquitto MQTT server.
The broker is going ONLINE but no entries in the inbox. Manual configuration are successful… but liked the autodiscovery feature
Does anybody can give me a hint where my knot in my thoughts can be located?
Thanks a lot!
Do your devices follow the Home Assistant or Homie standard? If not they cannot be auto-discovered. This is as it has always been since the binding was released in 2.4.
In M5 I am getting a Validation Issue with my old style rules file as follows…
2020-12-10 17:15:02.778 [INFO ] [el.core.internal.ModelRepositoryImpl] - Validation issues found in configuration model '24g.rules', using it anyway:
The field Tmp_24gRules.motionTriggerWindow refers to the missing type Object
The relevant lines are as follows. Note that the error is on motionTriggerWindow but not on either motionDetectorTimer or motionDetectorPhase.
val Map<String, Timer> motionDetectorTimer = newHashMap
val Map<String, DateTime> motionTriggerWindow = newHashMap
val Map<String, Integer> motionDetectorPhase = newHashMap