Thanks for your help. Obviously some things in phoscon are not correct. Phoscon runs in a proxmox instance. Until some time ago Proxmox ran on a Lenovo X200 in headless mode. Recently proxmox runs on an Intel NUC. Phoscon moved thereupon, too, without reinstallation. Possibly my problems were caused by this.
The json code, which is displayed to me with your help, seems to have some irregularities.
For example, I don’t get this displayed in pimatic.

32 config battery 100 duration 90 on true reachable true temperature 3000 ep 1 etag "d08373fac6d41dc1d546148ad0b9aa54" manufacturername "LUMI" modelid "lumi.sensor_motion.aq2" name "Pir-Kammer" state lastupdated "2019-06-08T13:34:03" presence false swversion "20170627" type "ZHAPresence" uniqueid "00:15:8d:00:02:73:28:96-01-0406"

And I can’t do anything with these next ones. But such or similar names are given to me during the device discovery.

40 config duration 60 on true reachable true etag "556031be6c28d733428a5060ec5ba901" manufacturername "Phoscon" modelid "PHOSCON_VPIR" name "VPIR Kammerlicht" state lastupdated "2019-06-02T07:28:08" presence false swversion "1.0" type "CLIPPresence" uniqueid "vpir-1559460425141" 41 config on true reachable true etag "556031be6c28d733428a5060ec5ba901" manufacturername "Phoscon" modelid "PHOSCON_FSM_STATE" name "FSM_STATE Kammerlicht" state lastupdated "2019-06-02T07:28:08" status 0 swversion "1.0" type "CLIPGenericStatus" uniqueid "fsm-state-1559460425141"

I can’t take over these strange devices in pimatic either. If I try it, then there is no device class.

Raspbee and Deconz and PimaticCrash