Add additional Homie implementations#39
Open
labodj wants to merge 1 commit intohomieiot:masterfrom
Open
Conversation
Member
|
Always nice to see new support for the specification, especially if it involves the new versions of it :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi,
I would like to add three Homie-related projects I have been working on to the implementations page.
The first one is
homie-v5, a maintained fork ofhomie-esp8266for ESP8266/ESP32 Arduino projects. Itkeeps Homie 3.0.1 as the default behavior, while also adding opt-in support for Homie 4.0.0 and Homie 5.x
metadata.
The other two projects are focused on Home Assistant MQTT discovery:
homie-home-assistant-discovery, a Node.js library and CLI that maps Homie MQTT metadata to HomeAssistant MQTT discovery payloads.
node-red-contrib-homie-home-assistant-discovery, a Node-RED node built on top of the same corelibrary, intended for users who prefer wiring this integration directly inside Node-RED flows.
I tried to keep the change small and limited to the existing implementations tables, without changing the
surrounding content or structure.
Validation done locally:
I could not run the full Hugo build locally because Docker/Hugo are not available in my local checkout.