SNZB-02 fails to send temperature msTemperatureMeasurement failed (AREQ - ZDO - bindRsp after 10000ms)

[tvrulesme]

Debug info

Zigbee2MQTT version: version 1.21.2 (commit #44922120) Adapter hardware: CC2531 Adapter firmware version: CC2531_DEFAULT_20201127

Supported device SNZB-02 pairs successfully but shows the following error when it attempts to broadcast a temperature reading Zigbee2MQTT:error 2021-10-03 10:23:10: Configure failed: Error: Bind 0x00124b0022cf704d/1 msTemperatureMeasurement from '0x00124b00193691c1/1' failed (AREQ - ZDO - bindRsp after 10000ms)

configuration.yaml:

homeassistant: false
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://192.168.0.2
  user: mqtt_user
  password: Penguin1
serial:
  port: /dev/ttyACM0
devices:
  '0x00124b0022cf704d':
    friendly_name: '01-humidity'
    retain: true

logs:

Zigbee2MQTT:info  2021-10-03 10:12:49: Starting Zigbee2MQTT version 1.21.2 (commit #44922120)
Zigbee2MQTT:info  2021-10-03 10:12:49: Starting zigbee-herdsman (0.13.149)
Zigbee2MQTT:info  2021-10-03 10:12:58: zigbee-herdsman started (restored)
Zigbee2MQTT:info  2021-10-03 10:12:58: Coordinator firmware version: '{"meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20201127,"transportrev":2},"type":"zStack12"}'
Zigbee2MQTT:info  2021-10-03 10:12:58: Currently 0 devices are joined:
.......

info  2021-10-03 10:18:39: Device '0x00124b0022cf704d' joined
info  2021-10-03 10:18:39: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x00124b0022cf704d","ieee_address":"0x00124b0022cf704d"},"type":"device_joined"}'
info  2021-10-03 10:18:39: Starting interview of '0x00124b0022cf704d'
info  2021-10-03 10:18:39: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x00124b0022cf704d","ieee_address":"0x00124b0022cf704d","status":"started"},"type":"device_interview"}'
info  2021-10-03 10:18:39: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"friendly_name":"0x00124b0022cf704d"},"type":"device_connected"}'
info  2021-10-03 10:18:39: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_started","meta":{"friendly_name":"0x00124b0022cf704d"},"type":"pairing"}'
info  2021-10-03 10:18:40: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x00124b0022cf704d","ieee_address":"0x00124b0022cf704d"},"type":"device_announce"}'
info  2021-10-03 10:18:40: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"0x00124b0022cf704d"},"type":"device_announced"}'
info  2021-10-03 10:18:40: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":[],"type":"groups"}'
info  2021-10-03 10:18:40: MQTT publish: topic 'zigbee2mqtt/bridge/config/devices', payload '[{"dateCode":"20201127","friendly_name":"Coordinator","ieeeAddr":"0x00124b00193691c1","lastSeen":1633252720100,"networkAddress":0,"softwareBuildID":"zStack12","type":"Coordinator"},{"description":"-","friendly_name":"0x00124b0022cf704d","ieeeAddr":"0x00124b0022cf704d","lastSeen":1633252720050,"networkAddress":59037,"type":"Unknown","vendor":"-"}]'
info  2021-10-03 10:18:40: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":[{"dateCode":"20201127","friendly_name":"Coordinator","ieeeAddr":"0x00124b00193691c1","lastSeen":1633252720166,"networkAddress":0,"softwareBuildID":"zStack12","type":"Coordinator"},{"description":"-","friendly_name":"0x00124b0022cf704d","ieeeAddr":"0x00124b0022cf704d","lastSeen":1633252720050,"manufacturerID":0,"networkAddress":59037,"type":"EndDevice","vendor":"-"}],"type":"devices"}'
info  2021-10-03 10:18:45: Successfully interviewed '0x00124b0022cf704d', device has successfully been paired
info  2021-10-03 10:18:45: Device '0x00124b0022cf704d' is supported, identified as: SONOFF Temperature and humidity sensor (SNZB-02)
info  2021-10-03 10:18:45: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"definition":{"description":"Temperature and humidity sensor","exposes":[{"access":1,"description":"Remaining battery in %","name":"battery","property":"battery","type":"numeric","unit":"%","value_max":100,"value_min":0},{"access":1,"description":"Measured temperature value","name":"temperature","property":"temperature","type":"numeric","unit":"°C"},{"access":1,"description":"Measured relative humidity","name":"humidity","property":"humidity","type":"numeric","unit":"%"},{"access":1,"description":"Voltage of the battery in millivolts","name":"voltage","property":"voltage","type":"numeric","unit":"mV"},{"access":1,"description":"Link quality (signal strength)","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"SNZB-02","supports_ota":false,"vendor":"SONOFF"},"friendly_name":"0x00124b0022cf704d","ieee_address":"0x00124b0022cf704d","status":"successful","supported":true},"type":"device_interview"}'
info  2021-10-03 10:18:45: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_successful","meta":{"description":"Temperature and humidity sensor","friendly_name":"0x00124b0022cf704d","model":"SNZB-02","supported":true,"vendor":"SONOFF"},"type":"pairing"}'
info  2021-10-03 10:18:45: Changed device specific options of '0x00124b0022cf704d' ({"retain":true})

......

Zigbee2MQTT:info  2021-10-03 10:23:00: Device '01-humidity' joined
Zigbee2MQTT:info  2021-10-03 10:23:00: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"01-humidity","ieee_address":"0x00124b0022cf704d"},"type":"device_joined"}'
Zigbee2MQTT:info  2021-10-03 10:23:00: Configuring '01-humidity'
Zigbee2MQTT:info  2021-10-03 10:23:00: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"friendly_name":"01-humidity"},"type":"device_connected"}'
Zigbee2MQTT:info  2021-10-03 10:23:00: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"01-humidity","ieee_address":"0x00124b0022cf704d"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-10-03 10:23:00: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"01-humidity"},"type":"device_announced"}'
Zigbee2MQTT:info  2021-10-03 10:23:00: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":[],"type":"groups"}'
Zigbee2MQTT:info  2021-10-03 10:23:00: MQTT publish: topic 'zigbee2mqtt/bridge/config/devices', payload '[{"dateCode":"20201127","friendly_name":"Coordinator","ieeeAddr":"0x00124b00193691c1","lastSeen":1633252980641,"networkAddress":0,"softwareBuildID":"zStack12","type":"Coordinator"},{"dateCode":"20201026","description":"Temperature and humidity sensor","friendly_name":"01-humidity","hardwareVersion":1,"ieeeAddr":"0x00124b0022cf704d","lastSeen":1633252980584,"manufacturerID":0,"manufacturerName":"eWeLink","model":"SNZB-02","modelID":"TH01","networkAddress":35923,"powerSource":"Battery","type":"EndDevice","vendor":"SONOFF"}]'
Zigbee2MQTT:info  2021-10-03 10:23:00: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":[{"dateCode":"20201127","friendly_name":"Coordinator","ieeeAddr":"0x00124b00193691c1","lastSeen":1633252980659,"networkAddress":0,"softwareBuildID":"zStack12","type":"Coordinator"},{"dateCode":"20201026","description":"Temperature and humidity sensor","friendly_name":"01-humidity","hardwareVersion":1,"ieeeAddr":"0x00124b0022cf704d","lastSeen":1633252980584,"manufacturerID":0,"manufacturerName":"eWeLink","model":"SNZB-02","modelID":"TH01","networkAddress":35923,"powerSource":"Battery","type":"EndDevice","vendor":"SONOFF"}],"type":"devices"}'
Zigbee2MQTT:error 2021-10-03 10:23:10: Configure failed: Error: Bind 0x00124b0022cf704d/1 msTemperatureMeasurement from '0x00124b00193691c1/1' failed (AREQ - ZDO - bindRsp after 10000ms)
Zigbee2MQTT:info  2021-10-03 10:23:10: Successfully configured '01-humidity'
Zigbee2MQTT:info  2021-10-03 10:27:01: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'offline'

