Any way to get around it crashing when using the GPIOS? I did notice that the "ranges" file mentioned earlier, in my system it is blank except a "-" in it. Is that how it should be?
UPDATE, I wiped out everything and started again. Reflashed rasbian, the newest EasyIoT server. It is all working with the Mydrivers being enabled, if I reboot I need to edit the RPiGPIOConfig file to disable the GPIOs or the server will not boot. This will be fine with me as I just ordered some nrf24's so I can enable the Mysensors driver. But all in all it is working with a few hoops to jump through.
*I did see one issue overnight, my CPU usage was a 50% steady, as soon as I shutdown server when to 0.
**The server is not writing to any of the log files. I followed the instructions on permissions on the build page. Ideas?
FYI, I have found that the v7 image for Raspberry will not boot on RPI2.
tonyn79 wrote: UPDATE, I wiped out everything and started again. Reflashed rasbian, the newest EasyIoT server. It is all working with the Mydrivers being enabled, if I reboot I need to edit the RPiGPIOConfig file to disable the GPIOs or the server will not boot. This will be fine with me as I just ordered some nrf24's so I can enable the Mysensors driver. But all in all it is working with a few hoops to jump through.
*I did see one issue overnight, my CPU usage was a 50% steady, as soon as I shutdown server when to 0.
**The server is not writing to any of the log files. I followed the instructions on permissions on the build page. Ideas?
FYI, I have found that the v7 image for Raspberry will not boot on RPI2.
CPU usage 50% is not normal. I guess this is because you do not have connected NFR24L01 on GPIO. I will investigate why GPIO doesn't work without MySensors driver and fix this in next release.
It looks like it was not liking not being able to write to the logs. I had to chmod 777 on the log directory, I dont know why, but after that the server was able to write to logs. It has been running at about 1% cpu usage since.
tonyn79 wrote: It looks like it was not liking not being able to write to the logs. I had to chmod 777 on the log directory, I dont know why, but after that the server was able to write to logs. It has been running at about 1% cpu usage since.