Question on pimatic-aqara plugin: Which gateway version?

---

black linux magic its a symlink
lrwxrwxrwx 1 root root 34 Okt 3 21:18 /etc/systemd/system/multi-user.target.wants/deconz.service -> /lib/systemd/system/deconz.service

ip address is in your case 127.0.0.1
and port is the port you give deconz

@kosta said in Question on pimatic-aqara plugin: Which gateway version?:

127.0.0.1

Thanx
The raspbee plugin documentation unfortunately does not have this information. Maybe it would be worth adding this to make it usable by a broader audience.

@kosta

next question: there is no information in the plugin documentation on the api key. during first usage of the device auto discovery function there was an entry that this api key is generated and indeed, after the discovery ended, checking the plugin shows an entry in this field

unfortunately starting the auto discovery function again does not show a raspee entry on the top (along with i.e. homeduino and tradfri) and the sensors I am trying to pair are not detected.

any guidance?

first of all deconz has to be configured independently. you must pair the devices in the deconz gui.
After that you can discover the devices with pimatic.

@kosta

Thanx kosta, another valuable little information maybe worth mentioning in the Plugin description?

So I managed to setup everything, apparently the API Key is generated automatically when doing the first Auto Discovery (maybe also worth mentioning in the Plugin Documentation)

I was able to pair the Multisensor sucessfully and also to incorporate it into my pimatic. Very Nice

I also have a contact /door / window Sensor and was once able to pair it via the Phoscon App, bute before I knew from your last tip that this is necessary to add it in pimatic, I deleted the sensor and now I am not able to pair it anymore

The LED blinking code suggests that the pairing was successfuly but the Phoscon GUI does not show the confirmation.

I would like to check if there is any “dead” entry in the device list via the Deconz GUI but I am unable to start it.

I logged on via RDP to the Raspian Desktop and in the Startmenu under “Development” there is an entry deCONZ.

I have re-enabled and re started the deconz GUI (which was disabled as part of the guideline) by using
sudo systemctl enable deconz-gui
sudo systemctl start deconz-gui

but when clicking on the Shortcut nothing happens

Any help to start the DECONZ GUI would be highly appreciated.

@cherberg I’m having the same trouble with opening the gui via rdp. There has been a comment on git that the problem is related to the rdp connection which is not showing desktop 0 or something else named x11.
https://github.com/dresden-elektronik/deconz-rest-plugin/issues/343

Sometimes it is working for me when I first stop deconz headless service and then start deconz-gui service and then start deconz.

$ sudo systemctl disable deconz
$ sudo systemctl stop deconz

$ sudo systemctl enable deconz-gui
$ sudo systemctl start deconz-gui

$ sudo deCONZ 

But I’m also running into some problems when starting deCONZ gui without vnc or rdp. I really don’t know why and I’m also interested in a reliable solution.

See also here:
https://forum.pimatic.org/topic/4254/new-plugin-pimatic-raspbee/68

The problem has also been discussed there…

@fabian

Thanx Fabian when trying what you suggest after the last command I get:

No protocol specified
QXcbConnection: Could not connect to display :10.0
Abgebrochen

which suggests that this may indeed be an RDP Display issue. I will try and connect the Raspberry directly to a display.

Just ordered a cable to connect the HDMI output to the DVI Input of an old Monitor.

@cherberg just give it a try. But as I have already mentioned the problem isn’t reliably solved by this. I had also some connecting problems to the raspbee module even though I was using a monitor.