When i try to install user widgets in user interface i get an error and this in log.
2021-11-13 17:48:57.116 [ERROR] [munity.CommunityUIWidgetAddonHandler] - Widget from marketplace is invalid: Couldn't find the widget in the add-on entry
Hi,
I have upgraded OpenHab to version 3.2.0 and I am getting the same error as well as this:
2021-12-23 08:51:29.423 [ERROR] [munity.CommunityUIWidgetAddonHandler] - Unable to parse YAML: Cannot deserialize value of type `java.util.Date` from String "Jan 1, 2021, 4:08:53 PM": not a valid representation (error: Failed to parse Date value 'Jan 1, 2021, 4:08:53 PM': Unparseable date: "Jan 1, 2021, 4:08:53 PM")
at [Source: (StringReader); line: 12, column: 12] (through reference chain: org.openhab.core.ui.components.RootUIComponent["timestamp"])
2021-12-23 08:51:29.424 [ERROR] [munity.CommunityUIWidgetAddonHandler] - Widget from marketplace is invalid: Unable to parse YAML
Most probably what @rlkoshak mentioned is correct, although these are not new widgets. They seem to have been published and downloaded by many people since February.
Edit: I only get this error, not the one with the YAML:
Hi,
since I have the same issue, I tried to install nearly all of the available widgets, including the battery status, Garbage Collection, Keypad, etc. All of which without successâŠ
Itâs allwas the same error message:
[ERROR] [munity.CommunityUIWidgetAddonHandler] - Unable to parse YAML: Cannot deserialize value of type java.util.Date from String âOct 28, 2021, 10:52:35 AMâ: not a valid representation (error: Failed to parse Date value âOct 28, 2021, 10:52:35 AMâ: Unparseable date: âOct 28, 2021, 10:52:35 AMâ)
at [Source: (StringReader); line: 37, column: 12] (through reference chain: org.openhab.core.ui.components.RootUIComponent[âtimestampâ])
My installation is RPi 3B+ with upgraded OH vom 2 to 3.2 via 3.1
So, I donât think itâs a problem with the widgets, but could it be a problem with date format? My region is Austria.
Hi, @cra. Welcome to the community and thanks for doing the in-depth test and sharing the results.
It would be useful to use the code fences option in the text editor when reporting error messages. There is a great post from Rich Koshak on the topic (How to use code fences)
on my new installed OH3.2 (VM on QNAP NAS with Ubuntu20.04LTS) I do have the same problems.
If I would do a wild guess I thing we ahve a regional settings problem. I installed my Ubunto with German locale and I see the errors below in the log file (tried 3 different ones) always referencing on the âtimestampâ row as issue.
Interestingly there is one widget called âAirCondition Controllerâ which I am able to add. but it looks like all the others dont (havent tested all of them but 6-8 others ) .
Any idea ?
M
2022-01-02 11:00:37.723 [ERROR] [munity.CommunityUIWidgetAddonHandler] - Unable to parse YAML: Cannot deserialize value of type `java.util.Date` from String "May 18, 2021, 12:42:12 PM": not a valid representation (error: Failed to parse Date value 'May 18, 2021, 12:42:12 PM': Unparseable date: "May 18, 2021, 12:42:12 PM")
at [Source: (StringReader); line: 31, column: 12] (through reference chain: org.openhab.core.ui.components.RootUIComponent["timestamp"])
2022-01-02 11:00:37.757 [ERROR] [munity.CommunityUIWidgetAddonHandler] - Widget from marketplace is invalid: Unable to parse YAML
2022-01-02 11:05:33.053 [ERROR] [munity.CommunityUIWidgetAddonHandler] - Unable to parse YAML: Cannot deserialize value of type `java.util.Date` from String "Oct 4, 2021, 11:28:30 PM": not a valid representation (error: Failed to parse Date value 'Oct 4, 2021, 11:28:30 PM': Unparseable date: "Oct 4, 2021, 11:28:30 PM")
at [Source: (StringReader); line: 71, column: 12] (through reference chain: org.openhab.core.ui.components.RootUIComponent["timestamp"])
2022-01-02 11:05:33.057 [ERROR] [munity.CommunityUIWidgetAddonHandler] - Widget from marketplace is invalid: Unable to parse YAML
2022-01-02 11:05:42.288 [ERROR] [munity.CommunityUIWidgetAddonHandler] - Unable to parse YAML: Cannot deserialize value of type `java.util.Date` from String "Feb 3, 2021, 1:12:37 PM": not a valid representation (error: Failed to parse Date value 'Feb 3, 2021, 1:12:37 PM': Unparseable date: "Feb 3, 2021, 1:12:37 PM")
at [Source: (StringReader); line: 25, column: 12] (through reference chain: org.openhab.core.ui.components.RootUIComponent["timestamp"])
2022-01-02 11:05:42.309 [ERROR] [munity.CommunityUIWidgetAddonHandler] - Widget from marketplace is invalid: Unable to parse YAML
This is odd, because the AirCondition Controller also has the timestamp property with a date that doesnât appear to be functionally different than the ones giving you the errors.
2022-01-02 21:01:42.260 [ERROR] [munity.CommunityUIWidgetAddonHandler] - Unable to parse YAML: Cannot deserialize value of type `java.util.Date` from String "Oct 2, 2021, 9:24:59 PM": not a valid representation (error: Failed to parse Date value 'Oct 2, 2021, 9:24:59 PM': Unparseable date: "Oct 2, 2021, 9:24:59 PM")
at [Source: (StringReader); line: 36, column: 12] (through reference chain: org.openhab.core.ui.components.RootUIComponent["timestamp"])
2022-01-02 21:01:42.261 [ERROR] [munity.CommunityUIWidgetAddonHandler] - Widget from marketplace is invalid: Unable to parse YAML
yes, indeed same format of timestamp on the AirCondition Controller widget. Perhaps the logged error is just a knock-on effect and not the root causeâŠ
I will try to copy the yaml code from one that does not work and add this as a personal widget to see if this is a may be a problem of the âmarketplaceâ
M
EDIT : 13:36h
I tried with the garage widget rlk_lock_list from Rich Koshak. Addng from the marketplace did not worked. But If I go to developer tools â widgets I could add the YAML code without any problems and then use the widget on an Item chainging the âAdd Metadataâ and âDefault List Item Widgetâ.
I was confused by this too because the parser is explicitely configured to handle this date format:
It doesnât specify the Locale however and if the system-configured one happens to be German, October 3-character is likely âOktâ, not âOctâ. Should be an easy fix.
In the meantime removing this timestamp line from the widgetsâ code works too, as itâs not too important.