Closed richard-scott closed 3 years ago
Can someone merge this back into the main stream please?
Version 0.1.2-beta uses MQTT and has the correct manifest.json
. If you aren't using Hildebrand hardware, I'm maintaining a fork here to get the data via the DCC instead
Hey all, apologies for my delay in replying to this, entirely missed the notifications for this but I'm enthused by the interest around seeing this integration working.
As @HandyHat points out, the https://github.com/unlobito/ha-hildebrandglow/tree/0.1.2-beta release uses MQTT and can pull real-time data from Hildebrand's hardware. I've set the repo's default branch to https://github.com/unlobito/ha-hildebrandglow/tree/mqtt so the current development state is a bit clearer. I have some local WIP code that aims to use Home Assistant's new energy management entities for reporting total meter readings which I hope to finish soon.
I should emphasise this integration is alpha quality at best- I've been running https://github.com/unlobito/ha-hildebrandglow/tree/0.1.2-beta for several months on my personal HA instance (using a Glow stick CAD), but it lacks error handling for DCC-only accounts.
I wasn't familiar with @HandyHat's fork, but I'd love pull requests here to re-add DCC functionality once the MQTT integration is stabler with a broader aim to merge this integration into https://github.com/home-assistant/core/. Best of luck with your fork in the meantime!
@unlobito I'd love to help add DCC functionality once you think MQTT is ready. Thanks for your support of the fork!
Manifests now need a version number otherwise the custom component doesn't get loaded.