Acknowledged
over 1 year ago

Simulator v7.2.0 Bug: With Sim v7.2.0 BLE connections made with nRF dongle drop after connect

With Sim v7.2.0 BLE connections made with nRF dongle disconnect immediately, after a device has successfully paired and connected.

Parents
  • It's not the nRF dongle, because the two test tested evices succesfully were paired and connected, before the disconnect occurs.

    ️Same code and same devices and same context, but different result, switching between 7.1.1 and 7.2.0. Whatever root cause it is, there is a difference between behaviour of SIM 7.1.1 and 7.2.0.

    My app, a datafield, is based on the nordic thingy flow. It simply does scan, pair, connect, then write CharDescriptor to enable notification, after this waits for OnCharacteristicChanged and grabs the delivered data. Thus, no need for queuing imho.

Comment
  • It's not the nRF dongle, because the two test tested evices succesfully were paired and connected, before the disconnect occurs.

    ️Same code and same devices and same context, but different result, switching between 7.1.1 and 7.2.0. Whatever root cause it is, there is a difference between behaviour of SIM 7.1.1 and 7.2.0.

    My app, a datafield, is based on the nordic thingy flow. It simply does scan, pair, connect, then write CharDescriptor to enable notification, after this waits for OnCharacteristicChanged and grabs the delivered data. Thus, no need for queuing imho.

Children
  • Can you replicate this with a sensor Garmin might have or send them the sensor you use so they can replicate it?

    In both cases you want to send Garmin the source for your app.

    When I had issues with the pi sensors, I made sure I could replicate it with a Thing52 for example.