Skip to content

Frequently Asked Questions

Jump to bottom
Alexander Nagy edited this page Jun 24, 2020 · 4 revisions

Why Raspberry Pi?

  • My first SBC was a Raspberry PI Zero W, my second was an Orange Pi Zero W. Stability and usability is much more better on the Raspberry side, so since then, i'm only using Raspberry's.

Can other SBC's used with RPIEasy?

  • In theory any Debian/Ubuntu Linux based PC can be used to run RPIEasy, but only with a subset of plugins. If someone really wants for a specific SBC support, than send it to me, and i will see. (For Orange Pi and USB FTDI it is mostly done at 2020) The complete GPIO layer has to be redone to complete this task...

Why Python? It is so ...

  • I know that for some time-sensitive operations Python is not the best. But it is easy (to me at least) to code and can be fixed quickly if made some mistakes, without compilation. :) And last but not least: there are a ton of different sample codes for python and raspberry.

Why Linux only?

  • However some basic plugins may be used with a Windows PC (untested&unlikely), but Windows compatibility is not something what i am planning in the near future, sorry. Come on, RPI best to use with Linux.

Why xyz functions not works the same way in RPIEasy than ESPEasy?

  • Simple: RPIEasy is Not ESPEasy. I tried my best to copy the look&feel and usability with some limits that serves better interoperability and modularity. I admit that ESPEasy is the most coolest thing i've seen, but i have my own thought about how an SBC have to report data. For example two way communication in controllers is a must have, and "taskvalueset" command not just sets a user value in memory, but do other stuffs, that the plugin handles. (such as changes it's dedicated GPIO, or making some noise, or setting an usb relay,etc

Why xyz command not works without the plugin that contains it?

  • The answer is in the question. A good example for it the Switch plugin and the GPIO command. (Modularity was my primary goal) If max 48 tasks is not enough for you, i will raise it to 256.

I have enabled a Switch plugin, and installed the RPi.GPIO dependency. GPIO still not works, why?

  • You must be an advanced ESPEasy user, and skipped the Raspberry PI class. :) RPIEasy goal was to made it easy to use functions, but it does not replace knowledge. You have to setup the pin usage mode, INPUT (including PullDown or Pullup) or OUTPUT before use. This is why i've created Hardware/Pinouts&Ports settings page, not just for decoration. After you choose proper modes, a reboot may or may not needed.

I can not setup pin states at the Pinout&Ports page!

  • Sorry, there are some Linux distributions that mounts / directory in readonly mode to prevent data corruption or /boot partition is mounted in RO mode after a non-clean shutdown. You have to run e2fsck or similar to fix filesystem error or made any necessary actions to make /boot/config.txt file writable, or modify it manually.

Why do not you create SD card image for RPI A/B/Zero?

  • I repeat: modularity is a primary goal. And always making a 2GB image for a 100kb script that changes 5 times in a week?

Why there are a lot of bugs and issues in RPIEasy?

  • I am not a real programmer, just a hobby programmer. I have a day job in property protection business, with a lots of work to do. Still try to fix errors in my spare time if i can, and upgrade my home system. (involving several Raspberry's and ESP8266's)

Why xyz device is not supported?

  • Perhaps i do not have one. Or i do not have enough time. Again, i have a day job, and sometimes i have to sleep. :) If you really want to support a specific device send me one or make a small donation to make me sleep less. ;) Just kidding, this program is free, and it has to be. In most cases it just a matter of time. One year, or maybe two. :) Open a new issue and we will see.

I've found a bug, what should i do?

Why not merging efforts with uPyEasy?

  • MicroPython and Python3 are similar, but not the same. Read on if you do not believe me.
Clone this wiki locally