Skip to content

Update z-wave.markdown #917

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
Merged
merged 4 commits into from
Sep 13, 2016
Merged

Update z-wave.markdown #917

merged 4 commits into from
Sep 13, 2016

Conversation

sgauche
Copy link
Contributor

@sgauche sgauche commented Sep 9, 2016

I added this automation when first setting up Home Assistant and the soft reset has been very problematic for me, it hangs my zstick gen5. So I wanted to make sure that people only add this automation if they run into issues and not add it as part of setting up hass.

@sgauche
Update z-wave.markdown
a71a7ba 
I added this automation when first setting up Home Assistant and the soft reset has been very problematic for me, it hangs my zstick gen5.  So I wanted to make sure that people only add this automation if they run into issues and not add it as part of setting up hass.
@fabaff
Copy link
Member

fabaff commented Sep 9, 2016

Is this related to #606?

@sgauche
Copy link
Contributor Author

sgauche commented Sep 9, 2016

It wasn't, but it sounds like the same issue I was having.

On Sep 9, 2016 10:44 AM, "Fabian Affolter" notifications@github.com wrote:

Is this related to #606
#606?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#917 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH3lXeZwE0kXq1k2VXQ3DAZqFCeKiV8Qks5qoXDHgaJpZM4J5Gl6
.

@sgauche
Copy link
Contributor Author

sgauche commented Sep 9, 2016

@fabaff I wouldn't ever see any traceback calls in the home assistant log like the forum post linked in #606. I would just see this in the OWZ_log.txt

