NOT_FOUND when subscribing to ECG

Issue #99 closed
Carlo Brunelleschi created an issue

Hello,
the ECG sensor returns NOT_FOUND when subscribing to /Meas/ECG/128.

This only happens sometimes, most of ECG subscriptions in fact complete successfully and data is then received.

I/Komposti: Adding EventListener for path: 180230001515/Meas/ECG/128
E/Komposti: [SDS RESPONSE] type: POST status: NOT_FOUND header: {"TaskId": 83, "Uri": "suunto://MDS/EventListener", "Content-Length": 0, "Reason": "NOT_FOUND", "Status": 404} error: [wb] Failed to get resource
V/Komposti: SDS::AndroidWrapper::callback A0: id: 83, type: 4, header: {"TaskId": 83, "Uri": "suunto://MDS/EventListener", "Content-Length": 0, "Reason": "NOT_FOUND", "Status": 404}, body:
D/MdsOperationHandler: SDSInternalCallback with call type: 4 header: {"TaskId": 83, "Uri": "suunto://MDS/EventListener", "Content-Length": 0, "Reason": "NOT_FOUND", "Status": 404}
E/DELTA: mdsSubscription_ECG - MdsException onError():
com.movesense.mds.MdsException: Failed status: 404, reason: NOT_FOUND

Longer log attached.

The application uses
mdslib-1.39.0(1)-release.aar
com.polidea.rxandroidble2:rxandroidble:1.10.2
io.reactivex.rxjava2:rxandroid:2.1.1
io.reactivex.rxjava2:rxjava:2.2.8

Movesense device
App version 1.1.0
Core version 1.9.2

Thanks

Comments (2)

  1. Petri Lipponen
    • changed status to open

    Could you attach a longer piece of log before the issue?

    I have a hunch that the sensor has disconnected just before subscribe causing the whiteboard not find the sensor part of URL ("suunto://<serial>") because the route table has been cleared already.

  2. Log in to comment