3 ms·
I've been looking at it many times, but I don't want to add myself work. Say I want to use RF24 (nrf24l01), if I just use raspbian I know it's an environment it
by comboy 6y ago
I've been looking at it many times, but I don't want to add myself work. Say I want to use RF24 (nrf24l01), if I just use raspbian I know it's an environment it's been tested on heavily, that all sensors libraries should just work because everybody is using the same hardware and software (in case of raspberry pi) and if it doesn't, I'm doing something wrong. But with heavily modified environment I don't want to spend 2 days debugging why i2c sometimes doesn't work or something like that. Am I understanding it wrong? Does anybody has some experiences to share?
To clarify I'm doing hobby projects, not industrial applications, but I do expect industrial-level reliability from my home automation.
- lawik 6y agoIf you want the reliability you open yourself to the eventuality that you might have to put in some of the work to achieve it. Things like SPI, I2C and GPIO can be expected to work with Nerves + Elixir Circuits. But some hobby hardware is definitely not straight forward since they tend to have libraries only in Python. I've ported one such myself (Inky eInk display) and many others have contributed similarly. Nerves is good for hobbyists that want a better workflow and more serious and reliable setup. But it focuses on solving for production devices of you compare it to Raspbian.