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
{{ message }}
This repository has been archived by the owner on Jun 2, 2023. It is now read-only.
We are using the constructor to init devices in the new translator format currently being built in the dev branch. We don't have a destructor (not supported in es6 JavaScript?) or any explicit disconnect/destroy button.
This is an issue for some translators, e.g. the Bluetooth LE based TI SensorTag temperature sensor. That needs an explicit connect and disconnect (both async).
For now we are working around this by create non-schema connect and disconnect methods in only the TI SensorTag temperature sensor. These methods are called explicitly in the unit tests.
Ideally connect/disconnect should be called automatically as part of translator lifecycle... for devices that need this, but we need to figure that out.
This could be something that is only important for non-hub translators. Since we are focused right now on hub based translators, this is something we can mull over.
The text was updated successfully, but these errors were encountered:
We are using the constructor to init devices in the new translator format currently being built in the
dev
branch. We don't have a destructor (not supported in es6 JavaScript?) or any explicit disconnect/destroy button.This is an issue for some translators, e.g. the Bluetooth LE based TI SensorTag temperature sensor. That needs an explicit connect and disconnect (both async).
For now we are working around this by create non-schema connect and disconnect methods in only the TI SensorTag temperature sensor. These methods are called explicitly in the unit tests.
Ideally connect/disconnect should be called automatically as part of translator lifecycle... for devices that need this, but we need to figure that out.
This could be something that is only important for non-hub translators. Since we are focused right now on hub based translators, this is something we can mull over.
The text was updated successfully, but these errors were encountered: