So I cleared my home-assistant.log file and hit clear under the “i” log display on the UI. Then did a restart of HASS. Nothing showed up in the logs. No entries at all. Everything else works, and the Xiaomi sensors show up at the top, but when I trigger a door sensor or motion sensor (or any other sensor) nothing is updated. However my Hassbian instance is running on my Pi in parallel right now and gets the updates no problem.
If there is nothing showing at all in your log you have bigger problems.
Actually we would prefer the full log posted to hastebin or similar.
So I restarted/reset the VirtualBox Hass.io VM and let it start up. My Hue showed up, my Xiaomi sensors, broadlink switches, etc, etc. I went to the “i” and hit refresh and went to home-assistant.log via configurator and hit refresh. The only thing in the logs was this:
2019-01-06 00:23:16 WARNING (Recorder) [homeassistant.components.recorder] Ended unfinished session (id=51 from 2019-01-06 07:16:31.490527)
Should I try removing all components except the xiaomi gateway to try and isolate whether something else is causing it?
Could this be a firewall type issue (with it being in the VM)? Maybe the host machine isn’t letting the incoming sensor data come through the firewall?
BTW, Thanks for taking the time to try and help! I really appreciate it.
I just found this: Xiaomi integration and multicast problem
He mentions running HA in a Virtualbox and that his sensors show up but don’t work. Anyone else have a solution to this problem? It seems that he thought that VirtualBox was blocking the multicast messages.
I didn’t post logs because like grifter7 there doesn’t seem to be any related activity in the logs (both hass and - in my case - the zigbee2mqtt logs). Sorry for not mentioning that. I’ve cleaned up my configuration.yaml because there were some other unrelated errors (asus device tracker, telegram notify stuff) so you can have a better look at my logs. I hope you see something that we are missing.
zigbee2mqtt log (note that I rebooted hass.io and then rebooted my broker): https://hastebin.com/ewosujizik.makefile
Mosquitto broker log: https://hastebin.com/iyefahewiy.sql
Hass log: https://hastebin.com/qulabirisa.coffeescript
at the moment I’ve synced 2 binary sensors (xiaomi aqara) that don’t update. The Tradfri lamps work without any problems. There’s no other zigbee devices connected.
I’m using virtualbox without any issue, however I did not use the vmdk. Might be worth the effort of installing it manually.
Oh ok. Maybe I can try that. Are you able to provide and simple steps to do that? Did you just follow the “Generic linux server” install instructions on this page: https://www.home-assistant.io/hassio/installation/ ?
I actually do not use HASSio but HA in docker;
I also came across this: https://community.openhab.org/t/xiaomi-mi-gateway-no-sensor-updates-muticast-issue/37256
And this: https://community.openhab.org/t/xiaomi-problem-with-sensors/31390/11
Both of which sound very much like what I’m experiencing.
Yes, it seems like a network/multicast issue but in HASSio you do not have any control of that so I’m not using it. As you do not experience any issues with your other setup I do not expect it to be a problem related to your router
I’d like to troubleshoot this further with my limited knwledge by downgrading. Now downgrading hass.io is not difficult for me (install older version on my rpi, boot et voila). However I don’t know how to install an older version of the add-on zigbee2mqtt. Can’t find information on the forums on that. Only suggestions I can find is to use snapshots but I dont have those. atm I only backup my configuration.yaml
So: how do I install an older version of an add-on?
Please stop hacking this thread, this isn’t about zigbee2mqtt.
Hi!
Did you have any luck?
I’m also trying to migrate from RPi3 to VBox on Win10. Using HASSio.
Runing Wireshark on another computer I can see the Xiaomi responding with multicast to the 10 disocevery messages and that is all I get from it.
I got the same issue, got hassio on a VM, the Xiaomi sensors are show but not updating
I never did figure this problem out 
I would love if someone smarter than me could figure it out, I’d love to run HA in a VM. My suspicion is that the problem lies somewhere with how VirtualBox manages multicast to the guest machine. I think I’ve seen people in the virtualbox forums complain about multicast issues.
Anyone have any ideas?
Having the same problem, in my case I’m using Synology virtual machine manager which is based on qemu
I’ve been updating this thread with my findings, add your comments if you want to help fix the issue! https://github.com/home-assistant/home-assistant/issues/21250
same issue here. Did a test copy of my Hassio instance to Oracle VM running Ubuntu on win 10. Xiaomi sensors etc all found on discovery and then that’s it. No updates, no log entries.
Pi Hassio instance working fine still.
Certainly a multicast issue with VM.