[openuv] invalid json received

[nesys]

strange issue with Openuv Binding. I see sometimes the binding is suddenly stopping, and I see this on PaperUI:

Invalid json received when calling https://api.openuv.io/api/v1/uv?lat=45.465051&lng=9.094615&alt=0` : {"error":{"name":"MongoError","message":"user is not allowed to do action [find] on [openuv-billing.requests]","ok":0,"errmsg":"user is not allowed to do action [find] on [openuv-billing.requests]","code":8000,"codeName":"AtlasError"}}`

If I start again (disabling and re-enabling the API via PaperUI), everything becomes green and online.

Expected Behavior

the binding should stay online

Current Behavior

the binding suddenly stops working. it needs a forced restart to go back online

Steps to Reproduce (for Bugs)

sometimes it happens, especially during the night

Your Environment

• Version used: 3.3.0 M6
• Environment name and version: openHABian
• Operating System and version: debian "buster"

[openhab-bot]

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/openuv-invalid-json-received/136556/4

[lolodomo]

You mean MainUI, not PaperUI which does not exist anymore in v3.x.

[nesys]

exactly, apologies for that :)

[nesys]

Update: now also during the day, and it is not recovering, even disabling and re-enabling the binding. It saying "User with API key not found" ... but the key is correct

[clinique]

Update: now also during the day, and it is not recovering, even disabling and re-enabling the binding. It saying "User with API key not found" ... but the key is correct

Yes, have it also currently. There is an error on OpenUV api side.

[nesys]

Update: now also during the day, and it is not recovering, even disabling and re-enabling the binding. It saying "User with API key not found" ... but the key is correct

Yes, have it also currently. There is an error on OpenUV api side.

that happened sometimes also in the past ...

[nesys]

btw this binding is becoming a nightmare for you, @clinique ... I'm really sorry for that, but thanks for your support

[clinique]

Don't bother, I've seen worst nightmares :) This one will be quite easy to fix.

[lolodomo]

Can we close the issue now?