Closed guyluz11 closed 1 year ago
Found out that ioBroker.esphome is only an adapter for esphome-native-api. This package didn't get updated in a long time so we may use one of the updated forks instead like nicerloop/esphome-native-api
The package didn't find my ESPhome device even though I saw it broadcasting mDNS in my local network. Tried also the fork from nicerloop but it didn't work, maybe this code is not compatible with the current ESPhome version.
Opened an issue about that just in case. https://github.com/Nafaya/esphome-native-api/issues/23
So there is a new fork that got maintained https://github.com/twocolors/esphome-native-api
here is the npm version of the package https://www.npmjs.com/package/node-red-contrib-esphome
Here is the Node-RED package that he created with it https://flows.nodered.org/node/node-red-contrib-esphome
Let's use the Node-RED integration as we did before with the Chromecast node-RED package.
Marged the pr, not tested in a snap but in contrast to the previous (python) implementation this does not use anything new that didn't get tested before under snap.
So I am closing the issue. Thanks
Currently there is an ESPhome support, it use the python package to control the devices. Unfortunately we are not able to make this package work under snap installation.
A new solution could be to use a JavaScript package to control the devices. For example ioBroker.esphome package.