{"action":"created","issue":{"url":"https://api.github.com/repos/Koenkk/zigbee2mqtt/issues/453","repository_url":"https://api.github.com/repos/Koenkk/zigbee2mqtt","labels_url":"https://api.github.com/repos/Koenkk/zigbee2mqtt/issues/453/labels{/name}","comments_url":"https://api.github.com/repos/Koenkk/zigbee2mqtt/issues/453/comments","events_url":"https://api.github.com/repos/Koenkk/zigbee2mqtt/issues/453/events","html_url":"https://github.com/Koenkk/zigbee2mqtt/issues/453","id":367480723,"node_id":"MDU6SXNzdWUzNjc0ODA3MjM=","number":453,"title":"Double response messages when publishing to zigbee2mqtt/<deviceid>/set","user":{"login":"simonvanderveldt","id":204286,"node_id":"MDQ6VXNlcjIwNDI4Ng==","avatar_url":"https://avatars0.githubusercontent.com/u/204286?v=4","gravatar_id":"","url":"https://api.github.com/users/simonvanderveldt","html_url":"https://github.com/simonvanderveldt","followers_url":"https://api.github.com/users/simonvanderveldt/followers","following_url":"https://api.github.com/users/simonvanderveldt/following{/other_user}","gists_url":"https://api.github.com/users/simonvanderveldt/gists{/gist_id}","starred_url":"https://api.github.com/users/simonvanderveldt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/simonvanderveldt/subscriptions","organizations_url":"https://api.github.com/users/simonvanderveldt/orgs","repos_url":"https://api.github.com/users/simonvanderveldt/repos","events_url":"https://api.github.com/users/simonvanderveldt/events{/privacy}","received_events_url":"https://api.github.com/users/simonvanderveldt/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-10-06T17:59:48Z","updated_at":"2018-10-07T19:43:11Z","closed_at":null,"author_association":"NONE","body":"When I publish a message to `zigbee2mqtt/<deviceid>/set` I get two messages in return to `zigbee2mqtt/<deviceid>`, the first one seems to echo the command sent to `/set`, the second one seems to be the actual response from the device, for example when I publish `{\"state\": \"off\"}` to `zigbee2mqtt/<deviceid>/set` I get the following two responses:\r\n```\r\nzigbee2mqtt/<deviceid> {\"state\":\"off\"}\r\nzigbee2mqtt/<deviceid> {\"state\":\"OFF\"}\r\n```\r\nThese logs only show up if the payload is recognized, i.e. if I send `{\"state\":\"foo\"}` nothing happens.\r\nThe second message is always in full caps, the first one is the same as the message I sent to `/set`.\r\n\r\nIs this expected behavior?\r\n\r\n[edit] I'm using version 0.1.6"},"comment":{"url":"https://api.github.com/repos/Koenkk/zigbee2mqtt/issues/comments/427680957","html_url":"https://github.com/Koenkk/zigbee2mqtt/issues/453#issuecomment-427680957","issue_url":"https://api.github.com/repos/Koenkk/zigbee2mqtt/issues/453","id":427680957,"node_id":"MDEyOklzc3VlQ29tbWVudDQyNzY4MDk1Nw==","user":{"login":"Koenkk","id":2892853,"node_id":"MDQ6VXNlcjI4OTI4NTM=","avatar_url":"https://avatars0.githubusercontent.com/u/2892853?v=4","gravatar_id":"","url":"https://api.github.com/users/Koenkk","html_url":"https://github.com/Koenkk","followers_url":"https://api.github.com/users/Koenkk/followers","following_url":"https://api.github.com/users/Koenkk/following{/other_user}","gists_url":"https://api.github.com/users/Koenkk/gists{/gist_id}","starred_url":"https://api.github.com/users/Koenkk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Koenkk/subscriptions","organizations_url":"https://api.github.com/users/Koenkk/orgs","repos_url":"https://api.github.com/users/Koenkk/repos","events_url":"https://api.github.com/users/Koenkk/events{/privacy}","received_events_url":"https://api.github.com/users/Koenkk/received_events","type":"User","site_admin":false},"created_at":"2018-10-07T19:43:11Z","updated_at":"2018-10-07T19:43:11Z","author_association":"OWNER","body":"This is expected behavior, zigbee2mqtt mocks a state message when the bulb is turned on/off, for two reasons:\r\n\r\n- Some bulbs don't send their OFF state when they are turned off (in your case it did), this would mean that you won't get an acknowledge.\r\n- In a situation where home assistant (or any other home automation software) bulb state is not in sync; e.g. actual state is ON, home assistant state is OFF. Home assistant would send an ON command but because the bulb is already ON, it would never acknowledge the ON command, in that case home assistant is stuck in the OFF state."}}
{"actor":{"display_login":"Koenkk"}}