Howto do a Raspee (Conbee II) installation?
@quotschmacher said in Howto do a Raspee (Conbee II) installation?:
Hi @quotschmacher,
I used the same way (with the ‘stable’ version in No. 3), but as I wrote, by saying ‘sudo apt install deconz’, the mentioned error occured.
After that I spend some time on finding more knowledge and also tested the way form kosta, which ended also then with an error message.
Maybe additionally: I first installed the plugin and also plugged the ConBee stick.
Might that be the problem?
firast of all: to get the api key you can type this:
curl --header "Content-Type: application/json" --request POST --data '{"devicetype":"pimatic"}' http://192.168.188.21:8080/api
where 192.168.188.21:8080 is the ip + port from your deconz webinterface.
here is history output from the raspberry, the steps regarding deconz:
10 sudo gpasswd -a $USER dialout
11 wget -O - http://phoscon.de/apt/deconz.pub.key | sudo apt-key add -
12 sudo sh -c "echo 'deb http://phoscon.de/apt/deconz \
13 $(lsb_release -cs) main' > \
14 /etc/apt/sources.list.d/deconz.list"
15 sudo apt update
16 sudo apt install deconz -y
17 sudo systemctl enable deconz
18 sudo nano /lib/systemd/system/deconz.service
everything under debian stretch.
line 18 only was necessary as i wanted to change the port from the webinterface
Sorry, doesn’t work.
Befor I tried, I set the port in the raspee plugin config to 8080 and restarted pimatic.
The IP adress ist the adress from the pimatic where the ConBee is plugged.
Look:
pi@raspberrypi:~ $ curl --header "Content-Type: application/json" --request POST --data '{"devicetype":"pimatic"}' http://192.168.188.62:8080/api
curl: (7) Failed to connect to 192.168.188.62 port 8080: Verbindungsaufbau abgelehnt
EDIT: I tried the same with port 80, the same port as my pimatic, and then I got an ‘Unauthorized’
In reference to the rest:
I did exactly the same, including reboot after line 10, as it is said on the web page.
I tried now sudo apt install deconz with -y, but the result stays the same:
pi@raspberrypi:~ $ sudo apt install deconz -y
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
E: Paket deconz kann nicht gefunden werden.
… and on Stretch
You receive the api key from deconz. So with no deconz running no api key.
Did you do a apt Update?
ok, beginners mistake sorry …
have been in the home/pi directory during the installation …
changed to root/ … and installation worked well
ConBee stick can be reached and configured via browser now
Next challenges I will look for the next days:
… we will see …
@quotschmacher said in Howto do a Raspee (Conbee II) installation?:
Did you do a apt Update?
Yes I did, the mistake was an other one…as I wrote.
… but as I also wrote, besides getting the key during the installation, I fear I have to put in also something into the plugin configuration and currently I have no clue where to get it, as I didn’t find a key in the WEB frontend of the ConBee stick.
There are some other mistakes…
The key only can be obtained if you allow third Party Apps in the Web frontend (phoscon app).
…hmhm, I found the function, but it can not be configurated to allow that in general!?
There is only a button ‘App connection’, then you can connect for 60 seconds and then it closes again!?
How shall I get a key by that?
EDIT: I guess I found it … let me test
EDIT2: No, not successful. I thought I can do it by the button ‘Configure with Phoscon App’ in the WLAN menue. But after setting the WLAN data, it says that something has gon wrong and falls back twice to the former configuration 
… I have to stop now a get some sleep, let’s proceed tomorrow.
Thanks for now @quotschmacher
@pedder said in Howto do a Raspee (Conbee II) installation?:
ok, beginners mistake sorry …
have been in the home/pi directory during the installation …
changed to root/ … and installation worked well
that for sure was not the mistake. in the steps specified at https://phoscon.de/de/conbee/install#raspbian the path doesn’t matter at all. something else might be wrong. what raspbian version are you using?
for the api-key: you allow the app connection for 60 seconds. this is yout window where you can perform the curl-prompt posted earlier. this way you get the api-key and with that key you can connect longer than 60 seconds. this is how i got it working.
I‘m running Stretch, installed by the Noobs package
The API key tipp I will test in the evening, thanks!
I think that is not described somewhere!?
@pedder said in Howto do a Raspee (Conbee II) installation?:
I think that is not described somewhere!?
i didn’t find it described like this. i collect the parts neccessary and put them together by myself. but the api-key could be in the plug-in description.
edit: at least a link to this http://dresden-elektronik.github.io/deconz-rest-doc/getting_started/ would be helpful
@Pedder @quotschmacher
Perhaps the following is also helpful…
https://forum.pimatic.org/topic/4254/new-plugin-pimatic-raspbee/64
@Fabian looks like you are right. having a look in the code of the plugin it shoul request the key itself.
i have created two wiki articles which describe the initial setup.
how to install deconz api (old way without repo) and some other usefull hints
for GUI mode, change default port etc.
-> https://github.com/treban/pimatic-raspbee/wiki/Installation-of-deCONZ
connect the plugin with the api:
-> https://github.com/treban/pimatic-raspbee/wiki/Connect-the-raspbee-plugin-to-deconz
if deconz is running, unlock the gateway for 60s and make a device discovery in pimatic.
the plugin automatically creates a key
Hi and thanks for all your support ,
That is really a great thing in that forum 
So, the API-key generation works and was that easy!!!
But why are all these important hints not linked in the plugin docu on the pimatic homepage?
https://pimatic.org/plugins/pimatic-raspbee/
Sorry, but for users as me, it is impossible to find all these dispersed information and in the end follow up in the right sequence.
As I thought this is only another ‘installation’, I would never have searched on Github for respective info.
So as it works now, but I’m not quite sure what steps I really did to get there, I will do another test with a fresh SD card image on the Test Pimatic as following:
PS.
But that may take some additional days as I’m now struggling to learn my OSRAM Plugs to the Phoscon App ….
I ran the scan now 5-6 times, while switching the plugs on and off, but they are not registered
nice that it works now.
the git readme already contains a link to the wiki.
Since only a new package version updates the pimatic plugins page, this is unfortunately missing there.
i will release a new version soon.
(with new readme)
@pedder said in Howto do a Raspee (Conbee II) installation?:
But that may take some additional days as I’m now struggling to learn my OSRAM Plugs to the Phoscon App ….
I ran the scan now 5-6 times, while switching the plugs on and off, but they are not registered
Strange, never had issues while pairing a osram smart+ plug. Even in daily use they are very stable and working without any problems within my system.
… well that is really frustrating here.
I started my Test pimatic an hour ago, which worked properly yesterday evening, but pimatic wasn’t able to reconnect to the stick any longer. I got error messages every 30 seconds:
error [pimatic-raspbee]: Connection could not be establised
error [pimatic-raspbee]: websocket keep alive error, try to reconnect
And the stick also wasn’t available via the phoscon WEB GUI any longer.
… reconfigured the plugin, tried another port, reinstalled the plugin, but nothing helps.
I then plugged the stick to my two Computers (Win7/10) and, … both responded that the just plugged in USB device has a problem … … which might also be the reason that I wasn’t able to bind my OSRAM plug to it yesterday.
So, it seems to be, that I’m the lucky one , who got 1 out of 1000 which has a problem in general and I will send it back …
… and additionally, the new stick will be send earliest on 23 of July
Isn’t that frustrating?
i had to send my conbee II back, too and the new one shall be there till friday. couldn’t connect to it anymore, even after firmware update and setting up the pi completely from scratch. but that gave me some time to get to know the deconz docker image - so the setup step isn’t required anymore.
Hmhm, I hope that they do not break too often …
