I had someone make me 2 versions of node. v8 and v9. I am using v8 successfully for a while now. I also had upgraded the npm.
https://www.dropbox.com/s/skm0d51ou4yqnqt/node_v8.11.3-2_mipsel_24kc.ipk?dl=0
https://www.dropbox.com/s/nuyvqo3rtkxhab2/node-npm_v8.11.3-2_mipsel_24kc.ipk?dl=0
Let me know how you like it, install it using opkg.
My recommendation is using NodeJS. I use NodeJS with Azure IoT Device and I dont run into any storage size issues. One little trick I found, install all your modules in /tmp, then move the node_modules folder to / . The folder will be highly compressed once its in flash memory.
C.H.I.P is gone now and Raspberry Pi makes no money on their 5$ version but has enough sales to break even and use it as a loss leader (Educational purposes). Each platform supports different functions. Did you know you could have up to 5 Ethernet ports on the Omega and it supports native soft AP to act like a router / hub? There are no Ethernet ports and NO WiFi on the Pi Zero.
There are a lot of things to consider besides price like application, use case, size, ect.
haha, you are doing the same thing I did. So all the connections are actually related to the Onion cloud.
you can stop the service and you will see the connections slowly disconnect and remove. If you reboot, the service will come back online. I deleted the service completely as I didn't want / need the Onion cloud.
Stop service:
service device-client stop
Delete service:
opkg remove device-client
reboot
After the reboot you shouldn't see the connections anymore. I actually removed most of the services pre-installed on the Onion.
@UFD said in I2S Issues:
are (0.2.2 b200)
Somewhere I read they disabled i2s audio, if you search the forums there is more info on it but no one from Onion.io has made any comments on it. Better to submit a help ticket if possible. I had to downgrade the fw to use audio as well. The other work around that I found that does work, though I hate it, is using a USB audio driver.
At some point the MAX98357A i2s power amp used to work over i2s. If you read on the forums people had issues above b193. Is there a way around the issue and fix i2s to be able to have audio out?
Thanks
I had someone make me 2 versions of node. v8 and v9. I am using v8 successfully for a while now. I also had upgraded the npm.
https://www.dropbox.com/s/skm0d51ou4yqnqt/node_v8.11.3-2_mipsel_24kc.ipk?dl=0
https://www.dropbox.com/s/nuyvqo3rtkxhab2/node-npm_v8.11.3-2_mipsel_24kc.ipk?dl=0
Let me know how you like it, install it using opkg.
Well fingers crossed you get this working 
Any updates on this? 
My recommendation is using NodeJS. I use NodeJS with Azure IoT Device and I dont run into any storage size issues. One little trick I found, install all your modules in /tmp, then move the node_modules folder to / . The folder will be highly compressed once its in flash memory.
MAYBE the cable was 2 separate USB connectors, 1 for webcam, 1 for microphone? Like a Y connector with shared power / gnd? no idea lol
I am building a Hub that supports POE as well. The circuit I am using supports 12-48v DC (dont want to deal with diode rectifier for AC) POE injectors. I am actually using Ubiquity as one of the POE testers.
You have a lot more passive components than I do. Mine only uses 12 BOM line items. (14) total. Maybe because my Ethernet Jack has the Harmonics built in. Either way, good work.