Clemens

Yes, it just copies the payload content into the message buffer and converts it from byte to char. I don't see any reason to use a byte-by-byte copy mechanism here...

Sure, It was already included in the last PR (https://github.com/SmittyHalibut/EleksTubeHAX/pull/95) I ran the PlatformIO Inspector again then and there was some more stuff... It actually just runs the command "platformio.exe...

I created a PR for the cpp check finding fixes https://github.com/SmittyHalibut/EleksTubeHAX/pull/101 The format stuff is not that important, I guess...I prepeared a branch already, but need to integrate the latest...

I merged this branch into the branch https://github.com/Martinius79/EleksTubeHAX/tree/AddedIPSTUBEs. It is now in PR https://github.com/SmittyHalibut/EleksTubeHAX/pull/86

> May I suggest that you create a hardware folder like the one that exists for the other clocks and enter the corresponding pictures of the board and pin assignment...

I found out, how the LED stripe on the bottom of the clock is working. It is just a continuation of the existing RGB LEDs with the same controlling pin....

> Good work! Still has potential for improvement. Yes, a lot :) But it is a spare time project, so one step after another... > The top-level README could do...

Hello, thx @Walmtech for the pictures! Yes, on this side of the board, it looks nearly all the same, except two places. But there seems to be no components soldered...

> @Martinius79 Also, is `AddedIPSTUBEH401-2` a correct branch? Yes, this is the branch, where this PR is coming from. So it is the right one.

> > Not sure what else I could try. > You can use the serial monitor in VS Code, to watch the output from the clock! Install the Serial Monitor...