Errors when running script about ph4-walkingpad HOT 11 CLOSED

Yes it works for the stats collection and there is times when the stats say
"ccal": null, "ccal_net": null, "ccal_sum": null, "ccal_net_sum": null
but then right after it works again like this:

{"time": 211, "dist": 13, "steps": 317, "speed": 30, "app_speed": 7, "belt_state": 1, "controller_button": 0, "manual_mode": 1, "raw": "f8a2011e010000d300000d00013d07000000e7fd", "rec_time": 1649253095.8210037, "pid": "user", "ccal": null, "ccal_net": null, "ccal_sum": null, "ccal_net_sum": null}
{"time": 212, "dist": 14, "steps": 317, "speed": 30, "app_speed": 7, "belt_state": 1, "controller_button": 0, "manual_mode": 1, "raw": "f8a2011e010000d400000e00013d07000000e9fd", "rec_time": 1649253095.8585336, "pid": "user", "ccal": 0.072, "ccal_net": 0.049, " ccal_sum": 13.453, "ccal_net_sum": 8.722}

from ph4-walkingpad.

yeah changed the interval and it seems to be working better. I just noticed first time that it seems like the peep comes from changing from manual speed mode to automatic. Without the connection to the script it cannot be changed in the middle of walk. (haven't used it for a long time without the connection so I'm not sure.)

from ph4-walkingpad.

thanks for the report! Unfortunately it seems that DTM100i is using a different protocol which is not reversed yet.

from ph4-walkingpad.

I have no access to this belt type, so in order to reverse engineer the protocol we would need couple of messages being exchanged between app and the belt. Android application is ideal for it.

https://github.com/ph4r05/ph4-walkingpad#easy-way---android-logs

from ph4-walkingpad.

I really don't want to install the android app.

I have been using this program to collect the stats and it has been enough for that. Just wondering should there be a way to use only the connecting and stats part of the program as those work for my pad. As I said I use the remote to control it.

from ph4-walkingpad.

@haivala ah so you say that this script works for you for stats collection? Stacktrace you posted indicates that the program has problems with parsing belt data packets (WalkingPadCurStatus.from_data(data)) containing number of steps, etc.

So do you get meaningful data from the belt, just the program randomly outputs errors you posted?

from ph4-walkingpad.

ah, in that case, I've pushed an update, you can try running it with --ignore-bad-packets, it should silence those errors you are getting.

It is just matter of logging, those unsupported packets won't be decoded, just discarded. But if you get reasonable info anyway, this should do the job.

from ph4-walkingpad.

Seems to be working but it gives this error on startup:

Executing <Task pending name='Task-1' coro=<WalkingPadControl.main() running at /.local/lib/python3.10/site-packages/ph4_walkingpad/main.py:375> wait_for=<Future pending cb=[BaseSelectorEventLoop._sock_read_done(10, handle=<Handle BaseS...events.py:254>)(), Task.task_wakeup()] created at /usr/lib/python3.10/asyncio/base_events.py:429> cb=[_run_until_complete_cb() at /usr/lib/python3.10/asyncio/base_events.py:184] created at /usr/lib/python3.10/asyncio/tasks.py:636> took 0.114 seconds

from ph4-walkingpad.

Hmm. And sometimes the belt starts peeping and starts to go faster for few seconds then it calms down. Bit dangerous but I'll live with it :)

from ph4-walkingpad.

Now it suddenly stopped which it has never done before

from ph4-walkingpad.

Hmm, use this at your own risk 😅 do not leave belt powered on unattended, etc.

The stats collection works in a way it sends periodically stats prompt message (each 500ms) to the belt, i.e., [247, 162, 0, 0, 162, 253]. Belt responds with the latest stats (including steps).

As this app was not tested with the belt, it can have unknown protocol and belt can interpret prompt message in a different way.

Maybe try using --stats 1500 to ask for stats each 1.5 second. The application is not sending any other messages.

from ph4-walkingpad.