Cannot re-register UUID after deleting myopenHAB account

1

Hi,
I deleted my myopenHAB.org account but now I’m unable to re-register.
When trying to register with the same or even a different email address, I get the error:

UUID is already in use on another account.

However, I cannot log in either – so I assume the account deletion is stuck halfway.
Could someone please manually release my UUID from the system so I can register again?

UUID: 6bc2af1d-eb27-4179-8418-e8ece617bbbc

Thanks a lot in advance!

2

I can’t do that but you can generate a new UUID. Stop OH, delete $OH_USERDATA/uuid and $OH_USERDATA/openhabcloud/secret (maybe just move them somewhere else just in case). Then start OH. The openHAB Cloud Connector add-on will regenerate both files with new values.

You should be able to register with a new UUID.

3

Thanks a lot for the quick and helpful response!
That worked perfectly – I followed your instructions, generated a new UUID and secret, and was able to register a new account without any issues.

Really appreciate the support – openHAB community never disappoints! :raising_hands:

LG André

4

Hi again – I’ve successfully registered a new account with a new UUID and the connection shows as “Online”, but unfortunately the Access Token section is still missing on the /account page.

Could you please enable the token feature for my account manually? That would be amazing – thanks again for your help!

5

The Cloud Connector doesn’t use an access token. If you’ve created an access token, that’s local to your OH instance and has nothing to do with the Cloud Connector. As far as I know the cloud server doesn’t have any concept of an access token. Do you mean the API access token?

6

Yes, exactly… I want to create an HTTP request using Node-RED that checks whether my OpenHAB is ‘online’, and I want to use that to control a switch. For querying the myopenhab.org site, I need the Bearer token — or am I thinking about this the wrong way? Is there a better method?

7

As far as I know the openhab cloud server doesn’t support bearer tokens. But you can use basic auth.

However, if you’ve disabled the implicit user role in your OH itself, you’ll need to authenticate to both, which probably means you need create an auth token for OH. Then you’l use basic auth to authenticate to the cloud server and the auth token to authenticate to your OH instance itself.

There is an option to add an implicit user role only to certain IPs or IP ranges. Since the cloud connector communicates with OH from localhost you can probably add localhost to that list and foregoe the auth token entirely.

I’ve never set anything like this up before so :person_shrugging: .

But assuming your Node-Red is running on the same network as your OH instance, you don’t need the cloud server to see if OH is online. You can just access it directly using basic auth.

8

I’ve set it up that way now, and it’s working perfectly with Node-RED! many thanks!!!
I’m also happy to share my Node-RED code if anyone’s interested.