Homeduino - timeout

---

I installed a Arduino nano with the recommended 433MHz receiver and transmitter.
At first it worked fine. I have traced my *brennenstuhl * sockets and configured them as switches (Switch 3).
They where switchable at the beginning and I was happy.

After a peroid of time they can’t be switched anymore. when switching, the GUI shows Oops timeout after a few seconds.
I think the homeduino is working fine I still can receive the commands sent from the remote and there are no errors in the log.
Only sending seems to be broken. I already changed the transmitter but still the same behavior.

I reinstalled the plugin and uploaded the files to the arduino a second time. But this did not help.

anything I can do to get closer to the issue?!

@benbeton hmm this is interesting.
First, a timeout in pimatic-Homeduino as nothing to do with the transmitter.
Are you sure you have no error messages? Without it can be very hard to find your failure.

@benbeton are you using a raspberry pi? if so could you post the result of the command

dmesg -T

few minutes after the problem occur.
I suspect a power failure from time to time

yes there are no errors.
I’ll test with dmesg -T

in the next days I will migrate from RPi1 to RPi2 and I will install all from scratch. Until then I leave it and will do some testing.
Maybe it is working with the new one. I’ll keep you informed.

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.

this is what I can see while running dmesg -T

Transfer to device 5 endpoint 0x1 frame 22 failed - FIQ reported NYET. Data may have been lost.
[Mon Feb 29 17:51:07 2016] Transfer to device 4 endpoint 0x1 frame 1398 failed - FIQ reported NYET. Data may have been lost.
[Mon Feb 29 17:52:06 2016] Transfer to device 5 endpoint 0x1 frame 1270 failed - FIQ reported NYET. Data may have been lost.
[Mon Feb 29 17:52:25 2016] Transfer to device 4 endpoint 0x1 frame 398 failed - FIQ reported NYET. Data may have been lost.
[Mon Feb 29 17:53:25 2016] Transfer to device 4 endpoint 0x1 frame 230 failed - FIQ reported NYET. Data may have been lost.
[Mon Feb 29 17:53:25 2016] Transfer to device 4 endpoint 0x1 frame 270 failed - FIQ reported NYET. Data may have been lost.
[Mon Feb 29 17:59:40 2016] Transfer to device 4 endpoint 0x1 frame 358 failed - FIQ reported NYET. Data may have been lost.
[Mon Feb 29 18:06:13 2016] Transfer to device 4 endpoint 0x1 frame 502 failed - FIQ reported NYET. Data may have been lost.
[Mon Feb 29 18:06:33 2016] Transfer to device 5 endpoint 0x1 frame 1758 failed - FIQ reported NYET. Data may have been lost.
[Mon Feb 29 18:06:33 2016] Transfer to device 5 endpoint 0x1 frame 1878 failed - FIQ reported NYET. Data may have been lost.
[Mon Feb 29 18:07:32 2016] Transfer to device 4 endpoint 0x1 frame 1350 failed - FIQ reported NYET. Data may have been lost

Don’t know if that is related the the issue seems to be the Bluetooth Stick, will try without them

lsusb -t
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/3p, 480M
        |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M
        |__ Port 2: Dev 4, If 0, Class=Vendor Specific Class, Driver=ch341, 12M
        |__ Port 3: Dev 5, If 0, Class=Wireless, Driver=btusb, 12M
        |__ Port 3: Dev 5, If 1, Class=Wireless, Driver=btusb, 12M```

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.

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/11

The 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.

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

@t1m0

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 /TTyUSB1

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:~ $ 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 adapter

I 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 the

udevadm 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