{"action":"created","issue":{"url":"https://api.github.com/repos/mavlink/mavlink/issues/901","repository_url":"https://api.github.com/repos/mavlink/mavlink","labels_url":"https://api.github.com/repos/mavlink/mavlink/issues/901/labels{/name}","comments_url":"https://api.github.com/repos/mavlink/mavlink/issues/901/comments","events_url":"https://api.github.com/repos/mavlink/mavlink/issues/901/events","html_url":"https://github.com/mavlink/mavlink/issues/901","id":320892592,"number":901,"title":"Add temperature sensor instance reporting","user":{"login":"jaxxzer","id":8315108,"avatar_url":"https://avatars3.githubusercontent.com/u/8315108?v=4","gravatar_id":"","url":"https://api.github.com/users/jaxxzer","html_url":"https://github.com/jaxxzer","followers_url":"https://api.github.com/users/jaxxzer/followers","following_url":"https://api.github.com/users/jaxxzer/following{/other_user}","gists_url":"https://api.github.com/users/jaxxzer/gists{/gist_id}","starred_url":"https://api.github.com/users/jaxxzer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jaxxzer/subscriptions","organizations_url":"https://api.github.com/users/jaxxzer/orgs","repos_url":"https://api.github.com/users/jaxxzer/repos","events_url":"https://api.github.com/users/jaxxzer/events{/privacy}","received_events_url":"https://api.github.com/users/jaxxzer/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2018-05-07T17:44:40Z","updated_at":"2018-05-07T19:38:36Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Suggestion for a new mavlink message:\r\n\r\nid: TEMPERATURE\r\n- uint32 timestamp\r\n- char[16] name\r\n- float temperature (degrees C)\r\n\r\nI know that the currently available plotting tools do not support 'instance fields' in a mavlink message, but that is another problem, and I think this is the most sensible way to enable reporting temperatures from different components ie 'imu1' 'esc1' 'probe1' in a flexible manner."},"comment":{"url":"https://api.github.com/repos/mavlink/mavlink/issues/comments/387178862","html_url":"https://github.com/mavlink/mavlink/issues/901#issuecomment-387178862","issue_url":"https://api.github.com/repos/mavlink/mavlink/issues/901","id":387178862,"user":{"login":"jaxxzer","id":8315108,"avatar_url":"https://avatars3.githubusercontent.com/u/8315108?v=4","gravatar_id":"","url":"https://api.github.com/users/jaxxzer","html_url":"https://github.com/jaxxzer","followers_url":"https://api.github.com/users/jaxxzer/followers","following_url":"https://api.github.com/users/jaxxzer/following{/other_user}","gists_url":"https://api.github.com/users/jaxxzer/gists{/gist_id}","starred_url":"https://api.github.com/users/jaxxzer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jaxxzer/subscriptions","organizations_url":"https://api.github.com/users/jaxxzer/orgs","repos_url":"https://api.github.com/users/jaxxzer/repos","events_url":"https://api.github.com/users/jaxxzer/events{/privacy}","received_events_url":"https://api.github.com/users/jaxxzer/received_events","type":"User","site_admin":false},"created_at":"2018-05-07T19:38:36Z","updated_at":"2018-05-07T19:38:36Z","author_association":"CONTRIBUTOR","body":"Does a new message really require such a process? This is not an additional micro-service. It is protocol spec.\r\n\r\n`Protocol specification and documentation changes are usually changes with less impact and can be directly raised as pull requests against this repository.`\r\n\r\n"}}
{"actor":{"display_login":"jaxxzer"}}