All of the issues that I identified in moving from M3 to M4 have been corrected in latest SNAPSHOT build. Kudos to the development team for the ability to quickly respond, identify the root cause and implement a fix. Very Impressive!
I am getting a lot of those as well using M4
See here for my testing results:
Try using the latest SNAPSHOT. That seems to have fixed many issues.
Yes it has fixed a few problems.
This line of code doesn’t work:
2023-07-08 10:25:31.286 [WARN ] [rg.openhab.core.io.net.exec.ExecUtil] - Failed to execute commandLine '[/usr/bin/mosquitto_pub, -h, 192.168.1.164, -t, broadlink/tv/sony/guide, -m, replay]'
Other than that seems ok. Will test further later on.
Have a lot of these errors now but that is probably because I changes the json file:
2023-07-08 10:21:09.105 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/javascript;version=ECMAScript-5.1' could not be found for identifier: 107fce72-0845-4f8f-a377-61a9e72fe5a4
2023-07-08 10:21:40.528 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/javascript;version=ECMAScript-5.1' could not be found for identifier: 2fc3dedc-efa6-484b-a046-e33dc89b0717
2023-07-08 10:21:40.650 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/javascript;version=ECMAScript-5.1' could not be found for identifier: 107fce72-0845-4f8f-a377-61a9e72fe5a4
Thanks
hi. also updated from M3 to M4. Lot’s of issues…
- […]Field ‘firmwareStatus’ could not be eliminated[…]
- […]Failed transforming the state[…]
- […]transformation throws exception[…]
- […]Failed to retrieve item during widget rendering[…]
- openhab schickte eine leere sitemap-liste / OpenHAB retured empty sitemap list
- Rules don’t fire automatically (“When the system has reached start level 20”)
I also noticed another thing, which didn’t happened in 4M2 - although I’m not sure whether it is Openhab issue or something with Influxdb itself.
In any case, since M4, storing of state change state takes bit longer than it used to and in one rule I had to increase delay for correct reading of persistence from 500ms to 3500ms. I admit, I have bunch of items, some of them are stored on change but such problem did not exist in M2.
Additionally, I get following errors with RRD4J now, which sort of suggest, that items are also not persisted in order any more too. I’m using default RRD4J persistence settings
2023-07-07 10:48:00.622 [WARN ] [d4j.internal.RRD4jPersistenceService] - RRD4J does not support adding past value this=1688719680, last update=1688719681. Discarding LogViewer_ManualUpdate - 0.0
2023-07-07 10:20:00.542 [WARN ] [d4j.internal.RRD4jPersistenceService] - RRD4J does not support adding past value this=1688718000, last update=1688718001. Discarding PowerPlug_07_Power - 1792.0
2023-07-07 10:07:32.802 [WARN ] [d4j.internal.RRD4jPersistenceService] - RRD4J does not support adding past value this=1688717252, last update=1688717253. Discarding MotionSensor_09_LinkQuality - 105.0
2023-07-07 10:07:32.777 [WARN ] [d4j.internal.RRD4jPersistenceService] - RRD4J does not support adding past value this=1688717252, last update=1688717253. Discarding MotionSensor_09_LinkQuality - 98.0
2023-07-07 09:59:23.096 [WARN ] [d4j.internal.RRD4jPersistenceService] - RRD4J does not support adding past value this=1688716763, last update=1688716764. Discarding PowerPlug_09_Quality - 91.0
2023-07-07 09:37:39.472 [WARN ] [d4j.internal.RRD4jPersistenceService] - RRD4J does not support adding past value this=1688715459, last update=1688715460. Discarding PowerPlug_09_Quality - 83.0
Can you show the persistence definition?
I’m seeing @reyhard’s messages too.
I have opened Persistence warnings · Issue #3697 · openhab/openhab-core · GitHub.
Various items, nothing special about them. Maybe except that all of them are UoM items and have unit metadata set.
But I think the key is the warning only appears when they’re updated (or rather persisted as specified on every change) multiple times in a second.
openHAB 4.0.0-SNAPSHOT - Build #3533
Anyone else having issues with state descriptions? In the webui, I can’t select/change them, but if I navigate from the model into the item itself, it works as expected. I think this started on 4.0.0.M4.
{
"link": "http://openhabian:8080/rest/items/Hayward_Filter_Filter_Speed_States",
"state": "67",
"stateDescription": {
"readOnly": false,
"options": [
{
"value": "0",
"label": "Off"
},
{
"value": "20",
"label": "Low"
},
{
"value": "67",
"label": "Medium"
},
{
"value": "100",
"label": "High"
},
{
I’m not sure what you mean here. As far as I’m aware, the only way that has ever been supported to change an Item’s state description is by navigating to the Item’s page, whether you navigate to it from the Model or from somewhere else. It’s Item metadata after all and the Item page is the only place where Item metadata can be edited.
Rich,
My apologies. I didn’t do a very good job explaining my issue. I’m not trying to change the state descriptions, but rather click on the default list item widget to issue a command to the item. The state description label list does not pop up. The item acts as if it is read only. It does properly display the correct state description label. In the item page itself, it works like normal.
So it works with the default stand alone widget which is shown in the screen shot.
Show the default list Item widget configuration since that’s the one that’s broken. Note that the list will only show up for a oh-label-item with an action of options.
Yes, I can confirm this. But was not sure if I need to change something in my configuration.
It has changed definitively from M3 to M4 and I see this behaviour e.g. for Roborock Vacuum Control and Sonos Favorites. In Item page it works, in Main UI it’s read only. But did not have time yet to check more in detaill.
Item page without Metadata:
MainUI:
In MainUI (Locations and Equipment), the same item is read only and no selection is possible.
I’m quite sure it would be possible to fix with “Default List Item Widget”. But in M3 it was not needed.
Before installing the Ambient Weather binding:
openhab> list -s -t 0 | grep -i json
17 │ Active │ 11 │ 1.0.6 │ org.apache.felix.cm.json
132 │ Active │ 80 │ 0.19.0.v20221118-0359 │ org.eclipse.lsp4j.jsonrpc
210 │ Active │ 80 │ 4.0.0.202307080306 │ org.openhab.core.storage.json
239 │ Active │ 80 │ 20180813.0.0 │ json
274 │ Active │ 75 │ 4.0.0.202307100418 │ org.openhab.transform.jsonpath
After installing the binding:
openhab> list -s -t 0 | grep -i json
17 │ Active │ 11 │ 1.0.6 │ org.apache.felix.cm.json
132 │ Active │ 80 │ 0.19.0.v20221118-0359 │ org.eclipse.lsp4j.jsonrpc
210 │ Active │ 80 │ 4.0.0.202307080306 │ org.openhab.core.storage.json
239 │ Active │ 80 │ 20180813.0.0 │ json
274 │ Active │ 75 │ 4.0.0.202307100418 │ org.openhab.transform.jsonpath
283 │ Active │ 80 │ 20230227.0.0 │ json
I tried stopping 283 but it didn’t help.
Still persisting in M4 and Snapshot 3533
I also noticed it restarts my OH cloud connection when it installs and removes. The actual log message seems to be related to that, not the Ambient Weather binding.
I just opened an Issue to track it too
Here is the default list item widget config. It’s not just this one item. Every one of my items with command options is read only in the gui.
Item Config:
label: Filter Speed States
type: String
category: ""
groupNames:
- gHayward_Filter
groupType: None
function: null
tags:
- Point
Default List Item Widget Config
value: ""
config: {}
Has an issue been filed yet?
Based on the config the action looks correct.
Hint, it’s way better to click the Code tab and paste that with code fences compared to screen shots.
```
code goes here
```
Thanks Rich. I’ll post code next time. As for opening an issue, I’m running openHabian on bookworm on an intel NUC. I know this is frowned upon and could be my issue.
@michaeljoos,
Are you running OpenHabian on a RasPi? If so, I can open an issue.
This shouldn’t have anything to do with how OH is installed. It’s a runtime issue, not an installation or deployment issue.
4 Likes
A post was split to a new topic: Zwave problem on new OH4 install