{"action":"closed","issue":{"url":"https://api.github.com/repos/home-assistant/home-assistant/issues/2422","repository_url":"https://api.github.com/repos/home-assistant/home-assistant","labels_url":"https://api.github.com/repos/home-assistant/home-assistant/issues/2422/labels{/name}","comments_url":"https://api.github.com/repos/home-assistant/home-assistant/issues/2422/comments","events_url":"https://api.github.com/repos/home-assistant/home-assistant/issues/2422/events","html_url":"https://github.com/home-assistant/home-assistant/issues/2422","id":163525589,"number":2422,"title":"Z-wave switch(es) go rogue on a pretty regular basis (with video!)","user":{"login":"ryanborstelmann","id":5846854,"avatar_url":"https://avatars.githubusercontent.com/u/5846854?v=3","gravatar_id":"","url":"https://api.github.com/users/ryanborstelmann","html_url":"https://github.com/ryanborstelmann","followers_url":"https://api.github.com/users/ryanborstelmann/followers","following_url":"https://api.github.com/users/ryanborstelmann/following{/other_user}","gists_url":"https://api.github.com/users/ryanborstelmann/gists{/gist_id}","starred_url":"https://api.github.com/users/ryanborstelmann/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ryanborstelmann/subscriptions","organizations_url":"https://api.github.com/users/ryanborstelmann/orgs","repos_url":"https://api.github.com/users/ryanborstelmann/repos","events_url":"https://api.github.com/users/ryanborstelmann/events{/privacy}","received_events_url":"https://api.github.com/users/ryanborstelmann/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-07-02T16:28:57Z","updated_at":"2016-07-29T18:19:23Z","closed_at":"2016-07-29T18:19:23Z","body":"Make sure you are running the latest version of Home Assistant before reporting an issue.\r\n\r\nYou should only file an issue if you found a bug. Feature and enhancement requests should go in [the Feature Requests section](https://community.home-assistant.io/c/feature-requests) of our community forum:\r\n\r\n**Home Assistant release (`hass --version`):**\r\n[Edit: seeing behavior on 0.23 now] 0.22.1 on AiO installer on Raspbian Jessie Lite\r\n\r\n**Python release (`python3 --version`):**\r\n3.4.2\r\n\r\n**Component/platform:**\r\nzwave\r\n\r\n**Description of problem:**\r\n## See video here of behavior: https://youtu.be/6FOJBG0l3g8\r\n\r\n(forgive the portrait video, it was 4:30 AM)\r\n\r\nBasically, most mornings (four of the past five nights) - always between midnight and 6am CST and each occurrence at a different time, my bathroom & walk-in closet switches lose their damn minds. node_35 is my \"shower light\", which has an automation rule that appears to be in play here. The rule turns all bathroom switches on/off when this switch is turned on/off. Note that this rule works great for the other 23.9 hours of the day. You'll see reference to this rule in the logs below.\r\n[Edit: happened tonight at 10:30pm CST, which is about 8 hours after I re-installed raspbian jessie lite & the AiO installer]\r\n\r\n**Expected:**\r\nFor this to not happen.\r\n\r\n**Problem-relevant `configuration.yaml` entries and steps to reproduce:**\r\n```\r\nzwave:\r\n  usb_path: /dev/ttyACM0\r\n  polling_interval: 1000\r\n  customize:\r\n    switch.geswitch_switch_35:\r\n      polling_intensity: 1\r\n    switch.geswitch_switch_27:\r\n      polling_intensity: 10\r\n    switch.geswitch_switch_32:\r\n      polling_intensity: 10\r\n    switch.geswitch_switch_19:\r\n      polling_intensity: 10\r\n    switch.geswitch_switch_39:\r\n      polling_intensity: 10\r\n    switch.geswitch_switch_6:\r\n      polling_intensity: 10\r\n    switch.geswitch_switch_40:\r\n      polling_intensity: 10\r\n```\r\nNotice I have switch_35, the switch in question here, set to poll every second. Since the GE 12722 switches don't report state, i need to use polling, which is an incredibly inefficient means to do this, in my opinion. If only I'd waited for the HS100+ switches... anyways, most of the switches are set to every 10s just so the UI updates, but that one switch is on every second due to it being in an automation rule.\r\n\r\nRelevant automation rules:\r\n```\r\n- alias: \"Ryan's Bathroom - All On\"\r\n  trigger:\r\n    platform: state\r\n    entity_id: switch.geswitch_switch_35\r\n    state: 'on'\r\n  action:\r\n    service: homeassistant.turn_on\r\n    entity_id: group.ryan_bathroom\r\n \r\n- alias: \"Ryan's Bathroom - All Off\"\r\n  trigger:\r\n    platform: state\r\n    entity_id: switch.geswitch_switch_35\r\n    state: 'off'\r\n  action:\r\n    service: homeassistant.turn_off\r\n    entity_id: group.ryan_bathroom\r\n```\r\n\r\n- zwcfg_*.xml: http://hastebin.com/anosaxavis.xml\r\n- `hass` logs at the time when this happens (03:42 is the first instance. Included some lead up logs to show what's \"normal\" for this time of day): http://hastebin.com/alewekuwez.xml \r\n\r\nAnother thing to note is that my OZW_log.txt file is huge - 300MB in each case. Sometimes it doesn't even log any longer and doesn't even log/catch this happening. I end up at about 3 million lines of logs, from the looks of things. Not sure if that's relevant.\r\n\r\n1. Wait till some time after midnight\r\n2. Watch the lights lose it\r\n3. restart `hass` to fix it for about 24 hours\r\n\r\n**Additional info:**\r\nThis only started when I moved from Docker to the AiO installer last week. I'm going to try re-installing, but something tells me I'll see the same behavior.\r\n"}}
{"actor":{"display_login":"ryanborstelmann"}}