[domneedham]

Hi everyone

fabgrenier took me on the road.

I had try every procedures from web interface for re-pairing without success.

But if i restart zigbee2mqtt just after deleting and before re-pairing it work !

Can confirm the exact same for me.

• pair device to z2m
• force delete device
• restart z2m
• pair again

Works perfectly after the above

[fabgrenier]

Hi guys, since my last post, I had the same problem again with a sensor which is a bit far from my network. When it stops sending data, it never sends again despite trying to force pairing.

I ran into a simpler solution, just restart mosquito then zigbee2mqtt and the faulty device come back as normal. I didn't need to force remove from Domoticz.

[ndevenish]

After many attempts with 1.23 (with and without wiping everything except initial configuration), I downgraded to 1.20, (without wiping the database) which had the same error, and then 1.19 (after wiping the database)- which worked first time. I had tried several other of the suggestions in this thread, including maxbaus' suggestion.

This is my very first self-setup Zigbee device, which I bought with a CC2531 (I have hue bridge so probably background communication on separate network) so it's connecting directly to the CC2531.

[ndevenish]

So, I did some diving into this, and ran a bisect (log). Each stage in the bisect ran the docker build, started from a clear configuration.yaml (no devices, network: GENERATE), and I held down the pairing button until the light flashed and the zigbee2mqtt log showed activity. Sometimes I needed to pair twice, because (only on commits where it was broken), it sometimes didn't load even recognise the battery/linkquality/voltage fields.

