I have a completely clean installation
thanks for your feedback. I managed to get M5 running, well … sort of. It seemed to discover most things but for example could not show the basic UI sitemap. So I got an impression of the new concepts but had no confidence in this migration and would rather try again with the final release, if a stable upgrade process for openhabian seems available.
Unfortunately I have limited time for trials and also only have one hardware available (RPi4) which I need to work reliably ‘in production’.
I would also prefer to change the standard persistence service before trying another migration (I already got rid of the 1.x bindings which are no longer supported).
I understand also mapdb won’t exist in OH3. What would be the future ‘standard’ persistence for OH3 as mapdb was in OH2?
(sorry for asking just like this, I simply did not yet have time to learn what persistence to use in OH3).
thanks jjhh
Two items
- I found that a restart (or two) and the basic UI was back.
- Mapdb is fine in OH3, but you have to delete the old OH2 files before it will work. There are some posts on that subject.
Bob
1 Like
OH3 M5 - Location card does not display the number of alarms
I want to use the feature of displaying the number of alarms on a location card as described under #556.
Number of alarms (after the title)
Point_Alarm hasLocation (the location) If no matching item found: Point_Alarm isPointOf (any equipment) hasLocation (the location)
Count those with the state ON: if any result, display the count after the title as shown.
Number of alarms (after the title)So i defined
-
a switch item named Debugging_Alarm with a class of Point_Alarm
-
allocated it to an equipment (group) named Kuehlschrank (gGO_SP1_4)
-
with an allocated location (group) named Keller 2.
After toggling the switch to ON i had the hope that the location card Keller 2 showed the alarm icon next to the location title but nothing happened.
Any ideas what i have made wrong ?
Any help is appriciated.
Only if you had openHAB 3 connect and store data prior to the fix (way back in M2 I think). If you didn’t connect with OH 3 prior to that point you should not have to delete anything.
1 Like
I think i found from persistence influxdb. The problem is that when i delete an item in the logging i can’t find any rule that says it’s removed. I remove a entire items file, first only the channels and then items also, but i don’t see anything’s getting removed. So it’s normal that influx is saying that it is already existing it is not removed when i deleted an item or updated to openhab3. I will search a work around…
Hello,
I have an issue with a string query with OH 3 RC1.
Short
if (OKExecute==“OK”) query is entered with OH 2.5 (this is what I want)
but NOT entered with OH 3.
Please tell what I’m doing wrong - THX.
Please have a look at the details
Details
OH 2.5.10
pi@raspberrypi:~ $ java -version
openjdk version “1.8.0_152”
OpenJDK Runtime Environment (Zulu Embedded 8.25.0.76-linux-aarch32hf) (build 1.8.0_152-b76)
OpenJDK Client VM (Zulu Embedded 8.25.0.76-linux-aarch32hf) (build 25.152-b76, mixed mode, Evaluation)
rule “Test1”
when
Item TestSwitch1 changed to ON
then
logInfo(“Log”,“test rule start” )
var String OKExecute=executeCommandLine("/opt/openhab2/conf/scripts/lock122.sh", 100)
logInfo(“Log”,"OKExecute Value 1 " + OKExecute)
if (OKExecute==“OK”)
{
logInfo(“Log”,"OKExecute Value 2 " + OKExecute)
}
logInfo(“Log”,“test rule end” )
sendCommand(TestSwitch1, OFF)
end
pi@raspberrypi:~ $ cat /opt/openhab2/conf/scripts/lock122.sh
mkdir /tmp/lock122 && [ -d “/tmp/lock122” ] && echo “OK”
tail openhab.log
2020-12-19 10:20:11.987 [INFO ] [g.eclipse.smarthome.model.script.Log] - test rule start
2020-12-19 10:20:12.050 [INFO ] [g.eclipse.smarthome.model.script.Log] - OKExecute Value 1 OK
2020-12-19 10:20:12.054 [INFO ] [g.eclipse.smarthome.model.script.Log] - OKExecute Value 2 OK //the if query WAS entered
2020-12-19 10:20:12.057 [INFO ] [g.eclipse.smarthome.model.script.Log] - test rule end
OH 3.0.0.RC1 - Milestone Build
pi@raspberrypi:~ $ java -version
openjdk version “11.0.9.1” 2020-11-06 LTS
OpenJDK Runtime Environment Zulu11.43+100-CA (build 11.0.9.1+1-LTS)
OpenJDK Client VM Zulu11.43+100-CA (build 11.0.9.1+1-LTS, mixed mode)
rule “Test1”
when
Item TestSwitch1 changed to ON
then
logInfo(“Log”,“test rule start” )
var String OKExecute = executeCommandLine(Duration.ofSeconds(1),"/opt/openhab/conf/scripts/lock122.sh")
logInfo(“Log”,"OKExecute Value 1 " + OKExecute)
if (OKExecute==“OK”)
{
logInfo(“Log”,"OKExecute Value 2 " + OKExecute)
}
logInfo(“Log”,“test rule end” )
sendCommand(TestSwitch1, OFF)
end
pi@raspberrypi:~ $ cat /opt/openhab/conf/scripts/lock122.sh
mkdir /tmp/lock122 && [ -d “/tmp/lock122” ] && echo “OK”
tail openhab.log
2020-12-19 10:32:01.700 [INFO ] [org.openhab.core.model.script.Log ] - test rule start
2020-12-19 10:32:01.735 [INFO ] [org.openhab.core.model.script.Log ] - OKExecute Value 1 OK //the if query WAS NOT entered
2020-12-19 10:32:01.743 [INFO ] [org.openhab.core.model.script.Log ] - test rule end
Many THX for your help
Klaus
Sorry it was kind of “forgotten” in the implementation. You should have them in RC2 (but not next to the title, along with the other icons).
Thank you for your feedback and for your awesome work.
1 Like
I just came across the same issue. Have you got any feedback on this or did you find a solution? Couldn’t find anything here
Thx
Sorry to say, but neither a feedback nor a solution, yet. Seems to be no problem in other migrations 
OK, thank you. I think I have to adjust the items after import then… Luckily I don’t have so many groups with this issue
I am running Milestone 5 on my Synology NAS but using the Docker app and I have no issues with the openHAB Docker image … it might be related to your configuration!
Hi,
I tested Milestone 4 yesterday for a very short time before I jumped directly from M3 to Milestone 5 today.
I recognized that the colored output in the karaf log has gone (INFO=cyan, ERROR=red, DEBUG=black, WARNING=magenta). Any idea how to get this back?
The M5 discussed here is for OH3.0, and became obsolete with the release of stable 3.0.
They’re currently working with OH 3.1 M4 and presumably towards 3.1 M5.
Oops, sorry. I took the wrong topic …
OH 3.1 Milestone 5 was just released that is why I thought I caught the right one and did obviously not read carefully … Sorry … I was too quick!!!
I will look out for the discussion thread for the 3.1.0.M5 …