how to solve it? Connection state change error: 133 newState: 0, An error occurred while connecting to the device:133

RE: how to solve it? Connection state change error: 133 newState: 0, An error occurred while connecting to the device:133

Sigurd — Mon, 06 Jul 2020 12:09:48 GMT

[quote user="Serobegi"]do you mean to adjust the time on the device and fix it, not the app?[/quote]

Yes. You could try to adjust that, and see if it helps. A sniffer-log could also be useful. See this link: https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Sniffer-for-Bluetooth-LE

RE: how to solve it? Connection state change error: 133 newState: 0, An error occurred while connecting to the device:133

Serobegi — Thu, 02 Jul 2020 10:57:20 GMT

ello

Then, do you mean to adjust the time on the device and fix it, not the app?

Thanks

RE: how to solve it? Connection state change error: 133 newState: 0, An error occurred while connecting to the device:133

Sigurd — Tue, 30 Jun 2020 12:18:41 GMT

Hi,

Error 133 - Gatt error is just a generic error. It happens in different occasions. We have observed it on

1) packet collision
2) CONNECT_REQ missed by the target
3) timeout (30 or 20 seconds after connection was initiated)
4) in general, an expected packet wasn't received or an unexpected was.

It used to be much more common in old days, now we see it less and less with the new phones, but the low-end devices still have a lot of problems with them. Very often it is enough to repeat the last operation, for example the connection request from the phone and it should work. Maybe you could also try to change the advertising interval on the nRF5x, and see if that makes any difference.