Requesting device_data from ping360 results in an empty profile:

Open
#178 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
embedded-iot

Research direction

Start by reproducing the Python call using p.wait_message([definitions.PING360_DEVICE_DATA]) and inspect the definition of PING360_DEVICE_DATA. Compare the returned profile with the expected Ping360 device data, then document or test the conditions under which the profile is empty. Done means the request returns a populated profile or the failure is clearly characterized.

Written by the indexing model from the issue text.

Description

device_data = p.wait_message([definitions.PING360_DEVICE_DATA])

Dominant language
Python
Stars
27
Forks
26
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bluerobotics/ping-protocol

All issues in bluerobotics/ping-protocol

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.