Hi @bramboomen,
glad it works for you.
-
Help, homeduino not working anymore [Solved]
-
you will have to stop pimatic before you run
sudo ./vhduinoin the virtualhomeduino directory. It’s because there is another instance ofvhduinorunning 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 readypi@raspberrypi:~/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/bin $ sudo ./vhduino readyperhaps 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
vhduinobinary from~/virtualhomeduinoto~/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 startLogfile
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 RXB6While 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 64I 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. -
Hey @SaxnPaule ,
as also already stated earlier in this thread, downgrading the kernel can only be a temporary fix. It won’t help in the long-run. Good news is that with @DaanNL’s great work we already have a fix.
We are currently waiting for the project’s maintainers to merge back the changes into the original project. Unfortunately, there was no feedback from the maintainers yet. But once the changes get approved the whole pimatic community will benefit from the fix.
Also see:
In the meantime you could test the fixed version of the virtualhomeduino as described in https://github.com/layereight/virtualhomeduino#testing and give us feedback whether it works for you.
-
Hallo zusammen,
habe soeben mein pi3 auf den neuen Kernel (4.9.35-v7+) aktualisiert und habe den Fix von https://github.com/layereight/virtualhomeduino angewendet.
Das Schalten von Funksteckdosen funktioniert auch mit dem neuen Kernel perfekt.
Allerdings funktioniert der Receiver nicht, in den Nachrichten unter “debug” wird hier nichts angezeigt (wenn ich z.B. mit einer 433 Fernbedienung schalte). Habt ihr noch einen Idee?
Den Receiver PIN habe ich dementsprechend geändert.Danke schon mal im Voraus.
Schöne Grüße
Chris -
@christoph-ch
Das Problem hat sich nach dem zweiten Neustart automatisch gelöst. -
@christoph-ch
Das heißt, bei dir werden empfangene Signal per Debug ausgegeben? Das funktioniert bei mir nämlich auch nicht. -
@christoph-ch and @carlptr,
I also made the observation that some receivers are just bad quality. Also see https://forum.pimatic.org/topic/487/hardware-tip-433-mhz-receiver-for-pimatic. In some cases distance between receiver and remote matters a lot.
I’ve got some pieces of the XY-MK-5V receiver and it is pretty bad. I need to come real close with the remote to see some debug output. I’m talking about centimeters here.
-
Hey there, i have the same problem and dont know how to solve it. My RPI2 freezes and the homeduino plugin doesnt work. I made a new install with Stretch and since this din’t work for me i tried an older Jessie Version but its the same problem. Here is my last log on Stretch after update, upgrade and installed the fix as described. I don’t want to make a new install of pimatic again since this is the 4th time.
pi@raspberrypi:~ $ pigpiod -v 64 pi@raspberrypi:~ $ lsb_release -a No LSB modules are available. Distributor ID: Raspbian Description: Raspbian GNU/Linux 9.3 (stretch) Release: 9.3 Codename: stretch pi@raspberrypi:~ $ node -v v4.8.3 pi@raspberrypi:~ $ npm -v 2.15.11 pi@raspberrypi:~ $ tail -f /home/pi/pimatic-app/pimatic-daemon.log 08:27:51.428 [pimatic-mobile-frontend] info: packing static assets 08:27:53.798 [pimatic-mobile-frontend] info: packing static assets finished 08:27:53.815 [pimatic-mobile-frontend] info: rendering html 08:27:58.801 [pimatic-maxcul] debug: incoming raw data from CUL: V 1.66 CUL868 08:27:58.808 [pimatic-maxcul] info: CUL FW Version: V 1.66 CUL868 08:28:10.255 [pimatic-mobile-frontend] info: rendering html finished 08:28:10.447 [pimatic] info: Listening for HTTP-request on port 5001... 08:28:10.468 [pimatic-maxcul] debug: enable MAX! Mode of the CUL868 08:30:02.940 [pimatic-homeduino] debug: Sending Protocol: switch4 unit:18 id:8 state:true all:false Pin:18 Repeats:20 08:30:03.853 [pimatic-homeduino] debug: data: "ACK" 08:30:49.905 [pimatic] info: Restarting... 08:30:49.923 [pimatic] info: Flushing database to disk, please wait... 08:30:50.083 [pimatic] info: Flushing database to disk, please wait... Done. 08:30:51.737 [pimatic] info: exiting... 08:30:54.171 2018-02-20 Tuesday 08:31:03.464 [pimatic] info: Starting pimatic version 0.9.42 08:31:07.755 [pimatic, ppm] info: 2.15.12 08:31:07.838 [pimatic] info: Loading plugin: "pimatic-cron" (0.8.8) 08:31:08.617 [pimatic] info: Loading plugin: "pimatic-mobile-frontend" (0.9.12) 08:31:09.879 [pimatic] info: Loading plugin: "pimatic-bh1750" (0.2.0) 08:31:09.966 [pimatic] info: Loading plugin: "pimatic-gpio" (0.9.0) 08:31:10.118 [pimatic] info: Loading plugin: "pimatic-homeduino" (0.9.11) 08:31:11.164 [pimatic] info: Loading plugin: "pimatic-maxcul" (1.0.3) 08:31:11.534 [pimatic] info: Loading plugin: "pimatic-netcheck" (1.1.0) 08:31:11.808 [pimatic] info: Loading plugin: "pimatic-openweather" (0.9.4) 08:31:11.916 [pimatic] info: Loading plugin: "pimatic-pushover" (0.9.4) 08:31:11.989 [pimatic] info: Loading plugin: "pimatic-shell-execute" (0.9.11) 08:31:12.055 [pimatic] info: Loading plugin: "pimatic-sunrise" (0.8.7) 08:31:12.119 [pimatic] info: Loading plugin: "pimatic-sysinfo" (0.9.4) 08:31:12.425 [pimatic] info: Loading plugin: "pimatic-wakeonlan" (0.9.4) 08:31:12.487 [pimatic-cron] info: the time is: Tue Feb 20 2018 08:31:12 GMT+0100 (CET) 08:31:13.182 [pimatic-maxcul] info: using serial device /dev/ttyACM0@38400 08:31:13.548 [pimatic-sunrise] info: Your location is set to lat: 51.339695, long: 12.373075 08:31:13.800 [pimatic-maxcul] info: serialPort /dev/ttyACM0 is open! 08:31:13.993 [pimatic] info: New device "Lampe Wohnzimmer Sofa"... 08:31:14.060 [pimatic] info: New device "TV"... 08:31:14.109 [pimatic] info: New device "Staubsauger"... 08:31:14.147 [pimatic] info: New device "Deckenlampe Wohnzimmer"... 08:31:14.182 [pimatic] info: New device "Deckenlampe Flur"... 08:31:14.223 [pimatic] info: New device "Deckenlampe Bad"... 08:31:14.265 [pimatic] info: New device "Deckenlampe Schlafzimmer"... 08:31:14.298 [pimatic] info: New device "Deckenlampe Alles"... 08:31:14.385 [pimatic] info: New device "System"... 08:31:14.550 [pimatic] info: New device "Aktuelles Wetter"... 08:31:14.655 [pimatic] info: New device "Heutige Vorhersage"... 08:31:14.715 [pimatic] info: New device "Alles"... 08:31:14.759 [pimatic] info: New device "PC"... 08:31:14.783 [pimatic] info: New device "Raspberry Pi"... 08:31:14.852 [pimatic] info: New device "PCWOL"... 08:31:14.918 [pimatic] info: New device "Sunrise & Sunset"... 08:31:15.510 [pimatic] info: New device "Lichtsensor"... 08:31:15.531 [pimatic] warn: No plugin found for device "dash-button-alles-aus" of class "AmazingDashButton"! 08:31:15.566 [pimatic] info: New device "Auto Sunset"... 08:31:15.614 [pimatic] info: New device "Pimatic"... 08:31:15.672 [pimatic] info: New device "Heizung Wohnzimmer Links"... 08:31:15.722 [pimatic] info: New device "Heizung Wohnzimmer Rechts"... 08:31:15.782 [pimatic] info: New device "Heizung Bad"... 08:31:15.860 [pimatic] info: New device "Heizung Schlafzimmer"... 08:31:15.901 [pimatic] warn: No plugin found for device "dash-button-alles-aus-2" of class "AmazingDashButton"! 08:31:15.956 [pimatic] info: New device "Sleeptimer"... 08:31:15.999 [pimatic] info: New device "Smartphone"... 08:31:16.042 [pimatic] info: New device "PC"... 08:31:16.069 [pimatic] info: New device "Chromecast"... 08:31:16.096 [pimatic] info: New device "Fritzbox"... 08:31:16.123 [pimatic] info: New device "FireTV Stick"... 08:31:19.474 [pimatic] error: Could not force add rule, because error has no rule attribute. 08:31:19.608 [pimatic] error: Could not parse rule "pc-off is pressed then execute "curl –silent –output http://svri4hjkv5brxycj.myfritz.net:7760/suspend"": The rule must start with "when" and contain a "then" part! 08:31:19.612 [pimatic] error: Could not parse rule "when dash-button-alles-aus is closed or when dash-button-alles-aus-2 is closed then press all-off": Could not find an provider that decides next predicate of "dash-button-alles-aus is closed or when dash-button-alles-aus-2 is closed". 08:31:19.721 [pimatic-maxcul] debug: templates loaded 08:31:19.859 [pimatic-maxcul] debug: check CUL Firmware version 08:31:19.883 [pimatic-maxcul] debug: Requested CUL Version... 08:31:19.883 [pimatic-maxcul] debug:> 08:31:19.899 [pimatic-homeduino] debug: data: "hardware not supported" unknown message received: hardware not supported 08:31:19.904 [pimatic-homeduino] debug: data: "garbage collected wiringX library" unknown message received: garbage collected wiringX library 08:31:19.907 [pimatic-homeduino] debug: data: "ready" 08:31:19.940 [pimatic-homeduino] info: Connected to homeduino device. 08:31:19.980 [pimatic-homeduino] debug: data: "ACK" 08:31:20.377 [pimatic-homeduino] debug: Receiving on pin 17 08:31:20.683 [pimatic-mobile-frontend] info: packing static assets 08:31:22.890 [pimatic-mobile-frontend] info: packing static assets finished 08:31:22.905 [pimatic-mobile-frontend] info: rendering html 08:31:26.977 [pimatic-maxcul] debug: incoming raw data from CUL: V 1.66 CUL868 08:31:26.984 [pimatic-maxcul] info: CUL FW Version: V 1.66 CUL868 -
Sorry @S7EN,
but your logs tell me that you do not have the fix in place:
08:31:19.899 [pimatic-homeduino] debug: data: "hardware not supported" unknown message received: hardware not supported 08:31:19.904 [pimatic-homeduino] debug: data: "garbage collected wiringX library" unknown message received: garbage collected wiringX libraryIt clearly shows that you are still using the old
vhduinobinary. Maybe you missed something during your setup.Do it like so: https://github.com/layereight/virtualhomeduino#testing
-
Hey, i made the steps again and everything works fine yet. Thank you
-
Hey @S7EN,
happy to hear that.
-
Is there something special todo for the rasberry pi3?
pimatic:
{ "plugin": "gpio", "debug": true, "active": true }, { "plugin": "homeduino", "driver": "gpio", "driverOptions": {}, "receiverPin": 1, "transmitterPin": 0, "debug": true, "active": true }pilight (working)
"settings": { "log-level": 0, "pid-file": "/var/run/pilight.pid", "log-file": "/var/log/pilight.log", "webserver-enable": 1, "webserver-root": "/usr/local/share/pilight/webgui", "webserver-http-port": 5001, "webserver-cache": 1, "**gpio-platform**": "raspberrypi3" }, "hardware": { "433gpio": { "sender": 0, "receiver": 1 } }I cant send or receive any 433mhz signal