2016-09-09 02:30:00.537 Info, Soft-resetting the Z-Wave controller chip
2016-09-09 02:30:00.538 Detail, contrlr, Queuing (Command) Soft-resetting the Z-Wave controller chip: 0x01, 0x03, 0x00, 0x08, 0xf4
2016-09-09 02:30:00.538 Detail, 
2016-09-09 02:30:00.538 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x00) - Soft-resetting the Z-Wave controller chip: 0x01, 0x03, 0x00, 0x08, 0xf4
2016-09-09 02:30:00.540 Detail, contrlr, Removing current message
2016-09-09 02:31:00.526 Detail, Node001, Queuing (Controller) Request Node Neighbor Update
2016-09-09 02:31:00.527 Detail, Node002, Queuing (Controller) Request Node Neighbor Update
2016-09-09 02:31:00.527 Detail, Node003, Queuing (Controller) Request Node Neighbor Update
2016-09-09 02:31:00.527 Detail, Node004, Queuing (Controller) Request Node Neighbor Update
2016-09-09 02:31:00.527 Info, Requesting Neighbor Update for node 1
2016-09-09 02:31:00.527 Detail, Node001, Queuing (Command) ControllerCommand_RequestNodeNeighborUpdate (Node=1): 0x01, 0x05, 0x00, 0x48, 0x01, 0x4e, 0xfd
2016-09-09 02:31:00.527 Detail, Notification: ControllerComand - Starting
2016-09-09 02:31:00.528 Detail, 
2016-09-09 02:31:00.528 Info, Node001, Sending (Command) message (Callback ID=0x4e, Expected Reply=0x48) - ControllerCommand_RequestNodeNeighborUpdate (Node=1): 0x01, 0x05, 0x00, 0x48, 0x01, 0x4e, 0xfd
2016-09-09 02:31:01.528 Error, Node001, ERROR: Dropping command, expected response not received after 1 attempt(s)
2016-09-09 02:31:01.528 Detail, Node001, Removing current message
2016-09-09 02:31:01.528 Detail, Node001, Notification: Notification - TimeOut
2016-09-09 02:31:01.529 Detail, Notification: ControllerCommand - Error - Failed
2016-09-09 02:31:01.529 Info, Requesting Neighbor Update for node 2
2016-09-09 02:31:01.530 Detail, 
2016-09-09 02:31:01.530 Detail, Node002, Queuing (Controller) Request Node Neighbor Update
2016-09-09 02:31:01.530 Detail, Notification: ControllerComand - Starting
2016-09-09 02:31:01.530 Detail, Notification: ControllerCommand - Sleeping
2016-09-09 02:31:01.531 Info, Requesting Neighbor Update for node 3
2016-09-09 02:31:01.531 Detail, 
2016-09-09 02:31:01.531 Detail, Node003, Queuing (Controller) Request Node Neighbor Update
2016-09-09 02:31:01.531 Detail, Notification: ControllerComand - Starting
2016-09-09 02:31:01.531 Detail, Notification: ControllerCommand - Sleeping
2016-09-09 02:31:01.532 Info, Requesting Neighbor Update for node 4
2016-09-09 02:31:01.532 Detail, Node004, Queuing (Command) ControllerCommand_RequestNodeNeighborUpdate (Node=4): 0x01, 0x05, 0x00, 0x48, 0x04, 0x51, 0xe7
2016-09-09 02:31:01.532 Detail, Notification: ControllerComand - Starting
2016-09-09 02:31:01.532 Detail, 
2016-09-09 02:31:01.533 Info, Node004, Sending (Command) message (Callback ID=0x51, Expected Reply=0x48) - ControllerCommand_RequestNodeNeighborUpdate (Node=4): 0x01, 0x05, 0x00, 0x48, 0x04, 0x51, 0xe7
2016-09-09 02:31:02.533 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
2016-09-09 02:31:02.533 Detail, Node004, Removing current message
2016-09-09 02:31:02.533 Detail, Node004, Notification: Notification - TimeOut
2016-09-09 02:31:02.534 Detail, Notification: ControllerCommand - Error - Failed
2016-09-09 09:27:49.363 Info, Node004, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True
2016-09-09 09:27:49.363 Info, Node004, SwitchBinary::Set - Setting node 4 to On
2016-09-09 09:27:49.363 Detail, Node004, Queuing (Send) SwitchBinaryCmd_Set (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x25, 0x01, 0xff, 0x25, 0x52, 0x4d
2016-09-09 09:27:49.363 Detail, Node004, Queuing (Send) SwitchBinaryCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x25, 0x02, 0x25, 0x53, 0xb2
2016-09-09 09:27:49.363 Detail, 
2016-09-09 09:27:49.364 Info, Node004, Sending (Send) message (Callback ID=0x52, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x25, 0x01, 0xff, 0x25, 0x52, 0x4d
2016-09-09 09:27:50.364 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
2016-09-09 09:27:50.364 Detail, Node004, Removing current message
2016-09-09 09:27:50.364 Detail, Node004, Notification: Notification - TimeOut

Landrash
Landrash reviewed Sep 9, 2016
View reviewed changes
source/getting-started/z-wave.markdown
@@ -199,8 +199,7 @@ The Z-Wave component exposes seven services to help maintain the network.
| test_network | Tells the controller to send no-op commands to each node and measure the time for a response. In theory, this can also bring back nodes which have been marked "presumed dead".|
| rename_node | Sets a node's name. Requires an `entity_id` and `name` field. |

The soft_reset and heal_network commands can be used as part of an automation script
to help keep a zwave network running relliably. For example:
The `soft_reset` and `heal_network` commands can be used as part of an automation script to help keep a zwave network running reliably as shown in the example below. By deafult, Home Assistant will run a `heal_network` at midnight. This is a configuration option for the zwave component, it defaults to `true` but can be diabled by setting `auto_heal` to false. Soft resetting some zwave controllers can cause the network to hang, so the below automation should only be used if there are issues with your zwave network.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Misspelled word: deafult should be default
Misspelled word: diabled should be disabled

@Landrash
Copy link
Contributor

Landrash commented Sep 9, 2016

Most likely this isn't caused by HA but is a problem with OZW.
I would suggest trying to replicate this outside of HA a bug report on their issue tracker.

Landrash
Landrash reviewed Sep 12, 2016
View reviewed changes
source/getting-started/z-wave.markdown
@@ -199,7 +199,7 @@ The Z-Wave component exposes seven services to help maintain the network.
| test_network | Tells the controller to send no-op commands to each node and measure the time for a response. In theory, this can also bring back nodes which have been marked "presumed dead".|
| rename_node | Sets a node's name. Requires an `entity_id` and `name` field. |

The `soft_reset` and `heal_network` commands can be used as part of an automation script to help keep a zwave network running reliably as shown in the example below. By deafult, Home Assistant will run a `heal_network` at midnight. This is a configuration option for the zwave component, it defaults to `true` but can be diabled by setting `auto_heal` to false. Soft resetting some zwave controllers can cause the network to hang, so the below automation should only be used if there are issues with your zwave network.
The `soft_reset` and `heal_network` commands can be used as part of an automation script to help keep a zwave network running reliably as shown in the example below. By default, Home Assistant will run a `heal_network` at midnight. This is a configuration option for the zwave component, the option defaults to `true` but can be disabled by setting `auto_heal` to false. Soft resetting some zwave controllers can cause the network to hang, so the below automation should only be used if there are issues with your zwave network.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this function if prefered for most users and is the default I would prefer something like this instead of the last sentence.

Using the soft_reset function with some z-wave controllers can cause cause the z-wave network to hang. If you're having issues with your z-wave network try disabling this automation.

@sgauche
Update z-wave.markdown
150566a 
changed last 2 sentences based on @Landrash suggestion.
@Landrash
Copy link
Contributor

One last thing. Your mixing z-wave and z-wave.
Just had a look and it's done all over the file in question. If you feel like fixing it go ahead, else I'll do it.

z-wave component should be zwave mentions of z-wave as a technology/network should most likely be z-wave. Openzwave shouldn't be touched since that the project name.
@fabaff you agree?

@sgauche
Update z-wave.markdown
04c2a96 
fixed usage of `zwave` component, Z-Wave for references to a Z-Wave network, and OpenZWave as a project name
@Landrash
Copy link
Contributor

Landrash commented Sep 13, 2016 •
edited
Loading

Thank you @sgauche
I'll merge this into a zwave branch to do some additional cleanup and add in the Pine 64 Z-wave module information.

edit Made a new branch instead.

@Landrash Landrash changed the base branch from current to z-wave September 13, 2016 05:50
@Landrash Landrash merged commit 3da35e3 into home-assistant:z-wave Sep 13, 2016
Landrash added a commit that referenced this pull request Sep 18, 2016
@Landrash
Cleanup and update of Z-Wave documenation (#935)
b167b8f 
* Update z-wave.markdown (#917)
- Notes added to Z-wave `soft-reset` about known issues by @sgauche 
- Fixed usage of `zwave` component, Z-Wave for references to a Z-Wave network, and OpenZWave as a project name by @sgauche
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@sgauche @fabaff @Landrash