Check the YAML specification

Oct 13, 2025 by pynkocean.com 116 views

Cannot Subscribe to Energy/Level and Comm/Peers: A Critical Issue with the Movesense Plugin

The Movesense plugin has been a game-changer for developers looking to integrate sensor data into their applications. With its robust features and seamless integration, it has become a go-to solution for many. However, as with any complex system, there are bound to be issues that arise. In this article, we will delve into a critical issue that has been reported by a developer, where they are unable to subscribe to certain events, specifically the Battery level events and connection notification events for the Movesense MD sensor.

The developer in question has been using version ^2.2.0 of the plugin and has encountered an issue where subscription to certain events looks unavailable. Despite following the YAML specification, which indicates that a subscription route exists for both "/System/Energy/Level" and "/Comm/Ble/Peers", they are unable to subscribe to these events. The developer has tried various combinations of Mds, MdsAsync, subscribe, and post to the "/Subscription" endpoint, both on iOS and Android, but are consistently getting an onSubscriptionError.

Example Code

To illustrate the issue, the developer has provided an example of the code they are using to attempt to subscribe to the "/System/Energy/Level" event:

MdsAsync.subscribe(
  Mds.createSubscriptionUri(serial,"/System/Energy/Level"),
  '{}',
);

This code throws an MdsError, code 404, which suggests that the API routes do not exist. This raises questions about the implementation of the plugin and whether the API routes are indeed missing.

YAML Specification

According to the YAML specification, a subscription route exists for both "/System/Energy/Level" and "/Comm/Ble/Peers". The relevant YAML files can be found at:

The issue reported by the developer is a critical one, as it affects the ability to subscribe to certain events. The YAML specification suggests that the API routes should exist, but the developer's attempts to subscribe to these events have been unsuccessful. This raises questions about the implementation of the plugin and whether the API routes are indeed missing.

Future Implementation

The developer has asked whether the API routes will be implemented in the future. While we cannot provide a definitive answer, we can suggest that the plugin developers may consider implementing these API routes in future updates. In the meantime, developers may need to find alternative solutions to subscribe to these events.

Recommendations

For developers who are experiencing this issue, we recommend the following:

Check the YAML specification to ensure that the API routes exist.
Verify that the code being used to subscribe to the events is correct.
Consider alternative solutions to subscribe to the events, such as using a different API endpoint or implementing a custom solution.

In conclusion, the issue reported by the developer is a critical one that affects the ability to subscribe to certain events. While the YAML specification suggests that the API routes should exist, the developer's attempts to subscribe to these events have been unsuccessful. We recommend that developers check the YAML specification, verify their code, and consider alternative solutions to subscribe to the events.
Movesense Plugin: Frequently Asked Questions

The Movesense plugin has been a game-changer for developers looking to integrate sensor data into their applications. With its robust features and seamless integration, it has become a go-to solution for many. However, as with any complex system, there are bound to be questions that arise. In this article, we will address some of the most frequently asked questions about the Movesense plugin.

Q: What is the Movesense plugin?

A: The Movesense plugin is a software development kit (SDK) that allows developers to integrate sensor data from the Movesense MD sensor into their applications. It provides a robust and seamless way to access sensor data, including acceleration, gyroscope, and magnetometer readings.

Q: What are the benefits of using the Movesense plugin?

A: The Movesense plugin offers several benefits, including:

Easy integration: The plugin provides a simple and intuitive API for accessing sensor data.
Robust features: The plugin includes a range of features, including support for multiple sensors, data filtering, and event handling.
Seamless integration: The plugin integrates seamlessly with popular development frameworks, including iOS and Android.

Q: What are the system requirements for the Movesense plugin?

A: The Movesense plugin requires the following system requirements:

Movesense MD sensor: The plugin requires a Movesense MD sensor to function.
iOS or Android: The plugin supports both iOS and Android development frameworks.
Java or Swift: The plugin supports both Java and Swift programming languages.

Q: How do I subscribe to events using the Movesense plugin?

A: To subscribe to events using the Movesense plugin, you will need to use the MdsAsync.subscribe() method. This method takes two parameters: the subscription URI and the event data.

Q: What are the possible error codes for the Movesense plugin?

A: The Movesense plugin returns the following possible error codes:

404: The API route does not exist.
500: An internal server error occurred.
503: The server is unavailable.

Q: How do I troubleshoot issues with the Movesense plugin?

A: To troubleshoot issues with the Movesense plugin, you can try the following:

Check the YAML specification: Verify that the API routes exist and are correctly configured.
Verify the code: Check that the code being used to subscribe to events is correct.
Check the Movesense MD sensor: Ensure that the Movesense MD sensor is properly connected and configured.

Q: Is the Movesense plugin open-source?

A: Yes, the Movesense plugin is open-source. The plugin is available on GitHub and can be modified and extended by developers.

Q: How do I contribute to the Movesense plugin?

A: To contribute to the Movesense plugin, you can:

Submit bug reports: Report any issues or bugs you encounter with the plugin.
Submit feature requests: Suggest new features or improvements to the plugin.
Contribute code: Contribute code to the plugin to improve its functionality and stability.

In conclusion, the Movesense plugin is a powerful tool for developers looking to integrate sensor data into their applications. With its robust features and seamless integration, it has become a go-to solution for many. We hope that this FAQ article has provided you with the information you need to get started with the Movesense plugin.