Skip to content
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.

Sign up for GitHub

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

Fixed typos and broken links, removed whitespace in homie_legacy_stat… #172

Merged
merged 2 commits into from
Jul 17, 2019
Merged

Fixed typos and broken links, removed whitespace in homie_legacy_stat… #172

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1d12976
Fixed typos and broken links, removed whitespace in homie_legacy_stat…
EPNW-Eric Jul 17, 2019
acd646c
Fixed typo
EPNW-Eric Jul 17, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion convention.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -314,7 +314,7 @@ Any other topic is not part of the Homie convention.
This convention only covers discoverability of devices and its capabilities.
The aim is to have standardized MQTT topics for all kind of complex scenarios.
A Homie device may therefore support extensions, defined in separate documents.
Every extension is identified by a unique ID.
Every extension is identified by an unique ID.
EP-u-NW marked this conversation as resolved.
Show resolved Hide resolved

The ID consists of the reverse domain name and a freely chosen suffix.
The proper term `homie` is reserved and must not be used as the suffix or as part of the domain name.
Expand Down
2 changes: 1 addition & 1 deletion extensions/documents/homie_legacy_firmware_extension.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ Newer versions on the other hand, do not specify them.
If a device of a newer Homie version implements this extension, the above mentioned attributes are backwards-compatible to older Homie versions.
Respectively, these attributes of an older device can be made Homie `4.0` compliant, by simply advertising this extension as implemented.
By doing this, these legacy attribute can be kept, and the device doesn't have to be altered much.
In addition to this extension, a second extension, [Legacy Stats]() exists.
In addition to this extension, a second extension, [Legacy Stats](https://github.com/homieiot/convention/blob/develop/extensions/documents/homie_legacy_stats_extension.md) exists.
If this extension is implemented, too, not only the firmware attributes are backwards-compatible, but the whole device.

## Homie Version
Expand Down
2 changes: 1 addition & 1 deletion ...ocuments/homie_legacy _stats_extension.md → ...documents/homie_legacy_stats_extension.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ so it was removed from the convention and decided to offer it as extension (see
If a device of a newer Homie version implements this extension, the stats of the device are backwards-compatible to older Homie versions.
Respectively, the *$stats* attribute of an older device can be made Homie `4.0` compliant, by simply advertising this extension as implemented.
By doing this, the legacy *$stats* attribute can be kept, and the device doesn't have to be altered much.
In addition to this extension, a second extension, [Legacy Firmware]() exists.
In addition to this extension, a second extension, [Legacy Firmware](https://github.com/homieiot/convention/blob/develop/extensions/documents/homie_legacy_firmware_extension.md) exists.
If this extension is implemented, too, not only the stats are backwards-compatible, but the whole device.

## Homie Version
Expand Down