How to set the Client Id

[WifiSen]

Hi

I'm using node red on a raspi and want to connect to my BSHC. The search does not work, but can ping the BSHC from my raspi. I can enter the IP manually but I can not enter an ID. When I try to pair anyway it says some information is missing.

Any hints? And what is the ID anyway?

Cheers
Wfif

[hxmelab]

Hi WifiSen,

the client id is auto generated and should fill the read only field of the shc configuration automatically.

If this is not working for you, please check for updates and check the logs. Did you get an error?

Kind regards
Phil

[WifiSen]

Hi Phil

I checked the logfiles and all I see are some entries when the bosch node is loaded. Nothing else. I expected to see at least an error message when scanning for the BSHC fails, but nothing.

How should the normal procedure look like after I have entered the IP manually? Just press Enter? How do I start the connection to the BSHC?

Cheers,
Wifi

[hxmelab]

When opening the configuration window for adding a new shc-config a message appears on the top of your window: "Generating new client data..." followed by "Generated!". This procedure is not only generating an id it is also generating a key and a certificate to communicate with the SHC. All the information will be posted with the pairing procedure. Hence, if these data is not getting generated it also won't work by just adding an id, because there are more information missing.

What Node-RED version and what version of the shc-nodes are you using?

[WifiSen]

Hi

When I open the window then the message "Generating new client data ..." appears but is followed by 2 "Not found" messages.

I use RedMatic 5.3.10 (https://github.com/rdmtc/RedMatic) which is node-red V1.0.3 togehther with shc-nodes V0.2.15.

[hxmelab]

To generate the client data two requests to the backend are necessary. It seems that the frontend is not able to get them.

Could you please check the requests and the output of the console?

[WifiSen]

That's what I see in the chrome console.

[hxmelab]

Ok, this should be fixed with version 0.2.16. Thank you WifiSen for reporting and tribute to hobbyquaker who solves the bug.

[WifiSen]

Glad I could help. When can I expect 0.2.16?

[hxmelab]

It's available now...

[WifiSen]

... and it works!

Thank you very much for the quick response. Gut gemacht!

Grüße,
Wifi