dorita980 VS nioev-mqtt

I installed this tool via npm on my MacBook.

This is for example a library to send commands to your roomba https://github.com/koalazak/dorita980

Please share here instead, others like me are also interested and actively https://github.com/koalazak/dorita980/issues/163 looking for solutions.

I'm aware of https://github.com/koalazak/dorita980 that I used in the past. I believe that should allow me to skip the app entirely. That might be sufficient to avoid for the device to "phone home" but I'm not sure. I could use WireShark to check and eventually use e.g a PiHole to filter this kind of requests. Ideally I'd flash my (relatively) old model with an open firmware but I'm not sure that exists.

I think I just found the problem, I looked for it before but somehow missed it (prob because I didn't know on came from Mqtt at the time). I think your firmware is version 1.x or whatever, which uses a different definition for Local. It doesn't include the MqttClient. The docs for that are here so try that and see if it works

The fourth version also has a gesture sensor at the top for controlling it. The gesture sensor is connected to the Zero which sends all detected gestures over mqtt to my animation script. I added a small video where I show all the scenes I created. The timer is my tea timer btw :). The frames are all rendered on my Ordroid XU4Q, which runs nioev-mqtt, which is my custom MQTT broker which has built-in JS scripting support. It also supports native libraries which you can dynamically load. This is how I created the cairo bindings to render the frames (and convert them to PNGs). To save power and reduce load, the frames in the video are only actually send at about 50FPS, but I managed way more in the past. At this point the Pi is the bottle neck, I should probably switch out the Python script on there for a bit of C++ at some point.