I upgraded to M5 and am glad to see a working ssh/karaf newline again
Thanks! Seems to work well. I had some (not reproducable) issues due to my timers with the m4 build, is there any need to adjust some timer rules since 2.4(M4)?
What’s the process for proposing/adding the semantic tags and/or synonyms that HABot uses. I’ve already noticed a number of locations that would be nice to have. Some that immediately come to mind…
Locations
Second Floor (parent=Floor)
Third Floor (parent=Floor)
Laundry Room (parent=Room)
Dining Room (parent=Room)
Family Room (parent=Room)
Powder Room (synonym of BathRoom)
Hallway (parent=Room)
Driveway (parent=Outside)
Patio (synonym of Terrace)
Garden (parent=Outside)
Porch (parent=Outside)
Front Porch (parent=Porch)
Back Porch (parent=Porch)
Screened Porch (parent=Porch)
Properties
Luminance
Ultraviolet
Seismic
Equipment
Fan
Ceiling Fan (parent=Fan)
Points
Heating Setpoint (parent=Setpoint)
Cooling Setpoint (parent=Setpoint)
Some possible options:
Create a dedicated thread on the forum to discuss additions?
HomeKit Integration is working for me on M5. However, when I upgraded from M4 to M5, my OH devices in Home app had lost their “Room” assignments in HomeKit. But I was easily able to reset them.
Sounds like you may need to clear pairings using Karaf and reconnect your OH install to HomeKit. Command is here.
No, if you’re using apt, switching to a specific version will always be the same in summary:
Switch to the relevant repo (i.e. stable, testing, unstable)
sudo apt-cache madison openhab2 allows you to see the list of available versions the “latest” versions are printed first e.g.
openhab2 | 2.4.0~M5-1 |.....
Install that specific version with sudo apt install openhab2=2.4.0~M5-1
A milestone in apt is always considered newer than a snapshot regardless of their dates so moving from testing to snapshot is the only case where you would need to do the above to upgrade. Otherwise use sudo apt update && sudo apt upgrade to get the latest version.
Only the stable releases are in every repository, including snapshot. Which is why you also see “2.2.0” and “2.3.0” there.
Milestone releases can’t be in the snapshot repository because “M1”, “M2” etc. is reported as newer than any number, which would break the functionality of apt upgrade.
Java 8 is still the only recommended version at this point in time. But testing to see if there are any other issues with using Java 11 is always welcome.
The “illegal reflective access” warnings don’t look nice but shouldn’t give any issues when using Java 9, 10 or 11. The warnings are there to nag developers to stop using deprecated APIs that will be removed in some future Java version.
You should IMHO open an ESH issue for discussion first, if the ontology changes are approved you’ll have to modify SemanticTags.csv as you figured out, then launch the groovy script (generateTagClasses here) to regenerate the type hierarchy - hopefully it will be done as part of the build in the future - and finally open a ESH PR with the changes.
If there are new tags, they should ideally be translated as well.
Remember you can always in the meantime tag the item with a more “generic” parent class (like ["Room"]) and add a synonym with metadata, i.e.
Group gStudy (gFF) ["Room"] { synonyms="Study,Office" }