-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with MQTT #15
Comments
I used the great eNet library of Magnus to create my own eNET2MQTT project, written in Python. It works great with an uptime of more than 150 days now. It is however not finished yet to release and I am still working on it off-and-on (hope to have more time available after the holidays). If you can not get your version to work and you are somewhat capable with Python code, sharing my results up to now can maybe help you. |
Hi nestorix1343, |
Are other devices visible through MQTT? Or is this the only device that doesn't show up? |
None of the enet devices show up. Other applications are able to communicate to the MQTT broker. |
Hi,
I realize this code is not being maintained anymore, but I'll try regardless since it seems to be the only eNet to MQTT project out there and I don't like to run everything through HA.
I managed to install the docker container and run it, but for some reason it doesn't appear to publish the information to MQTT.
Logs show the device and the MQTT topic, but I don't see it happening in MQTT Explorer.
04-Jul-23 20:36:00 - HA Autoconfigure: homeassistant/light/f3f1a218-078e-48e9-82b8-369800000383-1/config {"name": "Mijn thuis:Onderverdieping:Keuken:Dimmen", "unique_id": "f3f1a218-078e-48e9-82b8-369800000383-1", "brightness": true, "schema": "json", "device": {"name": "Mijn thuis:Onderverdieping:Keuken:Kookeiland", "identifiers": ["f3f1a218-078e-48e9-82b8-369800000383"], "model": "DVT_DA1M", "manufacturer": "Jung"}, "platform": "mqtt", "brightness_scale": 100, "command_topic": "enet/f3f1a218-078e-48e9-82b8-369800000383-1/set", "state_topic": "enet/f3f1a218-078e-48e9-82b8-369800000383-1/state"}
Any thoughts?
The text was updated successfully, but these errors were encountered: