openHAB 5.2 Release discussion

Setup, Configuration and Use News & Important Changes
221

That isn’t the reason, the problem persists after removing that add-on and restarting.

2026-08-03 13:22:13.351 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading DSL model 'thermostat.rules'
2026-08-03 13:22:13.397 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading DSL model 'upb.rules'
2026-08-03 13:22:14.059 [WARN ] [e.internal.VoiceManagerConfiguration] - No configuration description found for system:voice, unable to apply defaults!
2026-08-03 13:22:20.415 [ERROR] [.handler.AbstractScriptModuleHandler] - Script execution of rule with UID 'startup-1' failed: 'sendMail' is not a member of 'org.openhab.core.thing.binding.ThingActions'; line 6, column 3, length 74 in startup
2026-08-03 13:22:20.416 [INFO ] [e.automation.internal.RuleEngineImpl] - Rule engine started.
2026-08-03 13:22:39.358 [WARN ] [rest.core.item.EnrichedItemDTOMapper] - Failed transforming the state 'NULL' on item 'SecondFloor_Tstat_State' with pattern 'MAP(ct100.map):%s': Transformation service of type 'MAP' is not available.
2026-08-03 13:22:39.362 [WARN ] [rest.core.item.EnrichedItemDTOMapper] - Failed transforming the state 'NULL' on item 'SecondFloor_Tstat_FanMode' with pattern 'MAP(ct100-fanmode.map):%s': Transformation service of type 'MAP' is not available.
2026-08-03 13:22:39.365 [WARN ] [rest.core.item.EnrichedItemDTOMapper] - Failed transforming the state 'NULL' on item 'ForecastTodayIcon' with pattern 'JS(wmo-icon.js):%s': Transformation service of type 'JS' is not available.
222

Think I found the solution, I removed the JavaScript binding, restarted, re-installed the binding, and restarted again. That seems to have fixed it.

223

Strange, happy to hear you managed to fix it yourself!

224

similar here (1 x restart, clean cache (because it was seeing duplicate uninstalled binding for Homie) and a second restart after the clean cache and then had a strange restart mid day that i could not debug, but otherwise seems v-good

225

Updating my docker installation from 5.1.4 to 5.2.1 results in the following error:

+ IFS='

	'

+ '[' -n Etc/UTC ']'

+ mountpoint -q /etc/localtime

+ echo 'Warning: /etc/localtime is mounted. Please remove this volume mount and use the TZ environment variable instead.'

Warning: /etc/localtime is mounted. Please remove this volume mount and use the TZ environment variable instead.

++ find /usr/lib/jvm -mindepth 1 -maxdepth 1 -type d

+ export JAVA_HOME=/usr/lib/jvm/java-21-openjdk-amd64

+ JAVA_HOME=/usr/lib/jvm/java-21-openjdk-amd64

+ '[' unlimited = unlimited ']'

+ echo 'Configuring Java unlimited strength cryptography policy...'

Configuring Java unlimited strength cryptography policy...

+ sed -i 's/^crypto.policy=limited/crypto.policy=unlimited/' /usr/lib/jvm/java-21-openjdk-amd64/conf/security/java.security

+ capsh --print

+ grep -E Current:.+,cap_net_admin,cap_net_raw,.+

+ rm -f '/var/lock/LCK..*'

+ rm -f /openhab/userdata/tmp/instances/instance.properties

rm: cannot remove '/openhab/userdata/tmp/instances/instance.properties': Permission denied

Regarding Warning: /etc/localtime is mounted. Please remove this volume mount and use the TZ environment variable instead.

The current docs still list it as one of the volumes which one should mount. Or do I misunderstand something?

grafik
grafik849×206 10.9 KB

Regarding the failed rm, not sure why it fails, since permissions on the host seem ok.
grafik

I removed it manually which results in:

++ cmp /openhab/userdata/etc/version.properties /openhab/dist/userdata/etc/version.properties

+ '[' '!' -z '/openhab/userdata/etc/version.properties /openhab/dist/userdata/etc/version.properties differ: byte 267, line 8' ']'

+ echo 'Image and userdata versions differ! Starting an upgrade.'

+ tee /openhab/userdata/logs/update.log

tee: /openhab/userdata/logs/update.log: Permission denied

Image and userdata versions differ! Starting an upgrade.

Again, permissions on the host seem ok:
grafik

226

Seems to be related to selinux. Disabling it for the upgrade “solved” the issue. Strange that this did work for previous upgrades of the docker image.