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?
Help, homeduino not working anymore [Solved]
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.
Hi @bramboomen,
glad it works for you.
you will have to stop pimatic before you run sudo ./vhduino
in the virtualhomeduino directory. It’s because there is another instance of vhduino
running and it cannot lock the pid file.
@layereight your right. I have done that while pimatic was runnging. So the output for me is also ready from both directories
pi@raspberrypi:~/virtualhomeduino $ sudo ./vhduino
ready
pi@raspberrypi:~/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/bin $ sudo ./vhduino
ready
perhaps this problem is caused by pigpio? Do you have anthother idea how to solve the problem?
Thank you so far!
hmm, looks good so far. No segmentation fault. And it still doesn’t work for you? Do you still get the same error message from [pimatic-homeduino]
in your pimatic log file?
My remote forensic skills kinda hit their limits here. I can’t really tell what you’re doing wrong.
Are you really sure your homeduino config is correct? Not only the pin numbering?
What’s the exact hardware you’re running on?
Also maybe: Did you stop pimatic before you copied the new vhduino
binary from ~/virtualhomeduino
to ~/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/bin
?
@layereight i just copied the file again to the folder just to make sure, but the problem is still present while starting pimatic.
pi@raspberrypi:~ $ sudo service pimatic stop
pi@raspberrypi:~ $ sudo service pimatic status
● pimatic.service - LSB: pimatic service
Loaded: loaded (/etc/init.d/pimatic)
Active: inactive (dead) since So 2018-01-21 19:52:37 CET; 2min 3s ago
Process: 19142 ExecStop=/etc/init.d/pimatic stop (code=exited, status=0/SUCCESS)
Process: 2245 ExecStart=/etc/init.d/pimatic start (code=exited, status=0/SUCCESS)
Jan 21 18:48:05 raspberrypi pimatic[2245]: Started.
Jan 21 18:48:05 raspberrypi systemd[1]: Started LSB: pimatic service.
Jan 21 18:49:11 raspberrypi sudo[2477]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/local/bin/github-changes -o...TIC.md
Jan 21 18:49:11 raspberrypi sudo[2477]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jan 21 18:49:59 raspberrypi sudo[2477]: pam_unix(sudo:session): session closed for user root
Jan 21 19:23:26 raspberrypi systemd[1]: Started LSB: pimatic service.
Jan 21 19:52:34 raspberrypi systemd[1]: Stopping LSB: pimatic service...
Jan 21 19:52:36 raspberrypi pimatic[19142]: Sending SIGTERM to pimatic(2256), waiting for process exit...
Jan 21 19:52:37 raspberrypi pimatic[19142]: Stopped.
Jan 21 19:52:37 raspberrypi systemd[1]: Stopped LSB: pimatic service.
Hint: Some lines were ellipsized, use -l to show in full.
pi@raspberrypi:~ $ sudo pimatic.js status
Not running.
pi@raspberrypi:~ $ cd virtualhomeduino/
pi@raspberrypi:~/virtualhomeduino $ sudo cp vhduino /home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/bin/vhduino
pi@raspberrypi:~/virtualhomeduino $ cd /home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/bin/
pi@raspberrypi:~/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/bin $ sudo ./vhduino
ready
^C2018-01-21 19:59:43 sigHandler: Unhandled signal 2, terminating
pi@raspberrypi:~/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/bin $ cd
pi@raspberrypi:~ $ sudo service pimatic start
Logfile
pi@raspberrypi:~ $ tail -f /home/pi/pimatic-app/pimatic-daemon.log
19:24:44.723 [pimatic-homeduino] debug: data: "PING"
19:29:45.143 [pimatic-homeduino] debug: data: "PING"
19:34:45.737 [pimatic-homeduino] debug: data: "PING"
19:39:46.095 [pimatic-homeduino] debug: data: "PING"
19:44:46.296 [pimatic-homeduino] debug: data: "PING"
19:49:47.978 [pimatic-homeduino] debug: data: "PING"
19:52:36.494 [pimatic] info: Flushing database to disk, please wait...
19:52:36.635 [pimatic] info: Flushing database to disk, please wait... Done.
19:52:36.639 [pimatic] info: exiting...
20:00:16.885 2018-01-21 Sunday
20:00:28.742 [pimatic] info: Starting pimatic version 0.9.42
20:00:34.945 [pimatic, ppm] info: 2.15.12
20:00:35.066 [pimatic] info: Loading plugin: "pimatic-cron" (0.8.8)
20:00:36.033 [pimatic] info: Loading plugin: "pimatic-mobile-frontend" (0.9.12)
20:00:37.612 [pimatic] info: Loading plugin: "pimatic-gpio" (0.9.0)
20:00:37.780 [pimatic] info: Loading plugin: "pimatic-ping" (0.9.5)
20:00:37.871 [pimatic] info: Loading plugin: "pimatic-shell-execute" (0.9.11)
20:00:37.959 [pimatic] info: Loading plugin: "pimatic-mythermostat" (0.0.3)
20:00:38.068 [pimatic] info: Loading plugin: "pimatic-denon-avr" (0.9.9)
20:00:39.278 [pimatic] info: Loading plugin: "pimatic-iframe" (0.3.1)
20:00:39.353 [pimatic] info: Loading plugin: "pimatic-dht-sensors" (0.9.3)
20:00:39.410 [pimatic] info: Loading plugin: "pimatic-sunrise" (0.8.7)
20:00:39.479 [pimatic] info: Loading plugin: "pimatic-openweather" (0.9.4)
20:00:39.621 [pimatic] info: Loading plugin: "pimatic-sysinfo" (0.9.4)
20:00:39.917 [pimatic] info: Loading plugin: "pimatic-filebrowser" (0.9.0)
20:00:40.212 [pimatic] info: Loading plugin: "pimatic-filter" (0.9.3)
20:00:40.293 [pimatic] info: Loading plugin: "pimatic-samsung-tv" (0.9.0)
20:00:40.364 [pimatic] info: Loading plugin: "pimatic-links" (0.8.6)
20:00:40.414 [pimatic] info: Loading plugin: "pimatic-upnp-root" (0.9.0)
20:00:40.684 [pimatic] info: Loading plugin: "pimatic-wakeonlan" (0.9.4)
20:00:40.768 [pimatic] info: Loading plugin: "pimatic-homeduino" (0.9.11)
20:00:42.166 [pimatic] info: Loading plugin: "pimatic-telegram" (1.1.6)
20:00:43.931 [pimatic] info: Loading plugin: "pimatic-amazing-dash-button" (0.9.14)
20:00:44.051 [pimatic] info: Loading plugin: "pimatic-chronotherm" (0.9.8-10)
20:00:44.121 [pimatic-cron] info: the time is: Sun Jan 21 2018 20:00:44 GMT+0100 (CET)
20:00:44.955 [pimatic-sunrise] info: Your location is set to lat: 48.759145, long: 9.156588
20:00:47.348 [pimatic] info: New device "🌐 Media Switch"...
...
20:01:20.929 [pimatic-mobile-frontend] info: packing static assets
20:01:25.700 [pimatic-mobile-frontend] info: packing static assets finished
20:01:25.720 [pimatic-mobile-frontend] info: rendering html
20:01:30.123 [pimatic-homeduino] debug: data: "ready"
20:01:30.330 [pimatic-homeduino] info: Connected to homeduino device.
20:01:31.138 [pimatic-homeduino] debug: data: "ACK"
20:01:31.157 [pimatic-homeduino] debug: data: "2018-01-21 20:01:30 sigHandler: Unhandled signal 11, terminating"
unknown message received: 2018-01-21 20:01:30 sigHandler: Unhandled signal 11, terminating
20:01:31.168 [pimatic-homeduino] debug: data: ""
unknown message received:
20:01:32.229 [pimatic-homeduino] debug: Receiving on pin 17
[bot.info] bot started
20:01:40.948 [pimatic-mobile-frontend] info: rendering html finished
20:01:41.239 [pimatic] info: Listening for HTTPS-request on port 443...
20:01:41.253 [pimatic] info: Listening for HTTP-request on port 8080...
Hardware
So i didn’t change anything of the wiring setup which is working fine with the old homeduino binary.
Superheterodyne RXB6
While I checked my software setup I realised that there is the wiring pi installation. Might that cause some problems?
pi@raspberrypi:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
pi@raspberrypi:~ $ node -v
v4.6.2
pi@raspberrypi:~ $ npm -v
2.15.11
pi@raspberrypi:~ $ pigpiod -v
60
pi@raspberrypi:~ $ whereis pigpiod
pigpiod: /usr/bin/pigpiod /usr/man/man1/pigpiod.1
pi@raspberrypi:~ $ gpio -v
gpio version: 2.32
Copyright (c) 2012-2015 Gordon Henderson
This is free software with ABSOLUTELY NO WARRANTY.
For details type: gpio -warranty
Unable to determine hardware version. I see: Hardware : BCM2835
,
- expecting BCM2708 or BCM2709.
If this is a genuine Raspberry Pi then please report this
to projects@drogon.net. If this is not a Raspberry Pi then you
are on your own as wiringPi is designed to support the
Raspberry Pi ONLY.
hmm, I’m running out of ideas. Maybe last one:
Do your have a spare SD-Card were you can install latest Raspbian stretch? Repeat your pimatic installation there. Only difference I can see is the version of pigpio on the setups I’ve tested.
$ pigpiod -v
64
I also know that @DaanNL was coding against version 64 of pigpio. Maybe that will do the trick.
@layereight okay thank you so far. Setting up a new system will cost me some time, so this is not an option at the moment. But I will give it a try when I have some time.
Perhaps there is somebody using your binary successfully with raspbian Jessie? @wolf @mwittig @bramboomen @DaanNL @TH1485 @V1per @danieltrapp @Alexander-Lemke @fmmsousa @ArthurDent @christoph-ch @jee67 can you guys do me a favor and check your raspbian version, kernel version and the pigpio version? Just if you’re using the vhduino binary successfully. That will be great!
Thanks a lot!
@fabian said in Help, homeduino not working anymore [Solved]:
@layereight okay thank you so far. Setting up a new system will cost me some time, so this is not an option at the moment. But I will give it a try when I have some time.
Perhaps there is somebody using your binary successfully with raspbian Jessie? @wolf @mwittig @bramboomen @DaanNL @TH1485 @V1per @danieltrapp @Alexander-Lemke @fmmsousa @ArthurDent @christoph-ch @jee67 can you guys do me a favor and check your raspbian version, kernel version and the pigpio version? Just if you’re using the vhduino binary successfully. That will be great!
Thanks a lot!
Sory, I can’t help you I haven’t install vhduino yet.
pi@raspbpizero:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie
pi@raspbpizero:~ $ uname -a
Linux raspbpizero 4.9.35+ #1014 Fri Jun 30 14:34:49 BST 2017 armv6l GNU/Linux
pi@raspbpizero:~ $ node -v
v4.8.4
pi@raspbpizero:~ $ npm -v
2.15.11
pi@raspbpizero:~ $ pigpiod -v
60
pi@raspbpizero:~ $ whereis pigpiod
pigpiod: /usr/bin/pigpiod /usr/man/man1/pigpiod.1
pi@raspbpizero:~ $ gpio -v
gpio version: 2.44
Copyright (c) 2012-2017 Gordon Henderson
This is free software with ABSOLUTELY NO WARRANTY.
For details type: gpio -warranty
Raspberry Pi Details:
Type: Pi Zero-W, Revision: 01, Memory: 512MB, Maker: Sony
* Device tree is enabled.
*--> Raspberry Pi Zero W Rev 1.1
* This Raspberry Pi supports user-level GPIO access.