CONBEE II Debian 11 VM Ware

Hello everyone,
I saw the video today for Zigbee2Mqtt, so I feel like testing Gladys again to hopefully replace my Jeedom, which is satisfying me less and less…

I performed a custom installation of Gladys on a Debian on a VM installed on WMWare.
I have a Conbee II dongle that is properly paired on the VM.

When I go to the Zigbee2MQTT module

It appears, but it still detects that it is not present.
I saw on this post and in the ZIGBEE2MQTT documentation that you need to add the deconz information in the configuration.yaml file, but the problem is that Gladys does not install the MQTT instance because it does not find a dongle.

Do you have any idea how to fix the problem?

Have a great day everyone and thanks a lot.

Steve

Hello @oufman!

Content that my video made you want to try again :slight_smile:

We agree, what you did is just:

  • Arrive at the integration
  • Click on « Settings »
  • Select this USB port
  • Click on backup

?

Nothing else?

At this stage, Gladys does not check anything at the USB level, it just records the USB port, so there is no notion of « Conbee II in experimental support » at this stage, here we just record the USB port.

This should work.

If the container is not created, there must be another problem.

Edit: You are on a Debian VM

Which release is it?

Thanks for your quick reply.
And by the way, your videos are great, I’ve been following your project since the beginning, I really want to take the step because I find the interface clean, the logic behind it interesting and sustainable.

To get back to my problem, yes indeed, I just selected the port and clicked save, but Gladys doesn’t seem to want to validate further, the message remains on no USB port selected.

Thanks for your help,
Yes a VM on Debian 11.2

We’re having issues with bullseye on raspberry, if you can test it in 10 that would be great.

Another point, is serial device sharing okay in VM Ware (Host → Guest)? Does the host not lock access (exclusive)?

Thanks, it’s always nice to hear! :slight_smile:

Ok, so indeed we’re not even at the Zigbee2mqtt step.

Are you definitely on Chrome / Firefox or Safari just to be sure?

You can quickly check the requests made by your browser when you display the page and click on save?

(Right-click on the page => Inspect element => Network), then you check if an error occurs during the save.

Can you send us a screenshot of the responses here?

Edit: You’re lucky you get the right to a double live debug with hardware/system with @VonOx and software with me :smiley:

With pleasure.

I confirm that I am Chrome.
It seems there is a 500 error.

Yes, I appreciate getting help so quickly. That’s great.

I can try to reinstall a VM with Debian 10.

Regarding the lock, I don’t think so, because I use the same system for Jeedom (another VM and another CoinbeeII key), but I don’t have this problem.

Can you check Gladys’s logs when the 500 error occurs?

docker logs gladys --tail=1000

I wouldn’t be surprised if it’s the issue related to bullseye, the 500 like this on the connect looks a lot like a dockerode error…

Yep, the same as on raspy, except that we go a bit further, the environment is detected

So I tried to copy the logs, but apparently the forum limits me in the number of characters.

Is there something in particular I should look for in them?

Edit: Can I attach a text file?

So, which Linux distribution do you recommend? Is Debian 10 okay?

An error? ^^

Otherwise, if it’s too long, https://pastebin.com/

@oufman @pierre-gilles I created a new topic

Here you go :slight_smile:

Thanks, that’s indeed simpler and will prevent cluttering the other post.

Bingo, that’s right, it’s Debian 11!

Same symptom as on raspberry, dockerode is broken :slight_smile:

2022-01-11T09:26:53+0100 <warn> service.start.js:44 (Service.start) Unable to start service zigbee2mqtt Error: (HTTP code 301) unexpected -
    at /src/server/node_modules/docker-modem/lib/modem.js:301:17
    at getCause (/src/server/node_modules/docker-modem/lib/modem.js:331:7)
    at Modem.buildPayload (/src/server/node_modules/docker-modem/lib/modem.js:300:5)
    at IncomingMessage.<anonymous> (/src/server/node_modules/docker-modem/lib/modem.js:275:14)
    at IncomingMessage.emit (events.js:412:35)
    at endReadableNT (internal/streams/readable.js:1334:12)
    at processTicksAndRejections (internal/process/task_queues.js:82:21) {
  reason: undefined,
  statusCode: 301,
  json: <Buffer >
}
2022-01-11T09:26:53+0100 <error> index.js:20 (process.<anonymous>) uncaughtException catched: uncaughtException
2022-01-11T09:26:53+0100 <error> index.js:21 (process.<anonymous>) Error: getaddrinfo ENOTFOUND containers
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:71:26) {
  errno: -3008,
  code: 'ENOTFOUND',
  syscall: 'getaddrinfo',
  hostname: 'containers'
}

@pierre-gilles @VonOx :slight_smile:

You guys are in sync.

So, it’s a no-go on the 11 for now, should I reinstall a VM with Debian 10?