{"action":"created","issue":{"url":"https://api.github.com/repos/TD22057/insteon-mqtt/issues/86","repository_url":"https://api.github.com/repos/TD22057/insteon-mqtt","labels_url":"https://api.github.com/repos/TD22057/insteon-mqtt/issues/86/labels{/name}","comments_url":"https://api.github.com/repos/TD22057/insteon-mqtt/issues/86/comments","events_url":"https://api.github.com/repos/TD22057/insteon-mqtt/issues/86/events","html_url":"https://github.com/TD22057/insteon-mqtt/issues/86","id":371656328,"node_id":"MDU6SXNzdWUzNzE2NTYzMjg=","number":86,"title":"Cannot migrate insteon-mqtt to a new system","user":{"login":"djfjeff","id":10726912,"node_id":"MDQ6VXNlcjEwNzI2OTEy","avatar_url":"https://avatars1.githubusercontent.com/u/10726912?v=4","gravatar_id":"","url":"https://api.github.com/users/djfjeff","html_url":"https://github.com/djfjeff","followers_url":"https://api.github.com/users/djfjeff/followers","following_url":"https://api.github.com/users/djfjeff/following{/other_user}","gists_url":"https://api.github.com/users/djfjeff/gists{/gist_id}","starred_url":"https://api.github.com/users/djfjeff/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/djfjeff/subscriptions","organizations_url":"https://api.github.com/users/djfjeff/orgs","repos_url":"https://api.github.com/users/djfjeff/repos","events_url":"https://api.github.com/users/djfjeff/events{/privacy}","received_events_url":"https://api.github.com/users/djfjeff/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":14,"created_at":"2018-10-18T18:32:22Z","updated_at":"2018-10-23T14:07:41Z","closed_at":null,"author_association":"NONE","body":"Hi,\r\n\r\nI want to migrate insteon-mqtt from my Raspberry Pi to a VM. I installed everything with the same procedure that I have, connected the modem to the VM and started insteon-mqtt.\r\n\r\nTo this point, everything seems to work fine. But if I try to do a refresh-all, I get these error on the terminal : \r\n\r\n```\r\nNo read handler found for message type 0x69: All link get first: ack: True\r\nNo read handler found for message type 0x57: InpAllLinkRec: 21.xx.xx grp: 1 in_use: True type: CTRL last: False data: 0x01 0x00 0x00\r\nNo read handler found for message type 0x69: All link get first: ack: True\r\n```\r\n\r\nThe weird issue is that after the command finish, insteon-mqtt has erased my modem data file in data/\r\n\r\nIf I connect the modem back on my Raspberry Pi, refresh-all works fine there.\r\n\r\nAny idea?"},"comment":{"url":"https://api.github.com/repos/TD22057/insteon-mqtt/issues/comments/432261721","html_url":"https://github.com/TD22057/insteon-mqtt/issues/86#issuecomment-432261721","issue_url":"https://api.github.com/repos/TD22057/insteon-mqtt/issues/86","id":432261721,"node_id":"MDEyOklzc3VlQ29tbWVudDQzMjI2MTcyMQ==","user":{"login":"TD22057","id":1421685,"node_id":"MDQ6VXNlcjE0MjE2ODU=","avatar_url":"https://avatars2.githubusercontent.com/u/1421685?v=4","gravatar_id":"","url":"https://api.github.com/users/TD22057","html_url":"https://github.com/TD22057","followers_url":"https://api.github.com/users/TD22057/followers","following_url":"https://api.github.com/users/TD22057/following{/other_user}","gists_url":"https://api.github.com/users/TD22057/gists{/gist_id}","starred_url":"https://api.github.com/users/TD22057/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/TD22057/subscriptions","organizations_url":"https://api.github.com/users/TD22057/orgs","repos_url":"https://api.github.com/users/TD22057/repos","events_url":"https://api.github.com/users/TD22057/events{/privacy}","received_events_url":"https://api.github.com/users/TD22057/received_events","type":"User","site_admin":false},"created_at":"2018-10-23T14:07:41Z","updated_at":"2018-10-23T14:07:41Z","author_association":"OWNER","body":"Did you also run the exact same call in insteon-mqtt as test1.py?.  If the light on/off commands in test1.py work properly, then run the same command in insteon-mqtt and check the logs.\r\n\r\nFor the refresh problem, that isn't enough log output.  The code does set handlers for messages but it does that only in the correct context.  Meaning the handler for the 0x69 message is activated when that message should show up (after a refresh message is sent) - not at other times.  So the problems isn't in the log section you're posting - it's before that.  If the handler is not active, there is some reason why it was turned off (timed out, something else interrupted it) - that should be in the logs.  Post the full log from when the refresh command request arrives until the end.\r\n\r\nps: I do all my dev and testing on Ubuntu 16.04 so a real 64 bit OS isn't the issue."}}
{"actor":{"display_login":"TD22057"}}