Help, homeduino not working anymore [Solved]
Hi guys,
after re-installing my raspberry (Model B Rev 2) from scratch (4.9.59+, pimatic 0.9.42, pimatic-homeduino" (0.9.11)) and following instructions from @layereight … unfortunately my homeduino plugin still doesn’t work. Plugin in works ("[pimatic-homeduino] info: Connected to homeduino device.").
Just to confirm (while I am searching for the error): I don’t need the gpio plugin-in anymore? and the driver “gpio” is already installed somewhere?
Hey @Wolf,
the whole thread is only related to the “gpio” driver of the homeduino plugin. So 433MHz sender/receiver directly connected to the GPIO of your pi.
The configuration of the homeduino plugin didn’t change, except for the GPIO pin configuration. See https://github.com/layereight/virtualhomeduino
“Added pigpio library support, configuration uses GPIO pin numbers instead of wiringPI pin numbers.”
So if you use 433MHz sender/receiver directly connected to the GPIO of your pi and you use the “vhduino” binary compiled from my fork the configuration stays the same, except for the GPIO pin numbering (receiverPin and transmitterPin in the homduino configuration).
Also see: http://wiringpi.com/pins/
@layereight : thank you very much, it was the different GPIO pin configuration. I overlooked the comment and used the “old” wiringpi ones.
Now it works again!
sure @layereight: on average about 9,6% cpu
thanks. I was asking because I made a similar observation. And I believe this CPU utilization is much higher than the old binary, before @DaanNL’s adaptations.
@mwittig @leader21 @sweetpi Maybe it’s time for a review of the changes that @DaanNL and I did: https://github.com/layereight/virtualhomeduino
For me the cpu usage of vhduino is about 12% sometimes a bit more up to 17% and bit less down to 10%.
I’m using the standard version of homeduino v0.9.11 and a directly connected receiver and transmitter at the gpios of my raspberry.
really? Maybe I’m mistaken then. Perhaps the CPU utilization of the old binary was higher than I thought.
@Fabian: Can you do me the favour and compile the vhduino binary from my fork and run it on the same piece of hardware so we can have a direct comparison? That’d be really great! See https://github.com/layereight/virtualhomeduino
@layereight sure. I will give it a try tomorrow and report (hopefully) results.
Is it also possible to isolate only the cpu usage of vhduino and log it? This will give an objective comparison.
so i tried to log the cpu usage of the vhduino process with this command
while true; do i=$(date +"%H:%M:%S")' '$(ps -eo pid,pcpu,pmem,args --sort=pcpu c| grep vhduino); echo $i; echo $i >> vhduinologfile.log; sleep 1; done;
but the result is not varying. Therefore I only post some lines…
%date %PID %CPU %MEM %CMD
23:22:37 27622 12.7 1.1 vhduino
23:22:38 27622 12.7 1.1 vhduino
23:22:39 27622 12.7 1.1 vhduino
23:22:40 27622 12.7 1.1 vhduino
...
23:24:53 27622 12.7 1.1 vhduino
23:24:54 27622 12.7 1.1 vhduino
23:24:55 27622 12.7 1.1 vhduino
23:24:56 27622 12.7 1.1 vhduino
...
23:42:00 27622 12.7 1.1 vhduino
23:42:01 27622 12.7 1.1 vhduino
23:42:02 27622 12.7 1.1 vhduino
23:42:03 27622 12.7 1.1 vhduino
...
23:48:19 27622 12.7 1.1 vhduino
23:48:20 27622 12.7 1.1 vhduino
23:48:21 27622 12.7 1.1 vhduino
same happens for me. While the CPU usage in top is ever-changing, it stays the same with ps.
Is 12.7% the old or the new vhduino binary?
@layereight 12,7 % is the cpu usage of the old vhduino binary.
I just tried to get your binary running but there are some problems…
14:02:25.259 2018-01-07 Sunday
14:02:34.677 [pimatic] info: Starting pimatic version 0.9.42
14:02:40.043 [pimatic, ppm] info: 2.15.12
14:02:40.178 [pimatic] info: Loading plugin: "pimatic-cron" (0.8.8)
14:02:41.044 [pimatic] info: Loading plugin: "pimatic-mobile-frontend" (0.9.12)
14:02:42.338 [pimatic] info: Loading plugin: "pimatic-gpio" (0.9.0)
14:02:42.457 [pimatic] info: Loading plugin: "pimatic-ping" (0.9.5)
14:02:42.537 [pimatic] info: Loading plugin: "pimatic-shell-execute" (0.9.11)
14:02:42.622 [pimatic] info: Loading plugin: "pimatic-mythermostat" (0.0.3)
14:02:42.710 [pimatic] info: Loading plugin: "pimatic-denon-avr" (0.9.9)
14:02:43.686 [pimatic] info: Loading plugin: "pimatic-iframe" (0.3.1)
14:02:43.736 [pimatic] info: Loading plugin: "pimatic-dht-sensors" (0.9.3)
14:02:43.782 [pimatic] info: Loading plugin: "pimatic-sunrise" (0.8.7)
14:02:43.843 [pimatic] info: Loading plugin: "pimatic-openweather" (0.9.4)
14:02:43.953 [pimatic] info: Loading plugin: "pimatic-sysinfo" (0.9.4)
14:02:44.249 [pimatic] info: Loading plugin: "pimatic-filebrowser" (0.9.0)
14:02:44.454 [pimatic] info: Loading plugin: "pimatic-filter" (0.9.3)
14:02:44.546 [pimatic] info: Loading plugin: "pimatic-samsung-tv" (0.9.0)
14:02:44.603 [pimatic] info: Loading plugin: "pimatic-links" (0.8.6)
14:02:44.642 [pimatic] info: Loading plugin: "pimatic-upnp-root" (0.8.9)
14:02:44.888 [pimatic] info: Loading plugin: "pimatic-wakeonlan" (0.9.4)
14:02:44.965 [pimatic] info: Loading plugin: "pimatic-homeduino" (0.9.11)
14:02:46.123 [pimatic] info: Loading plugin: "pimatic-telegram" (1.1.6)
14:02:47.549 [pimatic] info: Loading plugin: "pimatic-amazing-dash-button" (0.9.14)
14:02:47.665 [pimatic] info: Loading plugin: "pimatic-chronotherm" (0.9.8-10)
...
14:03:21.946 [pimatic] error: Got string value for attribute start of VariablesDevice but attribute type is number.
14:03:21.950 [pimatic] error: Got string value for attribute stop of VariablesDevice but attribute type is number.
14:03:21.981 [pimatic] error: Got string value for attribute start of VariablesDevice but attribute type is number.
14:03:21.985 [pimatic] error: Got string value for attribute stop of VariablesDevice but attribute type is number.
14:03:22.052 [pimatic] error: Got string value for attribute start of VariablesDevice but attribute type is number.
14:03:22.056 [pimatic] error: Got string value for attribute stop of VariablesDevice but attribute type is number.
14:03:23.575 [pimatic-ping] warn: Error on ip lookup of Fritz: Error: queryA ENOTFOUND Fritz
14:03:23.690 [pimatic-homeduino] debug: data: "ready"
14:03:23.785 [pimatic-shell-execute] error: [ShellSwitch#Sonoff_Wohnzimmer_Switch] Error: unknown state=""!
14:03:23.999 [pimatic] warn: Could not update variable Sonoff_Wohnzimmer_Switch.state: undefined
14:03:24.005 [pimatic-shell-execute, ShellSwitch] error: Error getting attribute value Sonoff_Wohnzimmer_Switch.state: undefined
Unhandled rejection Error: unknown state=""!
14:03:25.453 [pimatic-homeduino] info: Connected to homeduino device.
14:03:26.124 [pimatic-mobile-frontend] info: packing static assets
14:03:30.892 [pimatic-mobile-frontend] info: packing static assets finished
14:03:30.904 [pimatic-mobile-frontend] info: rendering html
14:03:34.839 [pimatic-homeduino] debug: data: "ACK"
14:03:34.857 [pimatic-homeduino] debug: data: "2018-01-07 14:03:25 sigHandler: Unhandled signal 11, terminating"
unknown message received: 2018-01-07 14:03:25 sigHandler: Unhandled signal 11, terminating
14:03:34.861 [pimatic-homeduino] debug: data: ""
unknown message received:
14:03:35.062 [pimatic-homeduino] debug: Receiving on pin 17
[bot.info] bot started
14:03:45.073 [pimatic-mobile-frontend] info: rendering html finished
14:03:45.341 [pimatic] info: Listening for HTTPS-request on port 443...
14:03:45.344 [pimatic] info: Listening for HTTP-request on port 80...
14:08:46.348 [pimatic-homeduino] debug: data: "PING"
I’ll try it again from beginning… 
so i tried it again but the output stayes the same. Here is the log of installig process:
pi@raspberrypi:~ $ sudo service pimatic stop
pi@raspberrypi:~ $ sudo apt-get install pigpio build-essential git
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
build-essential ist schon die neueste Version.
git ist schon die neueste Version.
pigpio ist schon die neueste Version.
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
pi@raspberrypi:~ $ git clone https://github.com/layereight/virtualhomeduino.git
Klone nach 'virtualhomeduino'...
remote: Counting objects: 177, done.
remote: Total 177 (delta 0), reused 0 (delta 0), pack-reused 177
Empfange Objekte: 100% (177/177), 297.12 KiB | 0 bytes/s, Fertig.
Löse Unterschiede auf: 100% (78/78), Fertig.
Prüfe Konnektivität... Fertig.
pi@raspberrypi:~ $ cd virtualhomeduino
pi@raspberrypi:~/virtualhomeduino $ make -f Makefile.rpi
git clone https://github.com/pimatic/RFControl.git
Klone nach 'RFControl'...
remote: Counting objects: 257, done.
remote: Total 257 (delta 0), reused 0 (delta 0), pack-reused 257
Empfange Objekte: 100% (257/257), 80.38 KiB | 0 bytes/s, Fertig.
Löse Unterschiede auf: 100% (136/136), Fertig.
Prüfe Konnektivität... Fertig.
cd RFControl; git checkout -q 70413e8
g++ -Wall -O3 -DRF_CONTROL_VARDUINO=1 -c "pigpio_functions.cpp"
g++ -Wall -O3 -DRF_CONTROL_VARDUINO=1 -c "pigpio_rfcontrol.cpp"
g++ -Wall -O3 -DRF_CONTROL_VARDUINO=1 -c "virtualhomeduino.cpp"
g++ -Wall -O3 -o vhduino pigpio_functions.o pigpio_rfcontrol.o virtualhomeduino.o -lpthread -lpigpio -lrt
Success! Done compiling vhduino.
pi@raspberrypi:~/virtualhomeduino $ sudo cp vhduino /home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/bin/vhduino
last update:
The use of the old binary is working well.
If you can help me solving the problem I’ll give it another try.
Questions that might help:
Did you pay attention to the changed pin numbering in the configuration? The old vhduino used the wiringpi library the new uses pigpio to access the GPIO interface. You will definitely have to change your receiverPin and transmitterPin in the homeduino configuration.
Did you follow the “Testing” procedure from the docu in my fork? Which is:
See:
http://wiringpi.com/pins/
https://github.com/layereight/virtualhomeduino
@layereight Hi, yes that was my first impression also, but I had already configured the pin numbers directly after the make process of homeduino into the config file of pimatic. After starting pimatic (with the errors printed in my last post) I have checked the pin numbers in gui and started pimatic again. But at last, the result stays the same.
I have changed pin numbers
from
receiver Pin 0
transmitter Pin 1
to
receiver Pin 17
transmitter Pin 18
Perhaps I have made some other faults but from my point of view I have followed strictly to your instructions. Do you have another idea?
from your log I can see that your vhduino receives signal 11 (SIGSEGV), which means it crashes with a segmentation fault.
Can you do me the favour and run sudo ./vhduino after you compiled the source from my fork?
For me it shows this:
$ sudo ./vhduino
ready
What does it say for you?
I tested with:
Have you tried upgrading your Raspbian/kernel?
@layereight if have updated and upgraded the raspberry and did a reboot but the output from pimatic is the same as before. So Kernelupdate for firmware version 8 (jessi) from 4.4.49-v7 to 4.9.35-v7 didn’t solve the problem.
Output from sudo ./vhduino is only possible from vhduino folder oder pimatic-homeduino/…
1. Virtualhomeduino
pi@raspberrypi:~/virtualhomeduino $ sudo ./vhduino
2018-01-14 23:40:35 initInitialise: Can't lock /var/run/pigpio.pid
Error initialising pigpio -1
2. Home
pi@raspberrypi:~ $ sudo ./vhduino
sudo: ./vhduino: Kommando nicht gefunden
@layereight
I just started with Pimatic and your version of vhduino fixed my “hardware not supported issue”, so I just wanted to say thank you very much!
Hi @layereight
First of all nice work… I did take a look at your GitHub repo and don’t see any reference to my GitHub… Don’t you think it would be appropriate to have a reference to the original developer when merging my changes in another fork?
Kind Regards,
Daan
Hey @DaanNL,
thanks. And what do you mean? One can clearly see that my repo was forked from yours. It’s the first line on the github page. It says “forked from WebWire-NL/virtualhomeduino”. Same as it says on your repo “forked from pimatic/virtualhomeduino”. That’s standard open source software development.
If you’re afraid not to get the credits you deserve, please, don’t be. You did all the work migrating the project to pigpio, making it compatible for newer kernels. And I really appreciate that. I only did a small cleanup of the project’s build process.
@DaanNL, I added a contributors section to the project’s readme file.
Many pimatic users run into this issue for several months now. My sole intention is to get your work into pimatic’s original repository, @DaanNL. That’s why I did another pull request to the original pimatic repo now.
I know @mwittig alreaady had a look at the project. Let’s hope he will approve one of our PRs soon.
