This page last changed on Nov 08, 2013 by phil1348.
After a first test of Openremote on a old Via Epia server, I decided to turn to a Raspberry controller.
This is a very cheap combination both for purchase as for power requirement.
This was a good experience :
USB interface was not basically working. After solving this, the most tricky was to get a stable system, and the most important, a self rebooting system after i.e power shutdown.
I think I now get it. For the one interested, I'm open to share my experience.
If there is interest, I will try to post some resume of all the point I had to solve.
Great. Thanks for sharing.
You can post your results here or maybe later we can create a How-To.
Posted by mredeker at Nov 09, 2013 19:27
After now one year experience, I have to conclude that raspberry (for remind, sold as educational device) is not enough reliable for this usage.
It did work very nicely at the beginning, but the behavior becomes more and more erratic with the time.
The two biggest problems are :
- Erratic restart after main power shutdown (what is frequent were it is installed, in France mountains area). Even adding a UPS did not completly solve the problem. The USB is not reconnected all the times, without physically disconnect-reconnect, ethernet reconnection is not 100% reliable etc..
- More and more erratic restart of OR after controller synchronisation.
- The same when "soft restart", such as reboot command.
- SD card corrupted, what seems to be a known problem on Raspberry PI.
Thus, it's a good base to start and try, but it can only be used for "confort display". It cannot be used for heating regulation for example, cannot be used if you are not, as developper, on site. And for sure, cannot be used as a commercial product.
I will then conclude that I will not post any tutorial about "how to".
But I'm still open to share with others my experience.
For now, I will still continue with experiments..but I will have to turn to a more robust computer solution.
Does anyone can confirm than Synology would be a good option ?
Posted by phil1348 at Jan 23, 2015 13:30
I agree there could be more reliable HW solutions than raspberry expecially in terms of resiliency after power outages; however not sure you can achieve a reliable restart in all cases using a single system even different from raspberry. Self-healing/whatchdog processes can help but have intrinsic limitation as they run on the same machine.
For unattended systems controlling important stuff like heating or security, in mi view the best is to put another system in parallel checking the main one. In my experience, a system that is very predictable and reliable is Arduino. I have personally never experienced a case of a wrong restart with Arduino...
So, one solution could be to enable a serial communication between OR system and Arduino with the former sending periodical messages and the latter checking consistency. In case of discrepancies, Arduino would take-over restarting in hardware the OR system or sending an alarm or whatever. More important, Arduino can force to a know state its I/O during this phase.
A more simple solution with Raspberry is to toggle one of its Output through a Rule and make arduino checking this toggle. This would ensure Rule engine is working....
Perhaps a bit overkilling, but in my view is the best you can achieve keeping the overall solution low cost, low power consumption and simple.
just my thought....
Posted by galbip at Jan 25, 2015 10:00