You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Zepp OS Team received a lot of questions from developers at the recent developer workshop, so in order to let more of you who couldn't make it to the workshop know about them, we've organized the questions for your convenience.
Q: How to use the Bluetooth function on the simulator?
A: We understand developers’ need to use Bluetooth functionality to build some exciting Mini Programs. However, our current Zepp OS simulator does not support Bluetooth at this stage. To develop and test Bluetooth-related features, you will need to use an actual Zepp OS device.
Q: Will the docs be updated (soon) to include the v3.0 APIs for NFC, BlueTooth and the microphone?
Documentation on microphone access will also be provided as soon as possible.
We apologize that NFC capabilities will not be available at this time. However, to the best of our knowledge, there are plans to enable related technologies in the future. Please stay tuned.
Q: Talking about documentation, on Short Service System Events section. Can we get the full list of events available?
A: System events will be supplemented as soon as possible.
Q: will it be possible to get png files from fetch api, and then show them within the canvas? I saw that currently we can show the png files from assets folder on the canvas, however it is not clear whether you plan to allow loading png files from the internet.
A: Canvas could show image file on device. and we are currently working on getting png files with fetch api and transmit to smart watch.
Q: As you know, Canvas is a very powerful tool for creating dynamic and visually appealing user interfaces. However, one glaring gap in its current capabilities is the ability to draw triangles. While other shapes such as circles and rectangles are well supported, triangles are more cumbersome to create, requiring the use of multiple lines and multiple angles.
A: Canvas API will support triangle and multiple angles rendering in next simulator version.
Q: Also having a graph feature on the canvas would be nice to plot data that has been received from a sensor
A: We will continue to optimize and enhance the capabilities of Canvas. We believe this will make chart rendering much more powerful.
Q: Short Service System Events, would be nice an event when phone get disconnected/connected and when user fell asleep/woke up
A: Fall asleep & wake up already included, and we will consider about the phone connect status, on iOS there is disconnect event only when BT is switched off.
Q: Another one to add would be probably a not-filled Circle. Unless it's already available. Like we can draw a rect filled/empty, would be good having that possibility for every primitive.
A: we will support this in next simulator version.
Q: Can background service create notification?
A: yes, It's possible to send notification in background service.
Q: When do you plan to push Zepp OS 2.1 version to currently available Zepp OS 2.0 devices? GPS was planned on Zepp OS 2.1?
A: Zepp OS 2.1 already available on device like TRex-2 Ultra, and on GTR4, It will be upgraded in the near future, but we are unable to provide an exact time plan.
Q: Is there an api which can be used to check the current API_LEVEL in the app, so that we show only options which are available under the specific API_LEVEL?
Q: What would happen when call the API_LEVEL 2.1 code on a 2.0 system
A: Calling a higher version API on a system with API_LEVEL 2.0 may cause JS errors because the introduced methods do not exist and are undefined. Therefore, before calling, it is recommended to first check for existence. Please refer to the above example of using getSystemInfo.
Q: What about text so speech?
A: We currently don't have plan to provide this.
Q: The settings document is not complete. Has anyone brought this up meeting?
A: The documentation of Settings App has been a weak point of Zepp OS. We are considering optimizing it and providing more comprehensive examples and images to better guide developers.
Q: Will the Bluetooth protocol support high-quality audio codecs such as LDAC, AAC, and LHDC for playback?
A: No, we can't support these protocols.
Q: Will it be possible that smartwatch acts a peripheral for some other master device (e.g. control camera which is master in thast case?
A: The system has ability to do so, but we currently don't have plan to provide it for mini app
Q: Can we build an app that support both zepp os 2.0 3.0, where at the same time in app.json file we can specify the particular 2.0 devices, and also the zepp os 3.0 devices, by their shape? More specifically can we mix both device specifications in the same code base?
A: Unlike the upgrades from Zepp OS 1.0 to Zepp OS 2.0, system compatibility after Zepp OS 2.0 is fully ensured based on API_LEVEL. The same project code can be used, but it should be noted that high API_LEVEL APIs cannot run on low API_LEVEL devices. Compatibility needs to be checked when calling to ensure that no code errors are caused.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Zepp Health
-
Zepp OS Team received a lot of questions from developers at the recent developer workshop, so in order to let more of you who couldn't make it to the workshop know about them, we've organized the questions for your convenience.
Q: How to use the Bluetooth function on the simulator?
A: We understand developers’ need to use Bluetooth functionality to build some exciting Mini Programs. However, our current Zepp OS simulator does not support Bluetooth at this stage. To develop and test Bluetooth-related features, you will need to use an actual Zepp OS device.
Q: Will the docs be updated (soon) to include the v3.0 APIs for NFC, BlueTooth and the microphone?
A: We have updated the Bluetooth related APIs. Please refer to the official documentation at https://docs-testing.zepp.com/docs/next/reference/device-app-api/newAPI/ble/mstBuildProfile/ for details.
Documentation on microphone access will also be provided as soon as possible.
We apologize that NFC capabilities will not be available at this time. However, to the best of our knowledge, there are plans to enable related technologies in the future. Please stay tuned.
Q: Talking about documentation, on Short Service System Events section. Can we get the full list of events available?
A: System events will be supplemented as soon as possible.
Q: will it be possible to get png files from fetch api, and then show them within the canvas? I saw that currently we can show the png files from assets folder on the canvas, however it is not clear whether you plan to allow loading png files from the internet.
A: Canvas could show image file on device. and we are currently working on getting png files with fetch api and transmit to smart watch.
Q: As you know, Canvas is a very powerful tool for creating dynamic and visually appealing user interfaces. However, one glaring gap in its current capabilities is the ability to draw triangles. While other shapes such as circles and rectangles are well supported, triangles are more cumbersome to create, requiring the use of multiple lines and multiple angles.
A: Canvas API will support triangle and multiple angles rendering in next simulator version.
Q: Also having a graph feature on the canvas would be nice to plot data that has been received from a sensor
A: We will continue to optimize and enhance the capabilities of Canvas. We believe this will make chart rendering much more powerful.
Q: Short Service System Events, would be nice an event when phone get disconnected/connected and when user fell asleep/woke up
A: Fall asleep & wake up already included, and we will consider about the phone connect status, on iOS there is disconnect event only when BT is switched off.
Q: Another one to add would be probably a not-filled Circle. Unless it's already available. Like we can draw a rect filled/empty, would be good having that possibility for every primitive.
A: we will support this in next simulator version.
Q: Can background service create notification?
A: yes, It's possible to send notification in background service.
Q: When do you plan to push Zepp OS 2.1 version to currently available Zepp OS 2.0 devices? GPS was planned on Zepp OS 2.1?
A: Zepp OS 2.1 already available on device like TRex-2 Ultra, and on GTR4, It will be upgraded in the near future, but we are unable to provide an exact time plan.
Q: Is there an api which can be used to check the current API_LEVEL in the app, so that we show only options which are available under the specific API_LEVEL?
A: In API_LEVEL 2.1, we have added a new API getSystemInfo https://docs.zepp.com/docs/reference/device-app-api/newAPI/settings/getSystemInfo/. If this API is detected, it means our API_LEVEL version is higher than 2.0. Calling this API can get the system version and API_LEVEL version.
Q: What would happen when call the API_LEVEL 2.1 code on a 2.0 system
A: Calling a higher version API on a system with API_LEVEL 2.0 may cause JS errors because the introduced methods do not exist and are undefined. Therefore, before calling, it is recommended to first check for existence. Please refer to the above example of using getSystemInfo.
Q: What about text so speech?
A: We currently don't have plan to provide this.
Q: The settings document is not complete. Has anyone brought this up meeting?
A: The documentation of Settings App has been a weak point of Zepp OS. We are considering optimizing it and providing more comprehensive examples and images to better guide developers.
Q: Will the Bluetooth protocol support high-quality audio codecs such as LDAC, AAC, and LHDC for playback?
A: No, we can't support these protocols.
Q: Will it be possible that smartwatch acts a peripheral for some other master device (e.g. control camera which is master in thast case?
A: The system has ability to do so, but we currently don't have plan to provide it for mini app
Q: Can we build an app that support both zepp os 2.0 3.0, where at the same time in app.json file we can specify the particular 2.0 devices, and also the zepp os 3.0 devices, by their shape? More specifically can we mix both device specifications in the same code base?
A: Unlike the upgrades from Zepp OS 1.0 to Zepp OS 2.0, system compatibility after Zepp OS 2.0 is fully ensured based on API_LEVEL. The same project code can be used, but it should be noted that high API_LEVEL APIs cannot run on low API_LEVEL devices. Compatibility needs to be checked when calling to ensure that no code errors are caused.
Beta Was this translation helpful? Give feedback.
All reactions