Dash button problem

Johan_Thomas · January 29, 2017, 8:27pm

Hi !
I have a strange behaviour with my dash button. I have to explain that my openhab2 is on a wired laptop and i have also a WLAN network connected (for dash button to work). My WLAN network is working only between 6-00 to 23-00 because i dont want to have wifi everytime and in the night.
My dash buttons are working fine but only one day … I suspect that when the WLAN disappear at 23-00 the binding is not automatically refreshed at 6-00 when the WLAN comes back.
So i have to restart OH2 for my dash button to refunction…

It’s not really great… is there a solution ? is it possible to have a rule for restarting only the dash binding ?
Thanks a lot !!

patrickse · January 29, 2017, 8:36pm

I guess your wifi is provided by a router? Or do you use your laptop as access point?

Johan_Thomas · January 29, 2017, 8:49pm

yep its provided by a router. And i have a schedule on it to only active Wifi between 6-00 to 23-00 (CRON)

patrickse · January 29, 2017, 9:10pm

As far as I understand the binding, it just acts like a network sniffer looking for a spicific package to show up on your network. It will take a look at the source of the package and determine its MAC address to identify the button.

So it does not really connect to any wifi network or dash button. So it should not need to do any refresh to work again.

I would guess your problem is not related to your disappearing wifi network.

Have you tried to enable debugging on the binding to get an idea what is failing.

(I will try to reproduce your problem later that evening)

Johan_Thomas · January 29, 2017, 9:12pm

No i didnt try debug. Can you tell me how to enable it ?

patrickse · January 29, 2017, 9:20pm

I always use the karaf console to enable debugging.

Go to your openhab Server and connect with ssh to port 8101 authenticated as user openhab with password habopen. ‘ssh -l openhab localhost -p 8101’
run command ‘log:set debug org.openhab.binding.amazondashbutton’
run command ‘log:tail’ and press one of your dash buttons.
to disable debugging use the following command ‘log:set info org.openhab.binding.amazondashbutton’

Hope it will help…

Forgot to mention. Openhabs ssh Server is listening just on the loopback device by default.

Johan_Thomas · February 1, 2017, 6:30pm

Hi
sorry for the delay…
I have just check with DEBUG mode and it is fill up with :

2017-02-01 19:25:25.867 [DEBUG] [nal.pcap.PcapNetworkInterfaceService] - any is not a suitable network interfaces as no addresses are bound to it.
2017-02-01 19:25:25.868 [DEBUG] [nal.pcap.PcapNetworkInterfaceService] - bluetooth0 is not a suitable network interfaces as no addresses are bound to it.
2017-02-01 19:25:25.868 [DEBUG] [nal.pcap.PcapNetworkInterfaceService] - nflog is not a suitable network interfaces as no addresses are bound to it.
2017-02-01 19:25:25.868 [DEBUG] [nal.pcap.PcapNetworkInterfaceService] - nfqueue is not a suitable network interfaces as no addresses are bound to it.
2017-02-01 19:25:25.868 [DEBUG] [nal.pcap.PcapNetworkInterfaceService] - usbmon1 is not a suitable network interfaces as no addresses are bound to it.
2017-02-01 19:25:25.868 [DEBUG] [nal.pcap.PcapNetworkInterfaceService] - usbmon2 is not a suitable network interfaces as no addresses are bound to it.
2017-02-01 19:25:25.868 [DEBUG] [nal.pcap.PcapNetworkInterfaceService] - usbmon3 is not a suitable network interfaces as no addresses are bound to it.
2017-02-01 19:25:25.868 [DEBUG] [nal.pcap.PcapNetworkInterfaceService] - usbmon4 is not a suitable network interfaces as no addresses are bound to it.
2017-02-01 19:25:27.053 [DEBUG] [nal.pcap.PcapNetworkInterfaceService] - any is not a suitable network interfaces as no addresses are bound to it.
2017-02-01 19:25:27.054 [DEBUG] [nal.pcap.PcapNetworkInterfaceService] - bluetooth0 is not a suitable network interfaces as no addresses are bound to it.
2017-02-01 19:25:27.054 [DEBUG] [nal.pcap.PcapNetworkInterfaceService] - nflog is not a suitable network interfaces as no addresses are bound to it.
2017-02-01 19:25:27.054 [DEBUG] [nal.pcap.PcapNetworkInterfaceService] - nfqueue is not a suitable network interfaces as no addresses are bound to it.
2017-02-01 19:25:27.055 [DEBUG] [nal.pcap.PcapNetworkInterfaceService] - usbmon1 is not a suitable network interfaces as no addresses are bound to it.
2017-02-01 19:25:27.055 [DEBUG] [nal.pcap.PcapNetworkInterfaceService] - usbmon2 is not a suitable network interfaces as no addresses are bound to it.

