Seems that this was a newbee error. I had the example flow still active in the project, and used a second instance of the websocket in my own flow. But seemingly, those instances conflict with each other causing only parts of message to arrive.
If I have only one instance of the listening websocket in the project, everything seems to work smoothly.
The firmware upgrade problem, however, remains. I have fw 5.58, the OS has upgraded the firmware package to 5.60 but I can't upgrade the actual firmware as the fwspi --auto command doesn't start the upgrade.
I found out I had many SPI CRC2 errors in my kernel logs.
Looking around I found this post
It turns out the stock image 20220412.0 for nodered actually ships with the broken revision 1.108 of the kernel module.
Thanks to @knebb 's instructions I was able to downgrade to v1.106 and my neuron seems to be working fine again.
I hope someone from the customer support gets to see this post and fixes the image quickly.
Guys, you have a terrific product line (I bought two neurons and some accessories over the years and I am a very happy customer), but you should really improve the regression testing before releasing: it is not the first time I have problems when trying to use an official image: see here
I might be able to provide you with some logs in case you need help in troubleshooting on older hardware (S103 S/N 109 from 2017): just contact me in the next couple of days - then I'll have to put the system back on the field.
Thanks for the reaction!
Okey, I indeed thought it had something to do with that, but I couldn't find any update notes on the os image.
I don't really need to access the sensors through the unipi node anyways, so I'm going to try option 2.
the Node-RED image is defacto a Raspberry Pi OS. You can proceed with any general tutorial for adding the desktop environment, which you can find on the offical Raspberry Pi OS webpage.
this flow gets data from unipi 1.1. unipi lite does not have ai ao. Just skip it. temp input is one wire sensor data. the json all node initializes all variables and then websocket delivers actual data.