The last (untagged) commit where it works (repeatedly tested) is https://github.com/Koenkk/zigbee2mqtt/commit/27b36b316c5fe5d23abfd083bee4ffc1b43070b9. The bisect reports it's in the next three commits: https://github.com/Koenkk/zigbee2mqtt/compare/27b36b316c5fe5d23abfd083bee4ffc1b43070b9...9f12ef7370fd75362b890f1cf2429a8faf96f1a1. Obviously my suspicion falls on https://github.com/Koenkk/zigbee2mqtt/commit/9f12ef7370fd75362b890f1cf2429a8faf96f1a1, "Update zigbee-herdsman to 0.13.146", because it seems unlikely to be caused by TypeScript restructuring (which causes the build to fail before the herdsman update is applied).

However... the change to zigbee-herdsman in the public tag for those versions is.... not large: https://github.com/Koenkk/zigbee-herdsman/compare/v0.13.145...v0.13.146. The node-version at setup changed, and Device.meta was changed from private to public. Unfortunately, this is where the trail has run cold for me, because I don't know any of the cascading implications from either of those changes that might explain this error.

In any case, this implies that 1.21.1 is the last release where this worked; and it seems to work well for me, and pairs properly. (Edit: When I start from a clean configuration. Have not investigated what combination of removal might work).

Edit2: I've also seen this error crop up when attempting to reconfigure the device when it's sitting nearly out of range. But a re-pair worked instantly without clearing anything in zigbee2mqtt manually.

[sanyafifa]

Thank you @ndevenish ! downgraded to 1.21.1. Cleared all devices (copied the database file) Paired my snzb-02 and it worked!

[jjromannet]

I hit this issue few days ago when tried to setup 3 of my SNZB-02 devices (all purchased as a single order from single supplier). I only had coordinator in my network which is USB stick CC2531. I read all comments in both issues here but nothing helped - SNZB-02s were only reporting battery level at pairing time and never actually actively send any message to coordinator. I tried hitting reconfigure along with pressing button at various frequencies, force remove devices and add them back, remove battery etc. For this purpose i was using device A & B, device C was only paired once and I did not touch it.

From reading some comments here I concluded that people have more luck if there is router in the network. My another suspicion was that newer firmware (20201026) on SNZB-02 that i have is somehow incompatible. I purchased 2ch tuya switch device that is also acting as router and I gave it another go today. Today i had a bit more luck (it may be coincidence or indeed adding router to the network helped). Yet device A is not even reporting battery level right now and appears broken in the frontend - my working assumption is that I drain its batter during my tries last week. Device B started to report temperature and battery level (no humidity) only after i successfully reconfigured and set maximum reporting value for temperature to 60 (required frequent button presses). Device C - that i never tried to reconfigure before (only paired) - Today i only pressed reconfigure with default values T=> min: 5, max: 1800, H => min: 10, max 3600 - then it started to report both T&H

Another issue (not sure if related) is that "Last Seen" is always set to N/A even thought 2 out of 3 devices actually sending data to coordinator.

My set up it to run standalone (without HA) zigbee2mqtt as a docker container with following versions:

