First of all thank you for Cube OS Docker release!
I have a nas with a Cube OS (version 2.12.0) container, and others with Home Assistant and Mosquitto Broker. In the Cube OS container I’m using a Sonoff Dongle Plus MG24 (latest firmware) and I’ve successfully connected some Sonoff Zigbee devices, but I also would sync these devices to Home Assistant via mqtt, but can’t find mqtt server settings (if it’s possible).
I would use the MQTT Broker in Cube Os too, but always get “Failed to respond” error in settings page, even if the port 1883 is free (it would be great can change mqtt broker parameters however).
Hello,
Thank you for your detailed feedback.
We have successfully reproduced this issue, and our R&D team will need some time to analyze and locate the root cause. We will keep you updated as soon as we have any progress.
We truly appreciate your patience and understanding.
I use Zigbee2mqtt from home assistant as eWeLink Cube can see the status also from node Red and the use their open api to make a device. Pretty sure Zigbee2mqtt is available as a docker. There are some rules to allow automatically adding MQTT entities to home assistant. Maybe Cube could do something similar.
if you only have a few devices why not just listen to the device, filter it and MQTT out node in node Red?
specifically to home assistant you can install the eWeLink Palette in node red and then change an input Boolean or input number as a node Red flow.
You’re right I confirm that Zigbee2Mqtt is available as docker container, that was my “Plan B” to integrate devices in Home Assistant and other platforms, but still don’t know how to integrate them in Cube OS through mqtt, cause I haven’t found mqtt settings telling Cube OS, ip address, port, user, etc. configurations of an external Mqtt Broker.
I’d rather not install Node Red at the moment, but that is a good alternative to solve the problem.
What I would like to do is pairing Sonoff Zigbee devices in Cube OS and sync them to Home Assistant, like I saw is possible in the link below, but in that guide is being used Sonoff bridge.
I thought that was possbile in Cube OS with Dongle Plus MG24 too.
You don’t need any of that as the devices will all send MQTT messages. Just install an MQTT monitoring software such as MQTT explorer and copy the topics into the MQTT in node, although you’ll get everything and need to filter it. You will also need to copy the specific data address so that a switch node grabs the right data and then use eWeLink Cube to create a virtual device. There are loads of capabilities in the open API. More than real devices. Then after the switch node just use a template node to write json to change the state put to that device. Bingo you have the device in both systems. Quite a lot of work but fine for a small number of devices. I think they should automate reading Zigbee2MQTT messages like the GUI does in Home Assistant and do it automatically whenever you add a new device to zigbee2mqtt: appears both in Home Assistant and eWeLink Cube.
I think they should automate reading Zigbee2MQTT messages like the GUI does in Home Assistant and do it automatically whenever you add a new device to zigbee2mqtt: appears both in Home Assistant and eWeLink Cube.
This is a chance. What I expect to do is even simpler, pairing zigbee devices in Cube OS, and send data to a MQTT Broker (even manually entering settings), so I can integrate them in Home Assistant. I think Cube OS team can do it in their sleep! This function is already present in iHost and some Sonoff bridges, Dongle Max too I saw. I hope that’ll be available soon in Cube OS.
The solution you explained is for sure good, but I need something simpler, since I also plan to increase zigbee devices, and that will get a lot of work.
This function is already present in iHost and some Sonoff bridges, Dongle Max too I saw. I hope that’ll be available soon in Cube OS.