V 2.30.2 myapp nicht mehr möglich?

Phoscon App General Support
1

Hallo,

mit der Version:

deconz:armhf (2.22.02-raspbian-buster-stable)

konnte ich, nachdem ich Hamburger Menu => Gateway => Advanced => Authenticate APP ausgewählt hatte, mit

curl -X POST -H “Content-Type: application/json” -d ‘{“devicetype”: “myapp”}’ http://localhost:80/api

einen ‘username’ bekommen zB
[{“success”:{“username”:“AAA3C23***”}}]

mit dem ich dann Bosch Thermostat II integrieren konnte.

mit v 2.30.2 bekomme ich lediglich:

[{“error”:{“address”:“/”,“description”:“unauthorized user”,“type”:1}}]

Was mache ich falsch?

Danke,

2

With the same request ?

On my side I m using the request

curl http://IP:PORT/api/ -X POST -d '{"devicetype": "TestKey"}

You can look the http code returned too, if you need to unlock the gateway you have a 403 error code.

3

I am doing the exact same thing in V 2.30.2 that I successfully did in V2.22.02

Is obtaining a username / unlocking the gateway still supported?

without Authenticate app pressed I get:
pi@rpj01:~ $ curl -X POST -H “Content-Type: application/json” -d ‘{“devicetype”: “myapp”}’ -i http://localhost:80/api
HTTP/1.1 403 Forbidden
Access-Control-Allow-Origin: *
Content-Type: application/json; charset=utf-8
Content-Length: 70
[{“error”:{“address”:“/”,“description”:“unauthorized user”,“type”:1}}]

this is the response regardless if am in the 60 second “Authenticate App” mode or.
Again: the very same thing worked today on the version I had installed before.

4

Ok so have made some tests, the previous request was not working (probably a typo)
But this one is working for me

curl -X POST http://192.168.1.1:80/api/ -d '{"devicetype": "testkey"}'

And I have a different error message without authentication

[{"error":{"address":"/","description":"link button not pressed","type":101}}]

5

Thank you so much for this example URL. It did the trick.
In the end it seems that I could connect the BOSCH Thermostat with the firmware 344 to Deconz 2.30.2 in the Thermostat menu.

FWIW here is what ended working for me today on my rPI:

I did

 curl http://localhost:80/api/ -X POST  -d '{"devicetype": "TestKey"}

and got

[{"success":{"username":"71A2B7F139"}}]

interestingly BEFORE I had enabled the authentication mode in the DeCONZ app.
That step seems not to be needed anymore.

I obtained the Install Code (BOSCH_INSTALLCODE ) and ZigBee EUI-64 (from the Battery lid.
Thanks gpt for doing such a good job in OCR. Really beats typing those numbers, and
having to wonder if it fails because I can’t type or read properly.

It did

curl -X PUT -H "Content-Type: application/json"     -d '{"installcode": "BOSCH_INSTALLCODE"}'     http://localhost:80/api/71A2B7F139/devices/BOSCH_EUI-64/installcode

and got

[{"success":{"installcode":....

I then went to the UI and did go to Thermostats and clicked on Add thermostat.
During the 3 minute period I inserted the batteries into the BOSCH Thermostat II
while I was holding down the front (and only) button. It connected to DeConz.

This was not possible with my old app version. I had Thermostat with Firmware
Version 325, but they all died after a couple of months because of an hardware error.
The first replacement I got runs Bosch firmware 344.

Thanks so much for providing me with the proper username request curl program.
Feels like that the syntax for that has changed with deconz versions.

Problem solved. Now I hope that the new Bosch devices do better in terms of hardware
reliability.

Thank you for your help.

6

Perhaps not needed if you are on same machine (localhost)

It’s not from your bosh TRV firmware ? It’s possible to update them (Firmware are public) ?
Because lot of users have problem with this device.

7

Bosch Firmware 325 was working with pre V2.30.2 phoscon and probably V2.30.2,
could not test since I have no more functional 325 Thermostats left. They all died a hardware death after a couple of months.

Bosch Firmware 344 is NOT working with pre V2.30.2 phoscon

Hence the upgrade.

which DID CHANGE the onboarding mechanism as described here.

Pre V2.30.2 you had to enable auth to get a user name even if you are on the same machine.

1 Like