Carlos

The recent protocol buffer changes require MOS to now recognize if a user's MATRIX device is a Voice or Creator.

MATRIX OS outputs: ``` Zigbee available, not activated. ```

Works fine in HAL and MALOS, but MOS had no response.

None of the CV apps I made or downloaded from the MATRIX App Store worked.

I can't get the GPIO pins to properly work. Works in HAL, but not in MOS and MALOS. No errors are being logged either. @eighteyes @diegoribero

Sensors will sometimes be stuck at a value

2

Noticed with the IMU driver. This issue normally goes away after a device reboot.

This **only** affects the printing of the .read() function. ``` >> print(sensors.uv.read()) >> 0.003000 ``` The actual value is unaffected ``` >> print(sensors.uv.read().uv) >> 0.003000000026077032 ``` [Here](https://github.com/matrix-io/matrix-lite-py/blob/master/hal_wrapper/drivers/sensors.cpp#L43) is the printing...

`matrix ping` works, but an error will always appear. The documentation has it written down. /matrix-os/reference/cli-tool/#development ```Matrix CLI Error: TypeError: Cannot read property 'message' of null```

Typing the command in the CLI outputs this: ``` $ matrix update ⣷ /Users/carlos/.nvm/versions/node/v9.5.0/lib/node_modules/matrix-cli/node_modules/async/lib/async.js:718 task(_restParam(function (err, args) { ^ TypeError: task is not a function at /Users/carlos/.nvm/versions/node/v9.5.0/lib/node_modules/matrix-cli/node_modules/async/lib/async.js:718:13 at Immediate.iterate (/Users/carlos/.nvm/versions/node/v9.5.0/lib/node_modules/matrix-cli/node_modules/async/lib/async.js:262:13)...