{"action":"created","issue":{"url":"https://api.github.com/repos/JMRI/JMRI/issues/5774","repository_url":"https://api.github.com/repos/JMRI/JMRI","labels_url":"https://api.github.com/repos/JMRI/JMRI/issues/5774/labels{/name}","comments_url":"https://api.github.com/repos/JMRI/JMRI/issues/5774/comments","events_url":"https://api.github.com/repos/JMRI/JMRI/issues/5774/events","html_url":"https://github.com/JMRI/JMRI/issues/5774","id":358405978,"node_id":"MDU6SXNzdWUzNTg0MDU5Nzg=","number":5774,"title":"Refactor LocoNet Monitor to use jmri.jmrix.Message","user":{"login":"devel-bobm","id":13856693,"node_id":"MDQ6VXNlcjEzODU2Njkz","avatar_url":"https://avatars0.githubusercontent.com/u/13856693?v=4","gravatar_id":"","url":"https://api.github.com/users/devel-bobm","html_url":"https://github.com/devel-bobm","followers_url":"https://api.github.com/users/devel-bobm/followers","following_url":"https://api.github.com/users/devel-bobm/following{/other_user}","gists_url":"https://api.github.com/users/devel-bobm/gists{/gist_id}","starred_url":"https://api.github.com/users/devel-bobm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/devel-bobm/subscriptions","organizations_url":"https://api.github.com/users/devel-bobm/orgs","repos_url":"https://api.github.com/users/devel-bobm/repos","events_url":"https://api.github.com/users/devel-bobm/events{/privacy}","received_events_url":"https://api.github.com/users/devel-bobm/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":9,"created_at":"2018-09-09T19:47:53Z","updated_at":"2018-09-09T23:04:01Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Improve the implementation of LocoNet Monitor by making use of the `jmri.jmrix.Message` interface.  This would make it possible for \"tunneling\" connections to use \"LocoNet Monitor\" message interpretations without the \"tunneling\" mechanism having to know about LocoNet managers.  This would specifically help interpret \"tunneled\" LocoNet-style messages as seen with the Roco Z21.\r\n\r\nRef: the first @pabender comment in #5764."},"comment":{"url":"https://api.github.com/repos/JMRI/JMRI/issues/comments/419751633","html_url":"https://github.com/JMRI/JMRI/issues/5774#issuecomment-419751633","issue_url":"https://api.github.com/repos/JMRI/JMRI/issues/5774","id":419751633,"node_id":"MDEyOklzc3VlQ29tbWVudDQxOTc1MTYzMw==","user":{"login":"pabender","id":14183416,"node_id":"MDQ6VXNlcjE0MTgzNDE2","avatar_url":"https://avatars2.githubusercontent.com/u/14183416?v=4","gravatar_id":"","url":"https://api.github.com/users/pabender","html_url":"https://github.com/pabender","followers_url":"https://api.github.com/users/pabender/followers","following_url":"https://api.github.com/users/pabender/following{/other_user}","gists_url":"https://api.github.com/users/pabender/gists{/gist_id}","starred_url":"https://api.github.com/users/pabender/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pabender/subscriptions","organizations_url":"https://api.github.com/users/pabender/orgs","repos_url":"https://api.github.com/users/pabender/repos","events_url":"https://api.github.com/users/pabender/events{/privacy}","received_events_url":"https://api.github.com/users/pabender/received_events","type":"User","site_admin":false},"created_at":"2018-09-09T23:04:01Z","updated_at":"2018-09-09T23:04:01Z","author_association":"MEMBER","body":"\n\nSent from my iPad\n\n> On Sep 9, 2018, at 6:53 PM, Bob Milhaupt <notifications@github.com> wrote:\n> Yes, Llnmon.java does use specific prefixes. Sensor messages seen on the L2 connection are decoded with respect to prefix \"L2\". That way the displayed \"user names\" match both the connection and the sensor number. This is currently only done for Turnouts, Sensors, and Reporters.\n> \n\nI would actually prefer that it doesn’t have that hard link to the system name at all.  It seems to be a very heavyweight process that prevents some legitimate uses."}}
{"actor":{"display_login":"pabender"}}