Good day, want to try these WALL switches and would appreciate some information.
Do these provide state back to HA? So changes in the switch are seen in HA and vice versa?
And can I set 2 gateways to ensure proper coverage throughout the house?
Hi,
Do you try to generate the key with android or iOS?
Generate key at iOS will not work at this moment. You get a wrong key.
Generate key at Android is the solution for me. I get the right key with lowercase.
Ive had the Xiaomi Gateway working for months without any issues. The day before yesterday friends discconected the GW by accident and it was off for a couple of hours. Now I cant get it to connect with HASS.
setup: hass.io 0.61.1 on a raspberrypi3.
router is an ASUS RT-AC66U
my previous config was
xiaomi_aqara:
gateways:
key: txteldj5wtn8eeb8
Documentation shows that my config is out of date, but it was working. I couldnāt even get the GW to connect with the MI app properly. After hours of trying different config options and resetting the GW/password Iām at a loss. I havenāt updated my router so I doubt its a problem with my router.
(I think it somehow turned out to be a router problem. I ended up factory resetting my router and it seemed to fix it. The main tell for me was the MI Home Gateway app. If you go to general settings then to network info. It should say ālocal connectionā instead of āRemote connection.ā )
This is my first post here. I just bought a Raspberry PI 3 B+ and setup Home Assistant. I had working fine with a PICO PI I had previously. All of the sudden Hass could not find my Xiaomi Gateway, after much troubleshooting I managed to pin point where my issue is. First, this is what I started getting from Hass:
**=====**
**2018-06-20 17:24:48 ERROR (SyncWorker_5) [homeassistant.components.xiaomi_aqara] No gateway discovered**
**2018-06-20 17:24:48 ERROR (MainThread) [homeassistant.setup] Setup failed for xiaomi_aqara: Component failed to initialize.**
**=====**
I noticed that after I started using OpenVPN that my issue started, and I believe it has to do with the static routes OpenVPN sets up when I establish a tunnel with my Cloud Server.
Original route (Hass find the Xiaomi Gateway, all works fine):
**=====**
**root@raspberrypi:~# route -n**
**Kernel IP routing table**
**Destination Gateway Genmask Flags Metric Ref Use Iface**
**0.0.0.0 192.168.1.1 0.0.0.0 UG 202 0 0 eth0**
**192.168.1.0 0.0.0.0 255.255.255.0 U 202 0 0 eth0**
**root@raspberrypi:~# ip route get 224.0.0.50**
**multicast e000:32:800:400:200:0:800:700 dev eth0 src 192.168.1.113**
** cache <mc>**
**=====**
Once I start the VPN I noticed that the multicast address changes the route. Multicast going through the VPN:
**====**
**root@raspberrypi:~# route -n**
**Kernel IP routing table**
**Destination Gateway Genmask Flags Metric Ref Use Iface**
**0.0.0.0 10.8.0.13 128.0.0.0 UG 0 0 0 tun0**
**0.0.0.0 192.168.1.1 0.0.0.0 UG 202 0 0 eth0**
**10.8.0.1 10.8.0.13 255.255.255.255 UGH 0 0 0 tun0**
**10.8.0.13 0.0.0.0 255.255.255.255 UH 0 0 0 tun0**
**128.0.0.0 10.8.0.13 128.0.0.0 UG 0 0 0 tun0**
**162.242.211.145 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0**
**192.168.1.0 0.0.0.0 255.255.255.0 U 202 0 0 eth0**
**root@raspberrypi:~# ip route get 224.0.0.50**
**multicast e000:32:800:400:400:0:800:700 dev tun0 src 10.8.0.14**
** cache <mc>**
**=====**
I tried adding a static route to multicast but no success:
**=====**
**root@raspberrypi:~# ip route get 224.0.0.50**
**224.0.0.50 via 192.168.1.1 dev eth0 src 192.168.1.113**
** cache**
**=====**
Network and route always scared me. Anyone has any ideas to get around that? I need OpenVPN working otherwise I can access my Raspbian from outside.
I also have a livebox. The gateway is discovered and listed on the home page but I canāt interact with it. (switch light on/off)
Iām just getting {āerrorā:āInvalid keyā} when I try to switch the light on.