@Ghofran-Daoues TMPDIR variable is not set as you have spaces either side of the = symbol.

@Zemlak How did you install python 3.6

the pyserial package is so old it doesnt even support context manager to handle serial connections. did you work how if it is possible to update it? 3.9 or 3.10 would be great (even 3.8!). in a pinch you could use setuptools to install an updated package, but you're replying on them being compatible with 3.6 now.

@CAP-33 wouldn't the logical conclusion be that your first step would be to upgrade to the latest firmware?

@CAP-33 You are correct this is a "drawback" of python. I find python has a lot of drawbacks That's why I develop my apps using C.

@Victor-Lucio your on_log should print the buffer, it has no parameter named msg. buffer should contain any errors or warnings.

@Jonathan-Jefferies still going strong thanks for the reminder - I've updated the OpenWRT-Packages repo to set the openwrt-18.06 branch as the default!

see response here: https://community.onion.io/topic/3591/python3-modules-for-gpio-and-serial-port/8

Out of the blue I tried again from home and it seemed to have worked...

solved i used call method to solve this problem example: subprocess.call(["fast-gpio", "pwm", "19", "200", "10"])

This has worked for me, thanks Lazar! I'm having some weird SPI no_cs issue now that I'm trying to work through...anytime that command is included in the Python project, sleep gets an argument error. If I comment that line out then the project runs without error. I'll report back if I get it resolved.

@CAP-33 Glad to hear it, happy hacking!!

@luz Thank you very much for taking the time to reply to my question and explaining how Linux calls the various start up scripts. I will take your suggestion of creating a new script and enabling it. @Jon-Gordon Thanks to you as well for your suggestion, I think the first suggestion is more of an answer I am looking for. All the best to the both of you!

@Lazar-Demin Yes the GPIO 0 was plugged into the SSR 3-32V+ and the ground was plugged into the SSR - There was nothing connected to the SSR load side during my test.

@Pavils-Jurjans Ok, finally, got this working! The missing data problem was solved by changing the frequency to 200KHz. Apparently, the hardware SPI gets unreliable with low frequencies. Now I wonder what is the maximum frequency, as I tried 3.2MHz and it still works (For my 300 pixel APA102 RGB LED strip, I measure about 200 updates per second).

Indeed a cool upgrade. Now I'd be great if: the ALSA bug that prevents any audio play on newer firmwares was fixed (https://community.onion.io/topic/2910/kernel-panic-with-pulseaudio/2) the SPI RX bug preventing anything to be read via SPI was fixed (https://github.com/OnionIoT/spi-gpio-driver/issues/4#issuecomment-419640799) But, one thing at a time