Starting Zigbee2MQTT version 1.23.0 (commit #6ea61ba)
Starting zigbee-herdsman (0.14.10)
Coordinator firmware version: '{"meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20201127,"transportrev":2},"type":"zStack12"}'

SNZB-02 firmware versions: 20201026 Linux kernel: 5.13.19-4

Attaching extracts from DB for all three devices db-extract.zip

I need to park the project for next two weeks. My next steps:

1. Test battery and order replacement
2. Test version 1.21.1
3. Try to understand what is interview and somehow force two remaining devices to complete it

[ndevenish]

Try to understand what is interview and somehow force two remaining devices to complete it

Assuming that it’s not an easily traceable software issue, what would be required to properly diagnose this on the hardware side - sniffing the general packets was mentioned earlier, is that what would be definitive? (Which would presumably require buying a second coordinator and custom flashing)

[linker3000]

I've also downgraded to 1.21.1 and the SNZB-02 has been working solid for a week now.

[danieldid]

I'm facing exactly the same issue with 1.21.1 through 1.23.

The error thrown in the logs: Configure failed: Error: Bind 0x00124b00245ce94c/1 msTemperatureMeasurement from '0x00212effff07710a/1' failed (waiting for response TIMEOUT)

I have two Sonoff SNZB-02 from the same delivery. One is working like a charm. The other one is always having trouble after a couple of days. Usually removing and pairing helped out so far. Unfortunately this doesn't work anymore.

My setup:

• zigbee2mqtt@1.23
• conbee@0x26660700

I'm running everything in docker on a raspberry pi.

[jjromannet]

I downgraded to 1.21.1 and all of my SNZB-02s work now (even without router in the network). At first when i only changed version of image in docker-compose to koenkk/zigbee2mqtt:1.21.1 and restarted with forced build it still was not working. I deleted all files apart from docker-compose and executed:

docker compose down --remove-orphans
docker compose rm
docker compose up -d

After this I paired all devices again without any issue.

One of the differences i see is that in version 1.21.1 default accuracy for all reading is set to 2 decimal places while in most recent version it was set to no precision point. I wonder whether precision set to 0 may cause SNZB-02 to misbehave.

This would explain why devices were not working after image downgrade - without repairing (during pairing new configuration is send). I will test this hypothesis after i am happy with result of 1.21.1 testing.

@danieldid

• zigbee2mqtt@1.23

Can you confirm if your SNZB-02 does not work when you set up version 1.21.1 from scratch?

[danieldid]

@jjromannet I can confirm this works with 1.21.1

By the way your temps are pretty hot (no offense! :-)) I'd like to have it cool

As with 1.23 the interview doesn't work and no temp and humidity is delivered

