Web GPIO Status interface doesn't respond about berryio HOT 12 CLOSED

Hi Ken,
It looks like you have two issues, one where you need to set the directions on the GPIO permanently and one where the web interface isn't changing the GPIO mode.

1. Setting the GPIO permanently:
   Unfortunately its not possible to set the GPIO modes permanently because they are reset on bootup and BerryIO doesn't have the ability to set anything at startup. However you can add BerryIO commands in the /etc/rc.local file and they will be run when the Pi starts up. If you edit this file and add your commands on lines just before the "exit 0" command they will run every time your Pi is switched on and should be able to set the GPIO how you want it. Let me know if this works for you. You don't need the sudo as rc.local is run as root but it may be the case that you need to use the full path, for example "/usr/bin/berryio gpio_set_mode 24 out"
2. Mode not changing with the GUI:
   This is an unusual one. I've not seen this before. Can you go to the "About" page and find the gpio_set_mode link and use that and let me know what it says?
   For example to set pin 24 to out:
   http://#### your Pi #####:81/gpio_set_mode/24/out

from berryio.

Hi Daniel,

Thank you very much for responding to me so quickly. Setting the GPIO modes
the way you suggested works fine, thank you.

I'm not exactly sure what you wanted me to do but I put this into my
browser address bar:"http://192.168.0.14:80/gpio_set_mode/24/out"
And got this response:"ERROR: Cannot set pin "24" into mode "out" on the
GPIO Control page.

Regards, Ken

On Sat, Feb 7, 2015 at 2:31 PM, Daniel Bull [email protected]
wrote:

Hi Ken,
It looks like you have two issues, one where you need to set the
directions on the GPIO permanently and one where the web interface isn't
changing the GPIO mode.

Setting the GPIO permanently:
Unfortunately its not possible to set the GPIO modes permanently
because they are reset on bootup and BerryIO doesn't have the ability to
set anything at startup. However you can add BerryIO commands in the
/etc/rc.local file and they will be run when the Pi starts up. If you edit
this file and add your commands on lines just before the "exit 0" command
they will run every time your Pi is switched on and should be able to set
the GPIO how you want it. Let me know if this works for you. You don't need
the sudo as rc.local is run as root but it may be the case that you need to
use the full path, for example "/usr/bin/berryio gpio_set_mode 24 out"
2.

Mode not changing with the GUI:
This is an unusual one. I've not seen this before. Can you go to the
"About" page and find the gpio_set_mode link and use that and let me know
what it says?
For example to set pin 24 to out:
http://#### your Pi #####:81/gpio_set_mode/24/out

—
Reply to this email directly or view it on GitHub
#22 (comment).

Ken Ironside & Associates
voice & fax: +27 44 343 2031
mobile: +27 82 881 0665
email: [email protected]

"If we knew what we were doing, we wouldn't call it research..."

[image: Facebook] http://www.facebook.com/kenironside [image: Twitter]
http://www.twitter.com/kenironside [image: LinkedIn]
http://za.linkedin.com/in/kenironside [image: about.me]
http://www.about.me/kenironside

from berryio.

Thanks Ken, thats what I wanted you to do.
It looks like something is preventing the BerryIO web interface from changing the GPIO mode.
Could you run the following commands for me and let me know the output:
sudo /usr/share/berryio/scripts/gpio_set_export_permissions.sh
sudo /usr/share/berryio/scripts/gpio_set_device_permissions.sh

from berryio.

$ sudo /usr/share/berryio/scripts/gpio_set_export_permissions.sh
$ The user www-data' is already a member ofgpio'.

$ sudo /usr/share/berryio/scripts/gpio_set_device_permissions.sh
$ The user www-data' is already a member ofgpio'.
chgrp: cannot access /sys/devices/virtual/gpio': No such file or directory chmod: cannot access/sys/devices/virtual/gpio': No such file or directory

from berryio.

Hi Daniel,

There's no file or subdirectory in /sys/devices/virtual/ called 'gpio'

On Sat, Feb 7, 2015 at 4:04 PM, Daniel Bull [email protected]
wrote:

Thanks Ken, thats what I wanted you to do.
It looks like something is preventing the BerryIO web interface from
changing the GPIO mode.
Could you run the following commands for me and let me know the output:
sudo /usr/share/berryio/scripts/gpio_set_export_permissions.sh
sudo /usr/share/berryio/scripts/gpio_set_device_permissions.sh

—
Reply to this email directly or view it on GitHub
#22 (comment).

Ken Ironside & Associates
voice & fax: +27 44 343 2031
mobile: +27 82 881 0665
email: [email protected]

"If we knew what we were doing, we wouldn't call it research..."

