Release pimatic-raspbee@0.1.6
@bertreb said in Release pimatic-raspbee@0.1.6:
You could compare discovered sensor id’s with the phoscon values and determine the conversion
Hmhm, but that is exactly the problem, in Phoscon aren’t any ids.
So if they are in, could you provide a hint where I can find them?
I got your point, but I might be too blind to find the ids in the web-frontend.
I never saw ids or other parameters in Phoscon.
@bertreb said in Release pimatic-raspbee@0.1.6:
he screenshot above with the hex ids,
ahh! 
the screen shoot is from the deCONZ gui, not from the Phoscon app
I will check this then directly in deCONZ …
Thanks for now!
That didn’t lead to a result.
All the IDs and the values behind are completely the same in deconz amongst the three plugs. They look like triplets.
… I close for today and will test a complete new pairing tomorrow.
You can configure the sensor ID manually, but if the API isnt providing the sensor / data you wont get any info.
You can check if the sensor data of the plug is available with the browser url "http://<ip address deconz>:<port>/api/<api key>/sensors"
Check if the plug is in the list. If its in the list, the sensor ID is the key value of the sensor. Every sensor record starts with “<sensor ID >”:{“config”: …
If its not in the list, adding it manually doesn’t help, the problem is in Deconz.
@bertreb said in Release pimatic-raspbee@0.1.6:
If its not in the list, adding it manually doesn’t help, the problem is in Deconz.
Yep, I meanwhile did a another test while using the deconz integration in my ioBroker instance and there I got the same/similiar issues with this device.
(https://github.com/dresden-elektronik/deconz-rest-plugin/issues/3788)
Good thing there was, that ioBroker clearly shows device’s and sensor’s IDs directly in the web frontend in the objects section. Here I could verify (additionally), that what is delivered from deCONZ is waste, allthough in the deCONZ gui the values are shown propperly. I guess it’s a problem with the rest-api, or with the general deconz-pairing of these devices.
But at least only, when this type of device is paired a second time and also not necessarily to the same deconz. Maybe it would have to be reset via the original Tuya/Blitzwolf Gateway to work propperly in another environment!?
Hi again,
at least the one nasty plug is now also running propperly incl. all measurements (voltage, current, power, consumption).
I never saw such a wondering behaviour with a ZigBee device, but in the end it worked.
If one might run into similiar issues with the Tuya/Blitzwolf BW-SHP13, please have a look here:
https://github.com/dresden-elektronik/deconz-rest-plugin/issues/3788
One have to scroll down to the very bottom… 
I refreshed my deconz to variant 2.07.01/8.12.2020 and the firmware to adaptation 26660700.
Since I did that I get Bad solicitation each time I attempt to control my ikea blinds.
Every one of my controllers and movement sensors are not revealing their status.
The clever thing is, the ikea dazzle reports when I physically press the catch to open or close it on the blind,but in the event that I press anything in pimatic, I simply get terrible solicitation brief. http://liverpoolsmanandvanservice.co.uk/
Is it possible to connect two raspbee/ deconz instances to Pimatic. In Dmoticz it is, but since Pimatic is (still) my primary system, it would be nice if this is possible. Both deconz controllers are accessible in my home network. One is in the house and one in the barn, which is too far away to create a mesh network for one deconz controller.
