fgy41 Posted June 17, 2022 Share Posted June 17, 2022 5 hours ago, SimonF said: Do you still pass thru the usb device or just the serial entry. I uncheck the Conbee (Dresden Elektronik ZigBee gateway) from "USB devices" in the VM Edit menu and just pass through the serial entry. 1 Quote Link to comment
autumnwalker Posted July 11, 2022 Share Posted July 11, 2022 The workaround in the HA community worked for me too. Do we have any idea why this is required with Unraid? It was no issue for me to pass the same stick through with Proxmox previously. Quote Link to comment
stefan.tomko Posted July 11, 2022 Share Posted July 11, 2022 I am having the same issue with 6.10.3. Everything works OK on 6.9.2 I am using plugin "USB devices" and somehow I feel like editing the VM code, while it may fix things, is a workaround only. Is there some action being taken from developers to try to fix this? 2 Quote Link to comment
mpeterson Posted August 1, 2022 Share Posted August 1, 2022 I too share the pain of this and I agree that this is just a workaround. It would be nice to know the stance of the devs about this. Quote Link to comment
gergtreble Posted August 4, 2022 Share Posted August 4, 2022 This has affected me too. Upgraded to 6.10 and all my lights stopped working! Currently downgrading. Following topic in eager anticipation of a fix. Quote Link to comment
Todilo Posted August 17, 2022 Share Posted August 17, 2022 Can anyone shed some light on how to setupd the xml entry. Under unraid usb devices I have this: Bus 005 Device 002 Port 5-2ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II] So what numbers need to be where in the xaml entry? This is my current entry: <serial type='dev'> <source path='/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2132783-if00'/> <target type='usb-serial' port='5'> <model name='usb-serial'/> </target> <alias name='serial1'/> <address type='usb' bus='0' port='5'/> </serial> I can see the device in home assistant but it fails to connect so I guess some value is wrong Quote Link to comment
SimonF Posted August 17, 2022 Share Posted August 17, 2022 26 minutes ago, Todilo said: Can anyone shed some light on how to setupd the xml entry. Under unraid usb devices I have this: Bus 005 Device 002 Port 5-2ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II] So what numbers need to be where in the xaml entry? This is my current entry: <serial type='dev'> <source path='/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2132783-if00'/> <target type='usb-serial' port='5'> <model name='usb-serial'/> </target> <alias name='serial1'/> <address type='usb' bus='0' port='5'/> </serial> I can see the device in home assistant but it fails to connect so I guess some value is wrong Have you removed the device mapping in the VM template? also name will be different in HA. https://community.home-assistant.io/t/solved-conbee-2-fails-to-connect-to-zha-ha-in-unraid-vm/431276/2 Quote Link to comment
Todilo Posted August 17, 2022 Share Posted August 17, 2022 (edited) 1 hour ago, SimonF said: Have you removed the device mapping in the VM template? also name will be different in HA. https://community.home-assistant.io/t/solved-conbee-2-fails-to-connect-to-zha-ha-in-unraid-vm/431276/2 Is this the device mapping you are referring to? I have tried both ways but doesn't seem to help. I can actually see the device in HA like this, now with a very weird name: Edit: With this new setup it actually seem to work. I just have to reboot my entire system to see if the names stick. I now use: /dev/serial/by-id/usb-QEMU_QEMU_USB_SERIAL_1-0000:00:07.7-4-if00-port0 which seems, odd Edited August 17, 2022 by Todilo Quote Link to comment
SimonF Posted August 17, 2022 Share Posted August 17, 2022 3 minutes ago, Todilo said: Is this the device mapping you are referring to? I have tried both ways but doesn't seem to help. I can actually see the device in HA like this, now with a very weird name: Yes that was the mapping, needs to be left unticked. That name is correct and I use the by-id name in HA config. Quote Link to comment
Todilo Posted August 17, 2022 Share Posted August 17, 2022 2 minutes ago, SimonF said: Yes that was the mapping, needs to be left unticked. That name is correct and I use the by-id name in HA config. Thank you. It seems to be working now. Is there a way to actually see the mapped name in Unraid. I mean home assistant could find the tricky name /dev/serial/by-id/usb-QEMU_QEMU_USB_SERIAL_1-0000:00:07.7-4-if00-port0 but if I go to command-line in unraid I will only see /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2132783-if00 I have also tried a reboot fully of the system now so that was awesome (last time I had a power outage and stuff stopped working) Quote Link to comment
SimonF Posted August 17, 2022 Share Posted August 17, 2022 Not that I know of, but you can see the attached USBs on the VM root@computenode:~# virsh qemu-monitor-command HA --hmp info usb Device 0.2, Port 1, Speed 480 Mb/s, Product QEMU USB Tablet, ID: input0 Device 0.2, Port 4, Speed 12 Mb/s, Product QEMU USB Serial, ID: ua-serial001016 Device 0.2, Port 2, Speed 12 Mb/s, Product host:1.4, ID: hostdev0 Quote Link to comment
ljm42 Posted September 16, 2022 Share Posted September 16, 2022 I apologize but I am not fully understanding the issue here. Can someone please write up a feature request for what we want to happen? Some questions we need to answer: * How can the VM manager identify these devices that need special treatment? * What does the VM manager do with them today, and what does it need to do differently? * If I need to buy a device to test with, can you give me an Amazon link to purchase one? * What is the simplest possible test VM to prove whether or not it is working? Edit: Many thanks to stefan.tomko for the info here: https://forums.unraid.net/topic/122358-upgrade-from-692-610rc4-usb-in-vm-problem/page/2/#comment-1170445 As this serial functionality is already handled by SimonF's excellent USB Manager plugin there is no urgency to add it to the base OS. 1 Quote Link to comment
Pixelpaule Posted September 16, 2022 Share Posted September 16, 2022 (edited) Hello, so unfortunately I can not give any information about the technical problems, but for me personally runs the Phoscon ConBee II with Unraid "Version: 6.10.3" and Home Assistant (Home Assistant 2022.9.4; Supervisor 2022.08.6; Operating System 9.0; Frontend 20220907.2 - latest) very unstable. Since yesterday and an update of Home Assistant it now does not run at all. With Unraid 6.9 I had no problems at all. I could simply select the stick in VM Manager (as seen in the screenshot) and it was detected cleanly in Home Assistant. Since the update to 6.10 the whole thing just doesn't work anymore. Here is a link to the Phoscon ConBee II from Dresden Elektronik. Can I provide more information logs etc? Edited September 16, 2022 by Pixelpaule Quote Link to comment
JorgeB Posted September 16, 2022 Share Posted September 16, 2022 I remember seeing a report that changing the USB Controller in the VM from 2.0 (EHCI) to 3.0 (quemu XHCI) helped with this, worth a try. Quote Link to comment
Pixelpaule Posted September 16, 2022 Share Posted September 16, 2022 The change from 2.0 (EHCI) to 3.0 (quemu XHCI) did not bring any improvement for me. Quote Link to comment
garion Posted September 18, 2022 Share Posted September 18, 2022 same here, sticky with 6.9. I try several 6.10.X with no results. 6.90 works like a charm but 6.10.x doesnt work if not "patched way" others partners used, editing the XML or using the USB Manager plugin so I revert to 6.9 Quote Link to comment
stefan.tomko Posted September 19, 2022 Share Posted September 19, 2022 I followed instructions given by SimonF. I use USB manager but did not know that new feature has been added to pass device to VM in serial mode. So instead of modifying XML file, all you need to do is: 1) install USB manager plugin 2) Do not attach any device in the VM properties. Instead go to USB manager menu, locate the device you want to pass to VM, and click on device settings here: 3) Enable "connect as serial only" You can also select auto connect if you want to. Side note - if you did pass the device via USB manager before, then you probably did not use serial only mode. By checking this, mode will change. 4) Shut down your VM and start it again, it should attach device to your selected VM in serial mode: Once that is done, all you need to do is change the path to device. I use Z2M - in Z2M configuration, I just changed path from /dev/serial/by-id/conbeeXYZ to /dev/serial/by-id/qemuXYZ That is it. My Zigbee network works without any additional intervention needed, and I successfully upgraded to 6.10.3 More info can be found here as well: https://community.home-assistant.io/t/solved-conbee-2-fails-to-connect-to-zha-ha-in-unraid-vm/431276/8 One user reported that if you are using ZHA instead of Z2M, you need to change the config (within the VM terminal) to ~/config/.storage/core.config_entries and provide new device path 2 2 Quote Link to comment
ljm42 Posted September 19, 2022 Share Posted September 19, 2022 9 hours ago, stefan.tomko said: I followed instructions given by SimonF. I use USB manager but did not know that new feature has been added to pass device to VM in serial mode. So instead of modifying XML file, all you need to do is: Thank you for writing this up! And thanks to SimonF for their excellent USB Manager plugin. These serial devices should not block anyone from upgrading to 6.10 and beyond. Quote Link to comment
Pixelpaule Posted September 23, 2022 Share Posted September 23, 2022 (edited) @stefan.tomko unfortunately, this does not work for me, as you have described it to me... How did you connect the stick to Z2M? I have always installed Z2M according to these instructions. But unfortunately the stick is not recognized correctly in Unraid. Under port I used /dev/ttyUSB0. Edit: These are my current settings: Home Assistant Hardware Infos (Settings -> System -> Hardware) Zigbee2MQTT Settings in HA: And i only get this Messages in the error log from Z2M: [19:05:53] INFO: Handing over control to Zigbee2MQTT Core ... Zigbee2MQTT:info 2022-09-23 19:05:55: Logging to console and directory: '/config/zigbee2mqtt/log/2022-09-23.19-05-55' filename: log.txt Zigbee2MQTT:info 2022-09-23 19:05:55: Starting Zigbee2MQTT version 1.27.2 (commit #unknown) Zigbee2MQTT:info 2022-09-23 19:05:55: Starting zigbee-herdsman (0.14.53) Zigbee2MQTT:info 2022-09-23 19:05:55: zigbee-herdsman started (resumed) Zigbee2MQTT:info 2022-09-23 19:05:55: Coordinator firmware version: '{"meta":{"maintrel":0,"majorrel":38,"minorrel":114,"product":0,"revision":"0x26720700","transportrev":0},"type":"ConBee2/RaspBee2"}' Zigbee2MQTT:info 2022-09-23 19:05:55: Currently 0 devices are joined: Zigbee2MQTT:info 2022-09-23 19:05:55: Zigbee: disabling joining new devices. Zigbee2MQTT:info 2022-09-23 19:05:57: Connecting to MQTT server at mqtt://core-mosquitto Zigbee2MQTT:error 2022-09-23 19:05:57: MQTT failed to connect: Connection refused: Not authorized Zigbee2MQTT:error 2022-09-23 19:05:57: Exiting... Zigbee2MQTT:info 2022-09-23 19:05:57: Stopping zigbee-herdsman... Zigbee2MQTT:info 2022-09-23 19:05:58: Stopped zigbee-herdsman Edit Edit: 🤣 What surprises me the most: I have deactivated Z2M in Home Assistant and installed the ZHA integration. This works without problems and the stick is recognized correctly by ZHA. I did not change anything in the USB Manager settings. Edited September 24, 2022 by Pixelpaule 1 Quote Link to comment
stefan.tomko Posted September 24, 2022 Share Posted September 24, 2022 Your issue is with MQTT setup. I responded to you in HA forum. 1 Quote Link to comment
Pixelpaule Posted September 24, 2022 Share Posted September 24, 2022 Here the Info for all Unraid user... This is my Post from the HA Forum Okay, it works… It was a mistake in the configuration. In the first YouTube tutorial, the YouTuber did not specify a username or password in the Z2M configuration. In the updated version of the Video he does! So I had to put only the data from the mqtt-user in the configuration of Z2M! Now it seems to work! 1 Quote Link to comment
garion Posted September 26, 2022 Share Posted September 26, 2022 On 9/19/2022 at 8:52 AM, stefan.tomko said: 3) Enable "connect as serial only" finally I update to unraid 6.11.0 It works great but, Do you know why my ConBeeII serial number change from DEXXXXXX in USB Manager to /dev/serial/by-id/usb-QEMU_QEMU_USB_SERIAL_1-0000:00:YYY? Do you keep your original serial number in Unraid VM with USB Manager? thanks Quote Link to comment
SimonF Posted September 26, 2022 Share Posted September 26, 2022 2 minutes ago, garion said: finally I update to unraid 6.11.0 It works great but, Do you know why my ConBeeII serial number change from DEXXXXXX in USB Manager to /dev/serial/by-id/usb-QEMU_QEMU_USB_SERIAL_1-0000:00:YYY? Do you keep your original serial number in Unraid VM with USB Manager? thanks No qemu creates a new virtual name for it in serial mode hence the new name. I use an alais on the config so i know the usb device. 1 Quote Link to comment
Magic815 Posted October 1, 2022 Share Posted October 1, 2022 So I think I'm still having an issue with one of my USBs, after following the instructions of switching them to serial mode. This is what I see in USB manager after doing an upgrade to unRAID 6.10.3: Any thoughts on what else I could try? Quote Link to comment
stefan.tomko Posted October 1, 2022 Share Posted October 1, 2022 Same happened to me when I was once playing with VM and adapters. But it happened for devices that I passed normally and as serial. At some point, I had 3 "virsh error" messages for 3 adapters. That was already on 6.11.0. Rebooted Unraid, rebooted VM... no luck. After few moments, I did detach and attach devices again, and virsh error was gone. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.