[image: Facebook] http://www.facebook.com/kenironside [image: Twitter]
http://www.twitter.com/kenironside [image: LinkedIn]
http://za.linkedin.com/in/kenironside [image: about.me]
http://www.about.me/kenironside

from berryio.

I just tried it on 3 of my Pi's and the folder is there but I got someone else who has the latest version of Raspbian to test and they say its also missing :(
So it looks like something has changed in Raspbian and now the GPIO is moved/missing :(
Please give me some time to investigate this...

from berryio.

Hi Daniel,

No problem, I'm just so grateful that you might be able to help!

Po pressure from me.

Regards, Ken

On Sat, Feb 7, 2015 at 4:28 PM, Daniel Bull [email protected]
wrote:

I just tried it on 3 of my Pi's and the folder is there but I got someone
else who has the latest version of Raspbian to test and they say its also
missing :(
So it looks like something has changed in Raspbian and now the GPIO is
moved/missing :(
Please give me some time to investigate this...

—
Reply to this email directly or view it on GitHub
#22 (comment).

Ken Ironside & Associates
voice & fax: +27 44 343 2031
mobile: +27 82 881 0665
email: [email protected]

"If we knew what we were doing, we wouldn't call it research..."

[image: Facebook] http://www.facebook.com/kenironside [image: Twitter]
http://www.twitter.com/kenironside [image: LinkedIn]
http://za.linkedin.com/in/kenironside [image: about.me]
http://www.about.me/kenironside

from berryio.

Hi Ken,
Thanks for letting me know about this issue and your patience in getting it resolved. The issue was indeed that the GPIO virtual device files had moved in the latest version of Raspbian.

I know this sounds odd but please could you run berryio upgrade twice and let me know if it fixes the problem after the second run.

Thanks

from berryio.

Hi Daniel,

OK, progress! The GPIO Control screen is now reflecting the state of the
pins and the pin states can be changed from the GUI. However, the switches
appear but they don't switch on and off. The switches don't appear to be
clickable.

Regards, Ken

On Sat, Feb 7, 2015 at 7:28 PM, Daniel Bull [email protected]
wrote:

Hi Ken,
Thanks for letting me know about this issue and your patience in getting
it resolved. The issue was indeed that the GPIO virtual device files had
moved in the latest version of Raspbian.

I know this sounds odd but please could you run berryio upgrade twice and
let me know if it fixes the problem after the second run.

Thanks

—
Reply to this email directly or view it on GitHub
#22 (comment).

Ken Ironside & Associates
voice & fax: +27 44 343 2031
mobile: +27 82 881 0665
email: [email protected]

"If we knew what we were doing, we wouldn't call it research..."

[image: Facebook] http://www.facebook.com/kenironside [image: Twitter]
http://www.twitter.com/kenironside [image: LinkedIn]
http://za.linkedin.com/in/kenironside [image: about.me]
http://www.about.me/kenironside

from berryio.

Hi Daniel, apologies, the switches do work - I didn't see that I needed to
click on the 'On' and 'Off' writing.

Thanks you so much!

Regards, Ken

On Sat, Feb 7, 2015 at 7:28 PM, Daniel Bull [email protected]
wrote:

Hi Ken,
Thanks for letting me know about this issue and your patience in getting
it resolved. The issue was indeed that the GPIO virtual device files had
moved in the latest version of Raspbian.

I know this sounds odd but please could you run berryio upgrade twice and
let me know if it fixes the problem after the second run.

Thanks

—
Reply to this email directly or view it on GitHub
#22 (comment).

Ken Ironside & Associates
voice & fax: +27 44 343 2031
mobile: +27 82 881 0665
email: [email protected]

"If we knew what we were doing, we wouldn't call it research..."

[image: Facebook] http://www.facebook.com/kenironside [image: Twitter]
http://www.twitter.com/kenironside [image: LinkedIn]
http://za.linkedin.com/in/kenironside [image: about.me]
http://www.about.me/kenironside

from berryio.

Excellent news :)
Thanks for helping me test this Ken.

from berryio.

No, thank you for the amazing fast fix! Gotta love open source!

Go well!

Regards, Ken

On Sat, Feb 7, 2015 at 7:42 PM, Daniel Bull [email protected]
wrote:

Excellent news :)
Thanks for helping me test this Ken.

—
Reply to this email directly or view it on GitHub
#22 (comment).

Ken Ironside & Associates
voice & fax: +27 44 343 2031
mobile: +27 82 881 0665
email: [email protected]

"If we knew what we were doing, we wouldn't call it research..."

[image: Facebook] http://www.facebook.com/kenironside [image: Twitter]
http://www.twitter.com/kenironside [image: LinkedIn]
http://za.linkedin.com/in/kenironside [image: about.me]
http://www.about.me/kenironside

from berryio.