The difference (didn't check the changelogs!) between 1.21.1 and 1.23 is that you can't set the precission of the sensors under Settings (spezifisch) [german].

This is under 1.23

This is under 1.21.1

I'll have a look on this for a couple of days and will be reporting.

[danieldid]

Update after 2 days: Everything's running normal.

So it seems that downgrading was the solution or in other words in 1.23 something changed. I guess your thesis is correct @jjromannet. Must've been something with the accuracy. At least this is the only liable difference I can see.

BTW: I'm fairly new to docker and --remove-orphans did only work when using docker-compose up -d --remove-orphans. Should have read the flag first :-/ did reset some things (my complete influxdb datas were dropped).

[DarkPako84]

I have SONOFF SNZB-02 and the @maxbause solution didn't work for me. What I did is:

1. Enable joining new devices in z2m
2. Press and hold paring button on Sonoff device
3. Wait until z2m shows error with configuration
4. Go to Device section and click yellow reconfigure button next to the Sonoff device

Then device starts reporting data finally.

Finally i have find a great solution! Thanks!

[danieldid]

Post update - with 1.21.1 there's still no problem. Things are running normal.

[jjromannet]

@danieldid what do you mean by this? Did you setup your SNZB-02 with 1.21.1 and later upgraded zigbee2mqtt to more recent version - with SNZB-02 devices already paired?

[danieldid]

@jjromannet I set up everything with 1.21.1 in a docker environment. Then updated the image to the latest (back then) version 1.23. The problems mentioned here started with that version. I downgraded the docker image to 1.21.1 and started it with docker-compose up -d —remove-orphans (like mentioned previously).

Since then everything works seamlessly.

Can anyone confirm that with the latest version 1.24 this is working properly?

[linker3000]

No 1.24 does not work. I upgraded to 1.21.2 and the sensor still worked, but it stopped after a server reboot. I wanted 1.21.2 for Sonoff mains switch support and I had to revert to 1.21.1 then upgrade to 1.21.2 again.

On Tue, 15 Mar 2022, 21:39 Daniel Didusch, @.***> wrote:

@jjromannet https://github.com/jjromannet I set up everything with 1.21.1 in a docker environment. Then updated the image to the latest (back then) version 1.23. The problems mentioned here started with that version. I downgraded the docker image to 1.21.1 and started it with docker-compose up -d —remove-orphans (like mentioned previously).

Since then everything works seamlessly.

Can anyone confirm that with the latest version 1.24 this is working properly?

— Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/8971#issuecomment-1068497860, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEUHQXZ4JY7PLERKTB6XAM3VAD7QPANCNFSM5FHNI4WA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you commented.Message ID: @.***>

[dsduarte]

I had this problem again... I removed all my SNZB-02's and started Z2M with the key "avalability = false" on config.yaml and paired again and it was ok! I removed all my SNZB-02's again and started Z2M with "avalability = true" and paired again. Same error. Than, at last I removed all my SNZB-02's and started Z2M with "avalability = false" and paired again and it was ok!

I think we can declare "avalability = false" on devices.yaml only for the SNZB-02's.

[jjromannet]

I think i will join "give up on SNZB-02" camp. After playing with initial three devices (out of which I though i bricked two) I bought another 2 (so 5 devices in total here). Two new ones join the network without any issues with software version 1.21.1 (no luck with newer versions). After a week one of them stopped reporting any data - by pure guess i bought new CR2450 quality batteries - with their help all of devices (including ones I initially though were broken) started to work properly. Only info I was able to find about original batteries shipped with SNZB-02 device ("Newsun" brand here) are three opinion on popular online store each for 1 star out of 5 - complaining battery dies after a week.

Hint1: If you have any issues - start with new batteries - buy branded ones.

Unfortunately even with new batteries indicators are randomly dying.

PS: I just realized that reading of the sensor is also off. One of them is showing me 25.9 which is simply not possible (actual temp in this room is 22)

[matbech]

I'm seeing the same issue (error in log, no data is reported from device) using Zigbee2MQTT version 1.24.0, version 1.22.1 and with the dev branch as the original poster.

Also reconfigure (zigbee2mqtt/bridge/request/device/configure) does not solve my problem. The same error is reported:

info  2022-03-30 08:35:35: Starting Zigbee2MQTT version 1.24.0 (commit #7a2ddf24)
info  2022-03-30 08:35:35: Starting zigbee-herdsman (0.14.20)
info  2022-03-30 08:35:36: zigbee-herdsman started (resumed)
...
info  2022-03-30 08:37:14: Configuring '0x00124b002512211d'
error 2022-03-30 08:37:24: Configure failed: Error: Bind 0x00124b002512211d/1 msTemperatureMeasurement from '0x00124b0022812a65/1' failed (AREQ - ZDO - bindRsp after 10000ms)
info  2022-03-30 08:37:24: Successfully configured '0x00124b002512211d'
info  2022-03-30 08:37:24: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/configure', payload '{"data":{"id":"0x00124b002512211d"},"status":"ok"}'

Update: I can confirm that version 1.21.1 works. No error is reported and the device is reporting data.

@Koenkk Do you think you could take a look at this regression?

[Koenkk]

@matbech seem to be a duplicate of https://github.com/Koenkk/zigbee2mqtt/issues/10973#issuecomment-1073053188 , already fixed in the dev branch (make sure to repair the device after upgrading). (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html)

[danieldid]

I can confirm what @Koenkk said - this is fixed at least in latest dev branch. After reconfiguring all of my devices this works like a charm. This shall be closed though.

@matbech and @jjromannet did you tried it with 1.26 (latest) or dev branch?

[linker3000]

I've been running 1.25.0 for about a week and this version seems to have fixed disconnect issues with both my SNZB-02 temperature sensors and Sonoff S26R2ZB smart plugs.

Nigel

On Sun, 10 Apr 2022, 16:38 Daniel Didusch, @.***> wrote:

I can confirm what @Koenkk https://github.com/Koenkk said - this is fixed at least in latest dev branch. After reconfiguring all of my devices this works like a charm. This shall be closed though.

@matbech https://github.com/matbech and @jjromannet https://github.com/jjromannet did you tried it with 1.26 (latest) or dev branch?

— Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/8971#issuecomment-1094298964, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEUHQX7IF6KHLWQNKQKY6T3VELYYNANCNFSM5FHNI4WA . You are receiving this because you commented.Message ID: @.***>

[ndevenish]

I've updated to 1.25.0 and it seems to be working fine. I needed to re-pair, reconfiguration failed, but the re-pair worked first time and running smoothly since then.

This also fixed the issues I had (on 1.21.0) with an Ikea Tradfri button, so pleased all around.

[Koenkk]

Thanks for confirming all, time to close this.

[MarcoGT]

With 1.30.1 not working

[dsduarte]

With 1.30.1 not working

I got 1.30.3 and my SNZB-02 devices were getting offline and stop reporting every day... Yesterday I forced removed them and then added again e now they are working well.

[miekrr]

Same, not working on the latest docker image. Following instructions https://github.com/Koenkk/zigbee2mqtt.io/commit/fd2285ca15ec45d394502af866d9a977e9791cef fixes temporary.

Next server reboot usually at least one sensor is left out and doesn't report anything.

[mnn]

I am on 1.32.2 (I think current latest?) and even the "temporary fix" doesn't work for me. It takes long just to start pairing (5-10 minutes), it has to be almost touching the antenna otherwise there's not a chance of even getting this "far". Then usually paring fails. And even when it doesn't fail, it doesn't setup reporting, so I never hear from the device again... Tried it two times, it took total half an hour and without any result :weary:.