Add support of Zigbee2Mqtt Assistant

[robertcsakany]

Adding Web Interface to Zigebee2Mqtt. It getting the data from mqtt, so mqtt support have to be enabled in zigbee2mqtt container.

[krema]

@robertcsakany can you please resolve the merge conflict? It would be good if we could finally merge that into a master.

@Willem-Dekker everything looks good except the merge conflict, doesn't it?

[robertcsakany]

I think its okay. Its very simple container, only MQTT is required,

[Willem-Dekker]

@robertcsakany is this tested? i cant test is my self since i don't use zigbee

[krema]

I am already using it and can confirm that it works.

[Willem-Dekker]

@robertcsakany or @krema could you update the documentation as wel so others know how to use it and what it does, you can add a page in the /docs folder

[robertcsakany]

Sure. In the next week I will add some. And yes, its tested. I'm make changes only which I use by daily basis.

[ristomatti]

I just migrated from gcgarner's repo. It seemed to already have zigbee2mqtt assistant and I was already using it but I see now it's gone after migration. I'd like to know at what point has it disappeared?

[robertcsakany]

@Willem-Dekker Please check it' I've added some documentation.

[ristomatti]

Any schedule when this will be merged? I just happen to be on the remote location I'd want to setup IOTstack (incl. Zigbee2MqttAssistant) for today and leaving tomorrow. 🙂

I can of course merge this locally but is there still something missing for this to work properly?

[Slyke]

Hey @ristomatti and @robertcsakany , I have put this into the new-menu branch (along with zigbee2mqtt). I'm almost ready to merge it to the experimental branch. For now I left the virtual host setting to use xip.io, but do note that this will change in the future (it will have a configurable option, as this service can be hosted on the RPi, see: #83 )

[Slyke]

Hey @ristomatti and @robertcsakany can you please test zigbee2mqtt_assistant and/or zigbee2mqtt (plus any other serives you use) on the experimental branch? Please let me know if you run into any bugs, big or small. I have no way to test that the zigbee services are working correctly with the new menu.
In the project directory you can type the following:

git fetch
git checkout experimental
git pull
./menu.sh

[ristomatti]

@Slyke I'll try to remember when I'm next time at the install location. Meanwhile I found out though pretty much the same functionality can be achieved within Node-RED using https://flows.nodered.org/node/node-red-contrib-zigbee2mqtt and its bridge node. But maybe zigbee2mqtt assistant is a bit cleaner solution so I'll sure test it.

I was already successfully using it from Graham's repo before I switched over. Are there any significant changes?

[Slyke]

@ristomatti Yes! There are a lot of changes! I pretty much rewrote the entire stack from the ground up in Python (due to its popularity and ease of use when interfacing with YAML). I've been testing the new stack on multiple platforms (not just RPis), but some of the hardware specific stuff is difficult to test. Majority of it is done, there may be some small bugs. Ensure you have a working backup - mainly your docker-compose.yml file.

It was written in Python for planned future features (mainly auto-configuration based on selected services and hardware). You'll already see some of them have been completed, like port conflict checking and so on. I'll be starting on the documentation for it once I'm happy everyone else will be happy with it.

If you find any bugs, or even usability issues please let me know. Will attempt to fix.

Edit:

I added "node-red-contrib-zigbee2mqtt" to the list of installable NodeRed modules.

[robertcsakany]

@Slyke What about this PR? Can I merge it?

[ukkopahis]

Functionality has been added via other commits. This PR should be closed.