Closed mstormi closed 3 years ago
Thanks for reporting. We had a similar issue #1373 which is fixed by #1377 and #1406 in OH3.
Running 2.5.5 so #1377 should be in ?
No, unfortunately not. OH 2.5.x is based on OHC 2.5 which has been released on 16th Dec. 2019. #1377 has been merged in Feb. 2020.
Oh, ok. That's confusing many users not just me. Will there ever be an update to OHC2.5? Else it does not make sense to maintain things in 2 places, does it ? (given that OH3 has its own branch)
We do not maintain the core in two places. OHC2.5 was a final release and we do not plan to release any updates for it in the future. This repository only contains a "master" branch for OHC3.
Ah, so I misunderstood your statement (as #1377 being a fix to OH2.5 and #1406 being the same fix just applied to OH3). Man sollte mal boolsche Logik-Klammern in der Sprache einführen :-) Ok so no fix for now. Will then remove that item from the group as a workaround.
How do you handle cases like this in Github ? keep open until we can validate it's fixed in OH3?
There is no special way to handle such cases. Fell free to close this issue or not.
@mstormi May I ask you to check if it is fixed in OH3? Thanks.
Haven't ever seen it again since running OH3 so I think it's fixed.
I had this UoM item
Number:Intensity maxSonnenscheinRad "max. Sonneneinstrahlung zu dieser Uhrzeit [%.1f W/m²]" <sun> (Sonnenschutz,Einstellungen)
with a valid value but on updates it kept causing trouble in both groups it is in. (Both groups have no specific type or auto calculation of AVG or similar)
On another occasion I got