How can i fix it ? it doesn’t find the WLAN0 interface (but it’s really here). I have to restart the binding in order to make it work. It happens everytime my wifi is disconnected
Thanks !

Johan_Thomas · February 4, 2017, 8:00am

Is it possible to have a CRON rule to restart the binding ?

patrickse · February 4, 2017, 6:24pm

Maybe using ssh with key authentication. I’ve read something about it here in the forum. You could then fire the start / stop binding with ssh.

Johan_Thomas · February 7, 2017, 8:51pm

I will try but it seems complicated to find information for this…

do you tried to reproduce my error with Dash buttons ? Maybe i can submit a bug somewhere ?

higgers · February 15, 2017, 8:32pm

I have the same error:

2017-02-15 20:29:53.245 [capNetworkInterfaceService] - nfqueue is not a suitable network interfaces as no addresses are bound to it.
2017-02-15 20:29:53.245 [capNetworkInterfaceService] - usbmon1 is not a suitable network interfaces as no addresses are bound to it.
2017-02-15 20:29:53.245 [capNetworkInterfaceService] - usbmon2 is not a suitable network interfaces as no addresses are bound to it.
2017-02-15 20:29:55.245 [capNetworkInterfaceService] - any is not a suitable network interfaces as no addresses are bound to it.
2017-02-15 20:29:55.245 [capNetworkInterfaceService] - nflog is not a suitable network interfaces as no addresses are bound to it.
2017-02-15 20:29:55.245 [capNetworkInterfaceService] - nfqueue is not a suitable network interfaces as no addresses are bound to it.
2017-02-15 20:29:55.245 [capNetworkInterfaceService] - usbmon1 is not a suitable network interfaces as no addresses are bound to it.
2017-02-15 20:29:55.245 [capNetworkInterfaceService] - usbmon2 is not a suitable network interfaces as no addresses are bound to it.
2017-02-15 20:29:57.245 [capNetworkInterfaceService] - any is not a suitable network interfaces as no addresses are bound to it.
2017-02-15 20:29:57.245 [capNetworkInterfaceService] - nflog is not a suitable network interfaces as no addresses are bound to it.
2017-02-15 20:29:57.245 [capNetworkInterfaceService] - nfqueue is not a suitable network interfaces as no addresses are bound to it.
2017-02-15 20:29:57.245 [capNetworkInterfaceService] - usbmon1 is not a suitable network interfaces as no addresses are bound to it.
2017-02-15 20:29:57.245 [capNetworkInterfaceService] - usbmon2 is not a suitable network interfaces as no addresses are bound to it.
2017-02-15 20:29:59.245 [capNetworkInterfaceService] - any is not a suitable network interfaces as no addresses are bound to it.
2017-02-15 20:29:59.245 [capNetworkInterfaceService] - nflog is not a suitable network interfaces as no addresses are bound to it.
2017-02-15 20:29:59.245 [capNetworkInterfaceService] - nfqueue is not a suitable network interfaces as no addresses are bound to it.
2017-02-15 20:29:59.245 [capNetworkInterfaceService] - usbmon1 is not a suitable network interfaces as no addresses are bound to it.
2017-02-15 20:29:59.245 [capNetworkInterfaceService] - usbmon2 is not a suitable network interfaces as no addresses are bound to it.

My OH2 server is running on Ubuntu 16.10 in a VM on ESXi if that is relevant.

Johan_Thomas · March 5, 2017, 7:41pm

Hi,
if someone can give me an example of how to restart the binding with a rule.
It’s unusable for me, every day if i want my dash button i have to restart OH2…
Thanks in advance