To make a long story short, can someone please tell me how to configure my KVM system to work with my new CONBEE 2? My old Conbee works without any problems. Thank you very much and best regards!
There shouldn’t be any difference in terms of mounting.
Are you just swapping them out?
Yes, we actually did the same thing as with the Conbee stick.
To throw the stick into the VM we created a usb.xml config:
<hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x1cf1'/> <product id='0x0030'/> </source> </hostdev>
This we created with
virsh attach-device --file usb.xml --config vmname virsh attach-device --file usb.xml --config vmname --config
With the conbee stick this works perfectly.
Only with the conbee II deconz can not establish a connection.
Noticeable is maybe this warning in the dmesg, if you mount the stick:
VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not work properly. Using workaround
- Debian 11 Bullseye
- 5.10.0-8-amd64 kernel
- 7.0.0-3 libvirt-daemon
Guest VM with deconz:
- Debian 11 Bullseye
- 5.10.0-9-amd64 kernel
- Deconz 2.13.03-debian-buster-beta
this is something you probably understand better
I’m not sure why this don’t work but has KVM any more options for configuring USB and how usb devices are bound?
And perhaps you could just try to reset the ConBee2 FW with the command
sudo GCFFlasher_internal -r
One possibility is to add the stick as I described above. Otherwise you can put the /dev/ttyXY device into the VM. Unfortunately this does not work either.
At the moment I think it is something kvm specific. I have an identical server with proxmox. There the Conbee II stick works perfectly.
But right now I am a bit at a loss because I could not find any differences between the configuration, or used drivers between Proxmox and KVM.
Every time the error occurs we have this message in the deconz logs
zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
Do you know anything about this?
Nice, finally I found someone with the same problem
My Conbee 2 was working on a KVM machine on Fedora 33 for a good year. Then I upgraded Fedora to 35, and now I have exactly the same problem. Thus could be related to the KVM version.
Also trying to flash the firmware is failing, seems to be that deconz can’t communicate properly with the stick on the KVM machine.
I already found a possible solution: ConBee II and KVM - Hardware - Home Assistant Community
But not yet tested it. Maybee it works for you as well.
Yeah cool. It’s dumb but I’m still glad that we have the same problem.
About your possible solution:
I have also tried that and did not get it to work. In the VM the device /dev/ttyXY does not exist. Although the Conbee II is visible in the output of lsusb…
Would have liked to report now that it works.
Maybe it makes sense to wait for new firmware for the Conbee II. Seems to be currently not very stable.
Does anyone have an update? I would like to use my Conbee II