Martin Ždila

Thank for your prompt reply. > Are there any other interrupt routines? None I am aware of. Testcase only uses ESP8266_NONOS_SDK, your PWM implementation and the code from this report....

As I mentioned our product uses Mongoose OS. After we added Azure IoT functionality, the PWM quality rapidly decreased. Surprisingly (for me) `#define PWM_USE_NMI 1` fixed the problem.

https://github.com/SpenceKonde/ATTinyCore has tone() support for ATTiny85.

I replaced `deviceName = dev.getValueText(0x08)` with `deviceName = dev.getValueText(0x09)` and the device was found. Unfortunately the device disconnects shortly after it is connected. BTW the filter is `{'filters': [{'namePrefix': 'intelino'},...

Attaching output of `scratch_link -d`: [debug.log.gz](https://github.com/kawasaki/pyscrlink/files/7775756/debug.log.gz)

Thanks for your reply. I've managed to create a dump of websocket communication from working scratch-link on MacOS. Will it help? It contains all messages from connecting to the train...

WS dump when using pyscrlink: [pyscrlink-ws-dump.json.gz](https://github.com/kawasaki/pyscrlink/files/7796044/pyscrlink-ws-dump.json.gz)

It looks like pyscrlink is not receiving characteristics change (or not sending them via WS). I tried following steps using nRF Connect Android app: 1. connect to the device 2....

Meanwhile I've written Scratch Link for Linux and Intelino smart train in nodejs: https://github.com/zdila/intelino-smart-train-scratch-link-linux

I tried the `dev` branch with your commit but unfortunatley the problem is still there. Yes, my Node.js version works fine with my Intelino train.