Hub Mesh Bug - Custom drivers from linked devices selectable when creating virtual devices

@bobbyD @gopher.ny I discovered a bug with Hub Mesh as I was migrating my LAN apps from a C7 to a C8 Pro. I know that when you use Hub Mesh to link a device on a target hub that a copy of the driver is available on the target hubs. This driver "copy" is selectable when creating new virtual devices and if you select it the Add Device screen will spin indefinitely. This shows up when the source device is using a custom driver.

Steps to reproduce:

  1. Choose a device that utilizes a custom driver to where the code is on the source hub but not on a target hub.
    • On the source hub, enable hub mesh on this device that uses a custom driver
  2. On a target hub, go to Settings \ Hub Mesh \ Linked Devices and add that device to the hub.
  3. Navigate to Devices, click Add device, and choose Virtual
  4. Click the Select device type drop down and type in the name of the custom driver from the source hub and notice it is selectable on the target hub.
  5. Select that driver and enter a name and click Create and notice it spins forever.
  6. Using another browser, navigate to the device list and you will find a device created with that name and the selected driver will show on the list, but if you open the device notice the "Type" value is empty:

To make things more confusing and where I noticed this issue, add the custom driver to your target hub and follow the steps above but on step 6 you will notice you have 2 custom drivers to choose from:

The first selection is the "linked copy" and if you choose it, the Add device will spin forever. If you choose the second selection, the device will immediately be created.

1 Like

With the driver installed on the second hub, I also noticed that when creating the device I saw the two copies of the driver, but in the Device Details page, when selecting the driver (Type), I only saw one.

Correct but if you choose the first one when creating a virtual switch the driver (type) will be blank and when viewing the device.

Yes, that's what I saw as well. Took me a minute to work out this was the issue when installing my EcoWitt drivers on my test hub where I had also meshed my actual ecowitt gateway device from one of my production hubs.

1 Like