I used to have the same. After a few days running, my homeduino just stopped responding with the “Oops” message. I circumvented it by automatically restarting Pimatic every week. I know, that has solved exactly nothing so I will keep an eye on this thread.
-
Homeduino - timeout
-
l had also problems with homeduino and some nanos. I switch to a uno, and now the device is perfect.
-
glad I’m not alone here @DavidZH did you see any errors in the log?
Today I will switch my pimatic installation form RPi1 to RPi2, what kind of Pi’s are you using?
Maybe @Icesory can help to troubleshoot this!? I found a closed issue that describes the issue https://github.com/pimatic/pimatic-homeduino/issues/11The messages postet above are gone when the BT dongle is not plugged in but the timeout errror is still there,
A short time (maybe 2 min) after restarting pimatic, the switches are “switchable” but nothing happens on the sockets. -
Is your Homeduino plugin and the Homeduino Skript up to date?
I think it can be the same error as in the past.
You can try to deactivate all rules which sends commands to Homeduino and look if it is working now.pimatic rocks!!!
-
homeduino is up to date. Yesterday I set pimatic up from scratch cause I migrated from Pi1 to Pi2.
After this, it did not work. But I found a solution. (the solution has noting to do with upgrading from Pi1 to Pi2)My brennenstuhl sockets should be configured as switch3, described here: https://github.com/pimatic/rfcontroljs/blob/master/protocols.md
So I configured them as switch3 and “houseCode …” during the first test after the first config (this was days ago on Pi1), they worked fine and after this, I never get them to work again. With rules enabled, I get these timeout messages.
After disabling the rules, the timeout was gone but they still won’t switch.So I thought, ok lets try “switch4” with *“Id and code” and after this they are switching and rules are working fine.
Is this a bug in homeduino or just a error in the protocols document?
-
@sweebee said in Homeduino - timeout:
I had the same when I installed hue-zll. Timed out after switching a switch or setting a dimmer. After a reboot everything worked fine again. Then it occurred again after 5 hours. Last week I rebooted again and everything works fine till now.
Same problem till 2 weeks. Homeduino always "Oops…
timeout"
Then i make a restart and it wokrs for some hours. No error message or something else -
why homeduino shows no error on when it can not send
-
Sometimes the Raspberry changed the USB-Port itselv have you looked if the port is now the same as in the config?
By me the port has changed from /TTyUSB0 to /TTyUSB1 -
hmm but if i make a restart only with pimatic the system works fine again…
I’ll check if it does not work again
-
@V1per said in Homeduino - timeout:
Sometimes the Raspberry changed the USB-Port itselv have you looked if the port is now the same as in the config?
By me the port has changed from /TTyUSB0 to /TTyUSB1pi@raspberrypi:~ $ lsusb
Bus 001 Device 005: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Bus 001 Device 006: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@raspberrypi:~ $ lsusb
Bus 001 Device 005: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Bus 001 Device 006: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@raspberrypi:~ $same ports! and timeout again! i go insane!!!
-
@t1m0 said in Homeduino - timeout:
Bus 001 Device 005: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Bus 001 Device 006: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapterI think this two devices are cheap China Arduinos they have the same Chipset and also the same serial-no. I have the same problem… so the Raspberry don’t know who is USB0 and who is USB1 and at every reboot the USB-Port changed…
I haven’t solved the problem jet. I have ordered some Arduinos from an other seller and hope this solved this. -
You can also use the dev/serial/by-path/ addressing to identify your USB device, then you can use devices with the same serial nr.
also see https://forum.pimatic.org/topic/42/tip-homeduino-usb
and https://forum.pimatic.org/topic/1005/ttyusb0-ttyusb1-homeduino-and-my-sensors -
You mean this?
I have tryed it with persistent names but I have not found a way how Linux can differ the arduinos.
I will try it now with theudevadm info -a -n /dev/ttyUSB1 | grep '{devpath}' | head -n1
command and an UDEV rule.
-
no, instead of ttyUSB1 use /dev/serial/by-path/…
you should lookup what is on the dots on your local system -
OK, now I understand /dev/serial/by-path/ is under Linux the path to the USB port I have connect the Arduino. That have to work!
Thank you for the hint!!!
-
@rikki78 said in Homeduino - timeout:
no, instead of ttyUSB1 use /dev/serial/by-path/…
you should lookup what is on the dots on your local systemThat works perfekt!!! My path is for example:
/dev/serial/by-path/platform-3f980000.usb-usb-0:1.5:1.0-port0
-
we’ve also pinned this here :
https://forum.pimatic.org/topic/42/tip-homeduino-usbmaybe useful for other users who are having similar trouble for the future …
pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
@V1per said in Homeduino - timeout:
@t1m0 said in Homeduino - timeout:
Bus 001 Device 005: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Bus 001 Device 006: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapterI think this two devices are cheap China Arduinos they have the same Chipset and also the same serial-no. I have the same problem… so the Raspberry don’t know who is USB0 and who is USB1 and at every reboot the USB-Port changed…
I haven’t solved the problem jet. I have ordered some Arduinos from an other seller and hope this solved this.i know. so ich reboot the system with only one usb insered and put the second after the reboot the slot. i changed the config that now mysensor is usb 0 and homeduino to usb1. until now everything works
-
same problem!! At least every 2 days homeduino times out!!!
Is it posible to activate a rule: Homeduino times out -> restart pimatic???
the “times out” is nowhere where logs?!?!?!
What can i do… it realdy sucks -
@t1m0 May be your system runs out of file descriptors temporarilly?! Did you you check the syslog for any suspects?
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law