Ein Beispiel sind die Tuya Temperatur/Feuchtesensoren:
Das deConz logging zeigt, daß jeweils zwei Events geschickt werden:
debug_deconz.htm:11 {"attr":{"id":"76","lastannounced":null,"lastseen":"2023-07-13T16:57Z","manufacturername":"_TZE200_a8sdabtg","modelid":"TS0601","name":"Temperaturregler","swversion":"1.0.2","type":"ZHAHumidity","uniqueid":"a4:c1:38:35:7b:18:6b:9d-01-0405"},"e":"changed","id":"76","r":"sensors","t":"event","uniqueid":"a4:c1:38:35:7b:18:6b:9d-01-0405"}
debug_deconz.htm:11 {"attr":{"id":"77","lastannounced":null,"lastseen":"2023-07-13T16:57Z","manufacturername":"_TZE200_a8sdabtg","modelid":"TS0601","name":"Temperature 77","swversion":"1.0.2","type":"ZHATemperature","uniqueid":"a4:c1:38:35:7b:18:6b:9d-01-0402"},"e":"changed","id":"77","r":"sensors","t":"event","uniqueid":"a4:c1:38:35:7b:18:6b:9d-01-0402"}
Deswegen dachte ich, daß deConz das Problem verursacht. Im deConz Forum bekam ich dann folgende Aussage:
*The api should show 2 entities in the /sensor endpoint, one for humidity and one for temperature. They share the same unique id, up to the point of which endpoint. In this case the 05 and 02.
In your log part that is clearly visible.
Long story short, phoscon shows it as one device and phoscon uses the same api as iobroker does. In your case you need to check with the iobroker dev.*
Nun zur eigentlichen Frage - gibt es in ioBroker die Möglichkeit eine Art von 'skiplist' einzurichten mit IDs die ignoriert (kein Objekt wird angelegt) oder ausgeblendet werden?