Yes it is optional as you can write to the OLED with the OLED command from Rules, if you do not want to use automatic refresh feature...
As i tested it is fixed in the latest commit. https://github.com/enesbcs/rpieasy/comm ... 10875234ac
Moderators: grovkillen, Stuntteam, TD-er, enesbcs
Yes it is optional as you can write to the OLED with the OLED command from Rules, if you do not want to use automatic refresh feature...
As i tested it is fixed in the latest commit. https://github.com/enesbcs/rpieasy/comm ... 10875234ac
Dear enesbcs,enesbcs wrote: ↑19 Mar 2019, 18:57Yes it is optional as you can write to the OLED with the OLED command from Rules, if you do not want to use automatic refresh feature...As i tested it is fixed in the latest commit. https://github.com/enesbcs/rpieasy/comm ... 10875234ac
It's more easier than I thought.... just click on the blue link... et voila it's automatically installed...henkdejonge wrote: ↑20 Mar 2019, 14:11 I would like to use the RFID / Wiegand reader. But the dependencies shows that i'm missing wiegand.io I've tried all kind of things but I can't get it to work.
Henk.
I have'nt got any project that can benefit from remembering last state, but if you need it, i can add a filter to remember pin state only if type is pure Output.
If it is possible I will thankful to you. Sometimes the system (raspian)would be crash and need to be reboot by schedule or manually when that happen all scenery would be wrong if the GPIO doesnot remember last state. Easy ESP firmware already has that propery and it really help for the regular operations. Please add that property to the magnificent RPIEasy
If the OS crashed OR the SD card is not in a writable state, there are no way that the system will remember it's last state...
Second boot: Previous value of 1 restored...20:14:20: Pi Zero W 40 pins
20:14:20: State preserving is enabled
20:14:20: Event: System#Boot
20:14:20: Webserver starting at port 80
20:14:20: Event: Clock#Time=Wed,20:14
20:14:37: CMD: gpio,17,1
20:14:37: BCM17 set to 1
20:14:37: Event: 17#State=1
20:14:44: CMD: reboot
20:14:44: Event: System#Shutdown
... then setted to 0 with gpio command and reboot20:15:18: Pi Zero W 40 pins
20:15:19: Event: 17#State=1
20:15:19: 17: Restoring previous GPIO value 1
20:15:19: State preserving is enabled
20:15:19: Event: System#Boot
20:15:19: Webserver starting at port 80
20:15:20: Event: Clock#Time=Wed,20:15
Third boot: Previous value was 0 so there are nothing to do as it is already zero at boot...20:16:00: Event: Clock#Time=Wed,20:16
20:16:05: CMD: gpio,17,0
20:16:05: BCM17 set to 0
20:16:05: Event: 17#State=0
20:16:12: CMD: reboot
20:16:12: Event: System#Shutdown
20:16:44: Pi Zero W 40 pins
20:16:46: State preserving is enabled
20:16:46: Event: System#Boot
20:16:46: Webserver starting at port 80
20:16:46: Event: Clock#Time=Wed,20:16
20:17:06: Event: Clock#Time=Wed,20:17
How can you paste the logs here, my logs are disappear after reboot. Issue still continue from my side. Sorry about that, I know you do too much efford to me and my topic20:14:20: Pi Zero W 40 pins
20:14:20: State preserving is enabled
20:14:20: Event: System#Boot
20:14:20: Webserver starting at port 80
20:14:20: Event: Clock#Time=Wed,20:14
20:14:37: CMD: gpio,17,1
20:14:37: BCM17 set to 1
20:14:37: Event: 17#State=1
20:14:44: CMD: reboot
20:14:44: Event: System#Shutdown
If you do not see "State preserving is enabled" at logs, than it will not work of course. Remove and backup full rpieasy, then reinstall it from github and try again. If you do not see State preserve option at P029 than it is more than interesting, if you checked this option and did not show up, than your pin mode maybe not Output.
I connect to raspian with putty then apply your script that you mention above but ater restart RPIEasy putty warn me "server unexpectedly closed network connection". So connection is closed and cannot able to see the logs. I set 10 second seconds between keep alives then tick enable TCP keepalives option at putty but still lose conection after rebooting RPIEasy. Can you share your putty settings to meenesbcs wrote: ↑21 Mar 2019, 18:15If you do not see "State preserving is enabled" at logs, than it will not work of course. Remove and backup full rpieasy, then reinstall it from github and try again. If you do not see State preserve option at P029 than it is more than interesting, if you checked this option and did not show up, than your pin mode maybe not Output.
I am using ssh console to get logs. If you entering into ssh with any user, than enter "sudo su" this way you entering into root console after enter "screen -r" and if you are using with the preferred autostart way with screen, than you will get console log, which you can copy-paste.
Sorry i do not use Windows. I am using Ubuntu Linux with real ssh client, and it's screen remains readable after disconnect.asuz wrote: ↑22 Mar 2019, 16:24 I connect to raspian with putty then apply your script that you mention above but ater restart RPIEasy putty warn me "server unexpectedly closed network connection". So connection is closed and cannot able to see the logs. I set 10 second seconds between keep alives then tick enable TCP keepalives option at putty but still lose conection after rebooting RPIEasy. Can you share your putty settings to me![]()
This type of message coming from P001 (which is for input pins only) when this input pin state is already watched by another process.
Hello enesbcs,
The only reason can be that you are not using the Output helper plugin.
<5>RPIEasy RPIEasy: Event: isi#Temperature=23.0 192.168.4.57 26/03 00:36:48.742
Nice project! I've never used the "Display button" setting before... is it simply switching on and off the display?
more precise ... it switches the back light.is it simply switching on and off the display?
Display button added to P012 plugin at commit https://github.com/enesbcs/rpieasy/comm ... 3d4e066129
Thank you very much again for that effortenesbcs wrote: ↑30 Mar 2019, 18:33Display button added to P012 plugin at commit https://github.com/enesbcs/rpieasy/comm ... 3d4e066129
Hi,henkdejonge wrote: ↑10 Apr 2019, 10:11 Hi,
I still got a small issue. I can't get pygame installed. Tried all kind of things but NOGO.
Henk
Code: Select all
cat /etc/os-release
dpkg -s python3-pip
cat /etc/apt/sources.list
Code: Select all
sudo apt-get update
sudo apt-get install python3-pip
sudo pip3 install pygame
I see. Please try:henkdejonge wrote: ↑11 Apr 2019, 09:18 I've run the commands as requested. Everything went well. Only the last command for installing pygame exited with a error code 1.
Attached the output.
Code: Select all
sudo apt-get install libsdl1.2-dev
Code: Select all
sudo pip3 install pygame
Hi!henkdejonge wrote: ↑12 Apr 2019, 15:43 Hi,
Tried the command... same result...I think I'll try to reinstall the whole stuff from the beginning. Nice job for the weekend..
Thanks anyway for your support.. or perhaps somethings else pops up in your head..
Henk.
Code: Select all
sudo apt-get install libsdl-image1.2-dev libsdl-mixer1.2-dev libsdl-ttf2.0-dev libsdl1.2-dev ffmpeg libfreetype6-dev python3-dev
Thank you for your feedback I've added extra dependencies in todays commit to RPIEasy.
I am not sure if real-time pulse counting is even possible in Python language on a multi-tasking operating system. Please show me a working example for Raspberry and i will look into it.bennybubble wrote: ↑24 May 2019, 18:12 Hi,
I really like the RPIeasy initiative, same look and feel as the originial ESPeasy !
To get more I/O, I'm replacing an 8266 with a RPI but now I'm almost there, I see there is no Generic - Puls Counter plugin.
Are there plans to make such a plugin ?
-ben
What is the defintion of real-time?enesbcs wrote: ↑24 May 2019, 19:09I am not sure if real-time pulse counting is even possible in Python language on a multi-tasking operating system. Please show me a working example for Raspberry and i will look into it.bennybubble wrote: ↑24 May 2019, 18:12 Hi,
I really like the RPIeasy initiative, same look and feel as the originial ESPeasy !
To get more I/O, I'm replacing an 8266 with a RPI but now I'm almost there, I see there is no Generic - Puls Counter plugin.
Are there plans to make such a plugin ?
-ben
Yes one per second can be achieved if it is enough.bennybubble wrote: ↑24 May 2019, 19:50 What is the defintion of real-time?
In my case I want to count pulses from my gas- and energymeter, puls rate would be less then 1 Hz ...
I don't think this would be an issue with Python running on RPI/Raspbian.
-ben
It would be great if this could be implemented, can't you use edge-based-interrupt for counting (https://parg.co/hbz) ?enesbcs wrote: ↑24 May 2019, 21:37Yes one per second can be achieved if it is enough.bennybubble wrote: ↑24 May 2019, 19:50 What is the defintion of real-time?
In my case I want to count pulses from my gas- and energymeter, puls rate would be less then 1 Hz ...
I don't think this would be an issue with Python running on RPI/Raspbian.
-ben
https://github.com/enesbcs/rpieasy/issues/65bennybubble wrote: ↑27 May 2019, 12:31 It would be great if this could be implemented, can't you use edge-based-interrupt for counting (https://parg.co/hbz) ?
I'm more then happy to test it if needed !
-ben
Thanks, I will test it this weekend!enesbcs wrote: ↑27 May 2019, 17:08https://github.com/enesbcs/rpieasy/issues/65bennybubble wrote: ↑27 May 2019, 12:31 It would be great if this could be implemented, can't you use edge-based-interrupt for counting (https://parg.co/hbz) ?
I'm more then happy to test it if needed !
-ben
Thank you!pirquadrat wrote: ↑28 May 2019, 11:13 Hi!
I already use ESPEasy and found your project today. I must say: great work! That's a thing for a Raspberry Pi I was long looking for. Really nice idea![]()
But let me ask one question: do you plan to support FHEM as a controller? Or is MQTT the only way for now and near future?
Best regards
Hi,
Thank you for your suggestion, but in the last 12 months i tried everything to avoid usage of pigpio and its background services, and i want to continue this practice. I hope that someday the LIRC kernel driver can be used properly from python.StefanD wrote: ↑06 Aug 2019, 21:58 Hi Enesbcs,
regarding infrared plugin I want to tell you that am using with success in other python application pigpio library and according with the documentation it is also capable to be an alternative to lirc for transmitting and receiving IR codes. You can check this link :
https://raspberrypi.stackexchange.com/q ... g-ir-codes
and for python example this link:
http://abyz.me.uk/rpi/pigpio/examples.h ... on_irrp_py
Waiting your feedback
Best regards
Hi!StefanD wrote: ↑15 Aug 2019, 10:53 Hi Enesbcs,
looking at the plugins implemented in rpieasy I found one that looks very promising for me. It is about plugin P511 - Run OS command. My question is: with this command it is possible to run/stop any executable script even it is not a python3 script? Can be used in rules ? Please give me some details about this plugin...
Thank you
Yes, the reason is that status array is not implemented yet.
Users browsing this forum: No registered users and 9 guests