openHAB 5.2 Milestone discussion

Setup, Configuration and Use News & Important Changes
110

Latest snapshot build S5350 contains that fix.
It also includes the latest Karaf upgrade planned for next milestone, so other issues may show up in the snapshot.

111

@Kai you say there will be a new milestone; but will it be 1) in the next few days (quick fix), or 2) in the next ~1..2 months (just another release in the usual 30 day plus milestone cycle)?

EDIT: reason for asking is that if openhabian system is following ā€œlatest milestoneā€ I would like it to be ā€œlatest-known-good-milestoneā€ without having 30 days or more of ā€œknown-not-goodā€..

112

1! Expect it tomorrow already!

113

@Mherwege : did you check that with managed sitemap?

114

No, not yet.

115

There was this recent change:

@timl : you were previously with 5.2 milestone 2 when it worked?

116

With 5.2.M3 I had a syntax error with a DSL rule and had to rollback quickly to M2.

Maybe someone can confirm?

On M3 a piece of code like

import java.time.Duration
...............................
val duration = Duration.between(duration1, duration2).toSeconds()

gives:

no viable alternative at input 'between'
117

between is a new rule keyword (in rule conditions).
Use duration = ^between(ā€¦)
Solutions are in study to avoid that problem in the final release.

118

First, thanks for all the good work. I was trying the milestones to fix Unifi (which did not work yet), but all else was good until M4. Now something changed in persistence/influx/quantitative, trying to understand what, canā€™t find it.

Iā€™m on RPI, docker, influxdb2 as persistence. RulesDSL to calculate energies.

This code started to return some strange values (no error, but wrong data):

     val feedinNowH = feedin_energy_today.persistedState(timeNow)
     val feedinPrevH = feedin_energy_today.persistedState(timePrev)

Debugging seems that there are right data in influxdb (can see them directly), but not with the exact timestamp (which is rounded to hours, while data are coming every minute with some seconds,ms offset). Further debugging suggests that perhaps the request does not hit influxdb and/or get some ā€œorphanedā€ data (perhaps from previously used internal persistence, which defaulted in previous upgrade before I changed the influxdb configuration or some historical data in influxdb).

I tried to change to avoid not having exact number and specifying the persistence service by changing to:

     val etodayNowH = Etoday_togrid.maximumBetween(timeNowStart, timeNowEnd, "influxdb")
     val etodayPrevH = Etoday_togrid.maximumBetween(timePrevStart, timePrevEnd, "influxdb")

but it is still getting the same strange number. Rolling back to M2 fixes it.

Item definition:

Number Etoday_togrid "Gained Energy Today to Grid and House [%.1f kWh]"  <energy> (gSolaxModbus, gSolaxModbusSelection) {channel="modbus:data:localhostTCP:inputRegisters:ETODAY_TOGRID:number" }

but I also tried changing (without success) to

Number:Energy Etoday_togrid "Gained Energy Today to Grid and House [%.1f kWh]"  <energy> (gSolaxModbus, gSolaxModbusSelection) {channel="modbus:data:localhostTCP:inputRegisters:ETODAY_TOGRID:number", unit="kWh" }

Tried to read release notes, but did not hit anything obvious. Any ideas?

119

Yes. In 5.2M2 everthing is working. In 5.2M4 the sitemap structure works again, but conditional stuff (icon color, label color, icon etc.) is not working anymore.

120

I am aware and working on a fix. It may wor if you put == in front of the condition value.

121

It has been fixed now:

122

It has been fixed.