tinkertanker / pxt-iot-environment-kit Goto Github PK

In MakeCode the use of the Octopus Block to show temperature measured
Environment.octopus_BME280(Environment.BME280_state.BME280_temperature_C),
will only show integer values eg 23 oC but not 23,5 oC

We have been fine using the read DHT11 function in the old makecode interface.
But after makecode update, the function does not work anymore.

Please check.
Thanks a lot!!!

Please remove the following from the README as it is causing duplicate package imports:
```package
environment=github:sunnyrainwss/pxt-iot-environment-kit
iot=github:sunnyrainwss/pxt-iot-environment-kit
```

See microsoft/pxt-microbit#4832 for more info.

MakeCode for the micro:bit update is coming soon. Part of the update is floating point support. Existing MakeCode website supports only integer division which means
1/2 = 0
With this update 1/2 = 0.5

Action for you:
We have automatically detected this package uses division operator. Please take one of the following actions

• If the change to floating point division doesn't matter you can ignore and close this issue.
• If you want integer division then update your package typescript code to use integer division. Change a/b to Math.idiv(a, b)

You can test your package on the update here: https://makecode.microbit.org/beta

All the details on the update: https://makecode.com/blog/microbit/v1-beta
div found in environment.ts

https://github.com/elecfreaks/pxt-esp8266iot does not work with Micro:bit V2.

Trying to add the package results in a message that the 'network request failed'

The description is too long and bleeding out our cards. It might be clipped in the future.

Hi @tinkertanker,

As you might have seen from microsoft/pxt-microbit#3506 this extension is currently not compiling against the latest version of Micro:bit CODAL. This means it will not work with micro:bit V2.

Software for micro:bit V2 boards is built using CODAL rather than the DAL, and no longer includes the mbed layer. We’ve implemented the most frequently used mbed classes to support easy porting of existing extensions, but there may still be corner cases with this compatibility layer.

As your extension is currently not building, it will be disabled for micro:bit V2. People attempting to use your extension with a micro:bit V2 board will get error 929. This extension will only be re-enabled on micro:bit V2 once it is fixed.

There are details on how to ensure extensions work on both version of the micro:bit here (lancaster-university/codal-microbit-v2#31).

Looking at your extension source I believe that your extension falls under this category:

1. Use of mbed APIs that are in the compatibility layer, but no inclusion of mbed.h

Hi,
I would like to use your ESP8266 module and his microbit associate's package : http://www.elecfreaks.com/store/blog/post/how-to-send-microbit-data-to-iot-platform.html

It seems that it doesn't work with makecode V2.

Thanks
Regards