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

Jump to bottom

MultilevelSensorCC: Requirement to probe sensors #195

Closed
1 of 2 tasks
AlCalzone opened this issue Jul 26, 2019 · 1 comment · Fixed by #558
Closed
1 of 2 tasks

MultilevelSensorCC: Requirement to probe sensors #195

AlCalzone opened this issue Jul 26, 2019 · 1 comment · Fixed by #558
Assignees
@AlCalzone
Labels
new docs Changes that are required by newly discovered documentation

Comments

@AlCalzone
Copy link
Member

AlCalzone commented Jul 26, 2019 •
edited
Loading

Unless unsolicited Multilevel Sensor Report Commands are received, a controlling node MUST:

  • Probe the current reading for each supported sensor type at least every 6 hours for listening nodes.
  • Probe the current reading for each supported sensor type when the supporting node issues a Wake Up Notification Command for sleeping nodes.
@AlCalzone AlCalzone added CC new docs Changes that are required by newly discovered documentation labels Jul 26, 2019
@AlCalzone AlCalzone self-assigned this Jul 26, 2019
@AlCalzone AlCalzone added this to the v2.0.0 milestone Aug 18, 2019
@AlCalzone
Copy link
Member Author

The 2nd point will be done in #408

@AlCalzone AlCalzone modified the milestones: v2.0.0, Future Nov 17, 2019
@AlCalzone AlCalzone mentioned this issue Jan 10, 2020
Merged
@AlCalzone AlCalzone removed this from the Future milestone Jan 19, 2021
mdoggydog pushed a commit to mdoggydog/node-zwave-js that referenced this issue Jan 3, 2022
@raman325 @balloob
Add logging forwarder (zwave-js#195)
73cae0b 
* Add logging forwarder

* comments and bug fix

* fix tests

* use message symbol since it is fully formatted

* remove logging statements

* bump zwave-js and fix bug

* missed commit

* turn on when its needed and off when its no longer needed

* remove unused imports

* make clients private

* remove unused function

* default to list for transports

* bug fix

* try something else

* rework to simplify

* add structured data to event in case we want to do something with it downstreaem

* change approach slightly

* Add workaround for issue that occurs on first attach

* rename log transport class

* update docs

* set log level when creating log transport

* dont keep recreating transport, just change log level on the fly

* do better cleanup

* fix order of operations

* make commands driver level commands

* missed commit

* one less line

* drop to from listening logs commands

* Update src/lib/server.ts

Co-authored-by: Paulus Schoutsen <paulus@home-assistant.io>

* initialize log forwarder only when needed

* Update src/lib/server.ts

Co-authored-by: Paulus Schoutsen <paulus@home-assistant.io>

* prettier

* remove unnecessary guard

* Update src/lib/logging.ts

Co-authored-by: Paulus Schoutsen <paulus@home-assistant.io>

* simplify

Co-authored-by: Paulus Schoutsen <paulus@home-assistant.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AlCalzone AlCalzone

Labels
new docs Changes that are required by newly discovered documentation
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Schedule a refresh of values when no unsolicited updates are received zwave-js/node-zwave-js
1 participant
@AlCalzone