Repository navigation
Releases
Releases · 3735943886/rustuya-local
v0.2.3
- Log why a device is unavailable, once per reason: a warning naming the device, the bridge's error (with the
reason
rustuya-bridge 0.4.6 adds to an unreachable device); a warning when a device is connected but its state never
arrives; and a warning, once per device, when an event's dps cannot be read. Before, all of these were silent or
debug-only, so a device could stay unavailable with nothing in the log. - The bridge's error text, in the log and on the panel's device cards, leaves out the
idandnamethe bridge adds. - Require pyrustuyabridge 0.4.6, whose embedded bridge gives an unreachable device's
reasonand keeps a device that
rejects the local key reported as such (914) instead of unreachable (905). - Let Home Assistant start without waiting for rustuya (on a NanoPi R5C, setting up the entry held the start for
47.7 s; 10 s now): the integration's modules load with it instead of queueing behind every other integration's
imports. - A minute after the start, one line under
custom_components.rustuyasays how many of the bridge's devices report:
a warning, pointing at therustuya_localwarnings, when the bridge reports devices as not connected or nothing
reports at all, and otherwise at info level. Filtering the log by the integration's name showed nothing of them. - A failure to start (the broker unreachable, for one) now leaves the entry retrying setup, which Home Assistant
retries with backoff, instead of failed. - The panel's Edit device and Register manually say that a device whose LAN broadcasts do not reach this host
needs both its IP and its version, and ask before saving a Wi-Fi device with an IP but no version (the bridge does
not connect until it knows the version). The README says the same under Requirements and Troubleshooting.
Full Changelog: v0.2.2...v0.2.3
v0.2.3rc3
- Log why a device is unavailable, once per reason: a warning naming the device, the bridge's error (with the
reason
rustuya-bridge 0.4.6 adds to an unreachable device) and what to check; a warning when a device is connected but its
state never arrives (usually a wrong protocol version); and a warning, once per device, when an event's dps cannot be
read. Before, all of these were silent or debug-only, so a device could stay unavailable with nothing in the log. - The bridge's error text, in the log and on the panel's device cards, leaves out the
idandnamethe bridge adds. - Require pyrustuyabridge 0.4.6, whose embedded bridge gives an unreachable device's
reasonand keeps a device that
rejects the local key reported as such (914) instead of unreachable (905). - Let Home Assistant start without waiting for rustuya (on a NanoPi R5C, setting up the entry held the start for
47.7 s; 10 s now): the integration's modules load with it instead of queueing behind every other integration's
imports. - A minute after the start, one line under
custom_components.rustuyasays how many of the bridge's devices report,
how many are not connected or sent no state, and that the reasons are logged underrustuya_local: filtering the
log by the integration's name showed nothing of them. - A failure to start (the broker unreachable, for one) now leaves the entry retrying setup, which Home Assistant
retries with backoff, instead of failed.
Full Changelog: v0.2.3rc2...v0.2.3rc3
v0.2.3rc2
- Log why a device is unavailable, once per reason: a warning naming the device, the bridge's error (with the
reason
rustuya-bridge 0.4.6 adds to an unreachable device) and what to check; a warning when a device is connected but its
state never arrives (usually a wrong protocol version); and a warning, once per device, when an event's dps cannot be
read. Before, all of these were silent or debug-only, so a device could stay unavailable with nothing in the log. - The bridge's error text, in the log and on the panel's device cards, leaves out the
idandnamethe bridge adds. - Require pyrustuyabridge 0.4.6, whose embedded bridge gives an unreachable device's
reasonand keeps a device that
rejects the local key reported as such (914) instead of unreachable (905). - Let Home Assistant start without waiting for rustuya: while it starts, the entity platforms, the hub and the service
start once Home Assistant has started (on a NanoPi R5C, setting up the entry held the start for 47.7 s). The
entities appear then. - A failure to start (the broker unreachable, for one) now leaves the entry retrying setup, which Home Assistant
retries with backoff, instead of failed.
Full Changelog: v0.2.3rc1...v0.2.3rc2
v0.2.3rc1
- Log why a device is unavailable, once per reason: a warning naming the device, the bridge's error (with the
reason
rustuya-bridge 0.4.6 adds to an unreachable device) and what to check; a warning when a device is connected but its
state never arrives (usually a wrong protocol version); and a warning, once per device, when an event's dps cannot be
read. Before, all of these were silent or debug-only, so a device could stay unavailable with nothing in the log. - The bridge's error text, in the log and on the panel's device cards, leaves out the
idandnamethe bridge adds. - Require pyrustuyabridge 0.4.6, whose embedded bridge gives an unreachable device's
reasonand keeps a device that
rejects the local key reported as such (914) instead of unreachable (905).
Full Changelog: v0.2.2...v0.2.3rc1
v0.2.2
- Fix setup failing now and then (about one Home Assistant start in 64) with the built-in MQTT broker: its per-start
password could begin with-, which the broker took for an option ("unexpected argument '-A' found"). The password
no longer can, and the integration requires pymqttd 0.1.0, which accepts any password. - Spell the integration's name in lowercase, rustuya: in the integration list, the sidebar, the panel, and the title
of a newly added entry. An existing entry keeps its title.
Full Changelog: v0.2.1...v0.2.2
v0.2.1
- Add a setup choice for users without an MQTT broker: Beginner: everything inside Home Assistant (recommended) runs the
embedded bridge on a broker of the integration's own (pymqttd, rumqttd in a
child process), on127.0.0.1with per-start credentials. It is first in the setup menu, with the two expert choices
(your own MQTT broker) after it. - Fix Home Assistant freezing when the Tuya login's QR form was submitted before the login had finished: the submit
now shows progress while the login is checked, and the QR again if nothing was scanned. - Fix a scene, or any single action that sets a light's colour and brightness together, changing only the brightness
and leaving the light on the previous colour or white (#3): require tuya-interpreter 0.1.1, which computes each
write on the values it has just sent as well as those the device reported.
What's Changed
- Built-in MQTT broker for users without one by @3735943886 in #4
- Put the beginner setup mode first in the setup menu by @3735943886 in #5
- Fix the QR form's submit freezing Home Assistant; 0.2.1rc4 by @3735943886 in #6
- Keep the QR check waiting whatever calls the step meanwhile by @3735943886 in #7
Full Changelog: v0.2.0...v0.2.1
v0.2.1rc4
- Add a setup choice for users without an MQTT broker: Beginner: everything inside Home Assistant (recommended) runs the
embedded bridge on a broker of the integration's own (pymqttd, rumqttd in a
child process), on127.0.0.1with per-start credentials. It is first in the setup menu, with the two expert choices
(your own MQTT broker) after it. - Fix Home Assistant freezing when the Tuya login's QR form was submitted before the login had finished: the submit
now shows progress while the login is checked, and the QR again if nothing was scanned. - Fix a scene, or any single action that sets a light's colour and brightness together, changing only the brightness
and leaving the light on the previous colour or white (#3): require tuya-interpreter 0.1.1, which computes each
write on the values it has just sent as well as those the device reported.
What's Changed
- Fix the QR form's submit freezing Home Assistant; 0.2.1rc4 by @3735943886 in #6
Full Changelog: v0.2.1rc3...v0.2.1rc4
v0.2.1rc3
- Add a setup choice for users without an MQTT broker: Beginner: everything inside Home Assistant (recommended) runs the
embedded bridge on a broker of the integration's own (pymqttd, rumqttd in a
child process), on127.0.0.1with per-start credentials. It is first in the setup menu, with the two expert choices
(your own MQTT broker) after it. - Fix a scene, or any single action that sets a light's colour and brightness together, changing only the brightness
and leaving the light on the previous colour or white (#3): require tuya-interpreter 0.1.1, which computes each
write on the values it has just sent as well as those the device reported.
What's Changed
- Put the beginner setup mode first in the setup menu by @3735943886 in #5
Full Changelog: v0.2.1rc2...v0.2.1rc3
v0.2.1rc2
- Add a setup choice for users without an MQTT broker: No MQTT broker: run everything inside Home Assistant runs the
embedded bridge on a broker of the integration's own (pymqttd, rumqttd in a
child process), on127.0.0.1with per-start credentials. A broker of your own stays the usual way. - Fix a scene, or any single action that sets a light's colour and brightness together, changing only the brightness
and leaving the light on the previous colour or white (#3): require tuya-interpreter 0.1.1, which computes each
write on the values it has just sent as well as those the device reported.
What's Changed
- Built-in MQTT broker for users without one by @3735943886 in #4
Full Changelog: v0.2.1rc1...v0.2.1rc2
v0.2.1rc1
- Fix a scene, or any single action that sets a light's colour and brightness together, changing only the brightness
and leaving the light on the previous colour or white (#3): require tuya-interpreter 0.1.1, which computes each
write on the values it has just sent as well as those the device reported.
Full Changelog: v0.2.0...v0.2.1rc1