Possiblity to test via Docker

[chris-1243]

@Nerivec It looks really promising. I am just wondering if I may use a Docker container to test and crash.
All my setups are based on Docker (test and main network). Would you think I might run the commands required inside the Z2M container to get all the dependencies needed ?
By the way, do you have any time frame regarding RCP firmware for zstack (TI, maybe @Koenkk is working on this...?)

[Nerivec]

To run this in a Z2M container would be a bit complex (have to link repos, override dependencies, rebuild everything...), best to wait until the draft PR is merged, then it should be as easy as running any other adapter.

No timeframe on other stacks, need to find some time to build a few, test them out, see what's what 😉

[chris-1243]

Too much work for you at the moment. I am going to wait until the PR is merged and some RCP firmwares become available for zstack.

By the way, will it be easier to move from on driver to an other ? Let's say I'm in zstack and I have a Silabs coordinator I wish to use. Is the coordinator_backup still specific to the driver or as the stack is then stored in the computer, I may switch easily ?

[Nerivec]

All network parameters are controlled in this setup, so, switching should be as easy as unplugging the adapter, and putting in the other one (and changing the adapter path in config as needed). The adapter is only used for transmitting over the radio (hence "Radio Co-Processor", vs "Network Co-Processor"). 😉

As for switching from an already established NCP network to RCP, that remains to be figured out (taking over the network is easy enough, but re-populating all device parameters, not so much, have to dig into the NVM...).

[chris-1243]

I am wondering if I may run the npm command directly inside a Docker container... I need to try

[Nerivec]

Did you run npm run build?
npm run build:prod does not compile src/dev/*

https://github.com/Nerivec/zigbee-on-host/blob/main/package.json#L12-L13

[chris-1243]

Here is what I have done:

• start Z2M container (obviously with a dongle attached to it)
• ssh in the container and install npm with apk add npm
• in /app, I ran npm install then npm run build

I am not familiar at all with npm. Also, should I copy/paste some files?

[Nerivec]

There is something weird with that path though
/app/dist/dist/dev/cli.js should probably be /app/dist/dev/cli.js
Might need to check what's going on with the filesystem in the container, why that double dist.

[chris-1243]

I tried again with a simple debian container. I cloned your repo and mount it in the container.

I installed the npm packages and ran the commands. Everything went fine and I have been able to start the network👍 with a TI chip.

Any possibilities to already tell Z2M to connect to this instance?

[Nerivec]

No dev:cli is meant for direct/basic testing (a "minimal Z2M"), mostly for network forming and device joining.
We'll need the ZH adapter PR for use with Z2M.