Fix the internet forward to switch from Phone USBTethering form ETH0 automatic without having to restart the PI.

Quick fix:
ifdown usb0
ifup eth0

maybe killing the hostap is needed
pkill -f hostapd

Tried to go back to esp32 platform 4.4 (current is 6.2 and known to be broken - not compiling with most libraries), but esp32 always crashes.

Also esp32 needs to wire io0 to 3.3V to even boot.

Very strange.

When running deploy, there is no warning when a lock has appeared and preventing deploy from executing.

The following command can fix this problem
rm /tmp/.net.ulno.iotempower.deploy_lock

M5 driver support is a thing now but its not referenced in command.rst yet and would be nice to have it.

It still started the webserver and the httpserver but nothing loaded on the page.

The warning it gave:

Warning: Container node skipped: type=document
warn("Container node skipped: type={0}".format(mdnode.t))
Generating web-viewable documentation

it was fixed by running: iot doc make.

A default system.conf needs to be copied in the install to iot-systems.

estimate [ulno]: 4h <- if doing more than fixing the links

• gesture sensor not working very well,
• proximity is blocking others
• gestures are sometimes detected but not very reliable
• color sometimes working well

Has something to do with using the right capacitor on esp8266 - needs further investigation

Have some kind of snapshot for stabler versions of the Framework where people can maybe downgrade and get back to version where the drives that they need are working.

The dongle flash command seems to be broken. Especially if it is executed in a node folder.

On the Pi quickstart documentation on ACCESSING THE LOCAL SERVICES ON THE RASPBERRY PI the user name under the third item is iotempower when it should be iot.

Docker container runs on 172.17. on the Raspberry and it conflicts with the U.T university LAN. Assign a new I.P at
etc/docker/damon.json
"default-address-pools" : [{"base": "10.10.0.0/16", "size": 24}]

Create a gateway dongle that can communicate multiple protocols besides wifi.

In some cases, it might be useful to have different wifi configurations for a node within a system. Meaning, this node does not use the wifi configuration of system.conf, but in node.conf. For example if multiple AP in a building have different credentials. However, using node.conf to set different wifi credentials, does not change <node>/build/src/wifi-config.h. This still uses the credentials from system.conf, at least for ESP8266.

Gettting the error can't read system.conf when running initialize serial or deploy on the node 1 folder

when booting the mpu6050 you get a wierd error

Following the documentation of the First Node, when we first adopt/Initialize, a the UI with the buttons are not showing after clicking on the user menu button on the right corner. Only getting a terminal prompt.

Create a new project folder shortcut on CloudComander interface under the F2 tab. The same way we can create a new Node folder, it would be nice to be able to create a new project folder.

Add font_small, and add all fonts to display description

Output and relay documentation is outdated, it is showing the old Python parameters. output(name, pin, high_command="on", low_command="off") high_command and low_command not needed anymore.

Implement some polling to check if device is alive and send update when device available.

Manually add DS1302 Real-Time Clock sensor to the framework

If I want to adapt a node with the powershell i get the error like in the picture.

We can have guidelines to communicate how people should contribute to the project.

Setting guidelines for repository contributors

github docs example contrib guidelines

It would be nice to have a script to create multiple wifi.init files so the gateway can repeat the internet connection form multiple wifie routers without having to change the file.

A specialized flashing dongle that helps us adopt new devices quickly without using USB serial.

A dongle with screen with to pre-flash multiple devices. for adopt.
Over the air remote dongle adoption.
Some kind of Remote serial port. (solving the MAC OS, and Windows port issues)

Setting this up just on a windows PC with python and the serial port should be easy - estimate [ulno]: 4h
adding a remote dongle design of a device to carry around: 1month

The First Node Documentation it says : Make sure that the IoT dongle is connected to the Rapsberry Pi
There is no link there to how to set up the dongle.
Couldn't find any documentation on the dongle.
dongle help is not working

Use a https connection to get update form server and not the weird UDP outdated MD5 arduino update.

the multiple i2c bus support seem to have broken generic i2c display support

Accessing to i2c displays leads to crashes at the momhent.

This needs to be fixed somehow.

We are using these boards for our university courses - plenty of them are available. Combined with the Arduino MKR carrier, it gives a nice all-in-one IoT Node (lots of sensors, relays, output...).

The microcontroller board itself uses a WiFiNINA chip for wireless connection.

It would be great to support this board as node type. OTA should be possible as well.

pls work

When trying to integrate a RGB LED module via MQTT controlling the LED leads to weird behaviour (interface flashing, color picking not working correctly, etc.)

The LED is configured in my configuration.yaml file in home assistant like this:

light:
  - platform: mqtt
    name: "L3 Light RGB"
    state_topic: "node2/rgb1"
    command_topic: "node2/rgb1/set"
    brightness_state_topic: "node2/rgb1/brightness"
    brightness_command_topic: "node2/rgb1/brightness/set"
    rgb_state_topic: "node2/rgb1/rgb"
    rgb_command_topic: "node2/rgb1/rgb/set"
    payload_on: "on"
    payload_off: "off"
    optimistic: false
    on_command_type: 'first'

The problem might be the Node not sending status updates correctly.

without haveget, casual linux users dont have enaugh entropy to generate key, so it gets stuck. it needs to be in installation guide as requirement that we need it to be installed.

It appears that the MQTT port (1883) used by ESP8266 is hardcoded. However, in some cases it would be useful to change the port used for MQTT, ideally also using the node.conf or system.conf file. (I know that 1883 is a standardized port for MQTT, but would be a nice feature that could come in handy i.e. for debugging)

Rudimentary support for rgb strip bus (best on D4 on wemos D1 mini) is implemented and works well. Somehow in one of the latest Fastled or esp8266 sdk updates a good timed rgb-strip without flashes and unresponsive leds is not possible anymore.

TODO: mark that clearly and either find what broke or remove FastLED from iotempower

Extend ESPS's functionalities to work synchronized to a timestamp for coordinated actions between nodes.

Maybe the deploy mechanism can communicate with the power saving mechanisms and listen to an MQTT wake message before sending the over the air (OTA) updates to nodes that run on deepsleep.

Jump the initial 5 seconds (boot up and adoption grace period) for that.

Reverse proxy to mirror port 40080 to be visible on another port so it can be visible via SSH

Deal also with authentication in here and maybe cloudflare example

estimate [ulno]: 8h

The initial vl53l0x implementation uses still a lot of busy waiting due to the imported library. This needs to be fixed and turned into some polling mechanism in measure.

Until then using vl53l0x will only work alone (and needs to be connected correctly). Simple input and outputs might work in addition but i2c devices or the ultrasonic distance sensor will definitely not work in parallel and cause constant crashes making OTA flashing (deploy) impossible -> though adoption should still work.

It would be nice to have some documentation for the Laser sensor supported on the framework.

It would be nice to have an one line framework installer for Debian based systems or just DietPi would already be great.

connecting an sx1276/1278 to the dongle should allow an easy local two device LORA setup.

Support needs to built into the dongle and dongle daemon (to forward messages to mqtt) as well as in the esp8266 nodes.

It seems like the Infrared driver stopped working with updates