{"action":"created","issue":{"url":"https://api.github.com/repos/john30/ebusd/issues/79","repository_url":"https://api.github.com/repos/john30/ebusd","labels_url":"https://api.github.com/repos/john30/ebusd/issues/79/labels{/name}","comments_url":"https://api.github.com/repos/john30/ebusd/issues/79/comments","events_url":"https://api.github.com/repos/john30/ebusd/issues/79/events","html_url":"https://github.com/john30/ebusd/issues/79","id":220484115,"number":79,"title":"Arch Linux: cannot query ebusd anymore after sys upgrade","user":{"login":"milankni","id":937861,"avatar_url":"https://avatars0.githubusercontent.com/u/937861?v=3","gravatar_id":"","url":"https://api.github.com/users/milankni","html_url":"https://github.com/milankni","followers_url":"https://api.github.com/users/milankni/followers","following_url":"https://api.github.com/users/milankni/following{/other_user}","gists_url":"https://api.github.com/users/milankni/gists{/gist_id}","starred_url":"https://api.github.com/users/milankni/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/milankni/subscriptions","organizations_url":"https://api.github.com/users/milankni/orgs","repos_url":"https://api.github.com/users/milankni/repos","events_url":"https://api.github.com/users/milankni/events{/privacy}","received_events_url":"https://api.github.com/users/milankni/received_events","type":"User","site_admin":false},"labels":[{"id":256934916,"url":"https://api.github.com/repos/john30/ebusd/labels/help%20wanted","name":"help wanted","color":"159818","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":11,"created_at":"2017-04-09T17:06:02Z","updated_at":"2017-05-01T09:27:30Z","closed_at":null,"body":"Hi,\r\n\r\nI use Arch Linux on RPi 2 and after update of many packages (see below), I cannot query ebusd anymore. I use Ebusd Koppler by eservice-online.de (USB version).\r\n\r\nWhat still works\r\nEbusd can 'see' the messages broadcasted by the HVAC (well, the 'read timeout' for ACK is a new message):\r\n```\r\n2017-04-09 17:20:26.934 [bus debug] ERR: read timeout during receive command ACK, switching to skip                     \r\n2017-04-09 17:20:30.635 [update info] update MS cmd: 1008b5110101 / 0928296011ffff0000ff                                \r\n2017-04-09 17:20:30.636 [update notice] update MS StatusTHER: 20.0;20.5;17.375;-;-;0                                    \r\n2017-04-09 17:20:32.290 [bus debug] ERR: read timeout during receive command ACK, switching to skip                     \r\n2017-04-09 17:20:32.871 [update info] update MS cmd: 1008b5040100 / 0a00ffffffffffffff6011                              \r\n2017-04-09 17:20:32.872 [update notice] update MS OutsideTemp: 17.375                                                   \r\n2017-04-09 17:20:33.127 [update info] update MS cmd: 1008b5110102 / 050014965a78                                        \r\n2017-04-09 17:20:33.127 [update notice] update MS PumpStatus: off                                                       \r\n2017-04-09 17:20:34.723 [main debug] performing regular tasks\r\n```\r\nHowever, any command to actively query ebus results in errors, e.g. 'ebusctl read RoomTemp':\r\n```\r\n2017-04-09 09:46:08.259 [main debug] >>> read RoomTemp                                                                  \r\n2017-04-09 09:46:08.259 [bus info] send message: 3115b509030d3a00                                                       \r\n2017-04-09 09:46:08.301 [bus debug] notify request: ERR: read timeout                                                   \r\n2017-04-09 09:46:08.302 [bus error] send to 15: ERR: read timeout, retry                                                \r\n2017-04-09 09:46:08.302 [bus debug] ERR: read timeout during ready, switching to skip                                   \r\n2017-04-09 09:46:08.364 [bus debug] notify request: ERR: read timeout                                                   \r\n2017-04-09 09:46:08.365 [bus error] send to 15: ERR: read timeout, retry                                                \r\n2017-04-09 09:46:08.365 [bus debug] ERR: read timeout during ready, switching to skip                                   \r\n2017-04-09 09:46:08.429 [bus debug] notify request: ERR: read timeout                                                   \r\n2017-04-09 09:46:08.429 [bus error] send to 15: ERR: read timeout, retry                                                \r\n2017-04-09 09:46:08.429 [bus debug] ERR: read timeout during ready, switching to skip                                   \r\n2017-04-09 09:46:08.493 [bus debug] notify request: ERR: read timeout                                                   \r\n2017-04-09 09:46:08.493 [bus error] send to 15: ERR: read timeout                                                       \r\n2017-04-09 09:46:08.493 [bus error] send message part 0: ERR: read timeout                                              \r\n2017-04-09 09:46:08.493 [main debug] <<< ERR: read timeout                                                              \r\n2017-04-09 09:46:08.493 [bus debug] ERR: read timeout during ready, switching to skip                                   \r\n2017-04-09 09:46:08.494 [main debug] >>>                                                                                \r\n                                                                                                                        \r\n ... lot of empty lines removed ...                                                                                     \r\n                                                                                                                        \r\n2017-04-09 09:46:08.494 [main debug] <<< ERR: command not found                                                         \r\n2017-04-09 09:46:08.494 [network debug] [00007] wait for result                                                         \r\n2017-04-09 09:46:08.494 [network info] [00007] connection closed\r\n```\r\nI tried various versions of ebusd (2.1 - master), but no go. Interestingly, in raspbian jessy ebusd 2.4 (binary downloaded from github) works just fine.\r\n\r\nShortly before the failure, I upgraded many packages (list is attached), although I assume the best candidate might be kernel or rpi firmware or possibly the new boot configuration (there is a new directory /boot/overlays, whose README says that RPi now boots with device tree enabled - I do not understand the architecture much to be able to comment on that). \r\n\r\n[pacman.log.txt](https://github.com/john30/ebusd/files/908375/pacman.log.txt)\r\n\r\nAny idea?"},"comment":{"url":"https://api.github.com/repos/john30/ebusd/issues/comments/298310480","html_url":"https://github.com/john30/ebusd/issues/79#issuecomment-298310480","issue_url":"https://api.github.com/repos/john30/ebusd/issues/79","id":298310480,"user":{"login":"Crazyachmed","id":8402464,"avatar_url":"https://avatars0.githubusercontent.com/u/8402464?v=3","gravatar_id":"","url":"https://api.github.com/users/Crazyachmed","html_url":"https://github.com/Crazyachmed","followers_url":"https://api.github.com/users/Crazyachmed/followers","following_url":"https://api.github.com/users/Crazyachmed/following{/other_user}","gists_url":"https://api.github.com/users/Crazyachmed/gists{/gist_id}","starred_url":"https://api.github.com/users/Crazyachmed/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Crazyachmed/subscriptions","organizations_url":"https://api.github.com/users/Crazyachmed/orgs","repos_url":"https://api.github.com/users/Crazyachmed/repos","events_url":"https://api.github.com/users/Crazyachmed/events{/privacy}","received_events_url":"https://api.github.com/users/Crazyachmed/received_events","type":"User","site_admin":false},"created_at":"2017-05-01T09:27:30Z","updated_at":"2017-05-01T09:27:30Z","body":"I have the same issue.\r\n\r\nWorking: 4.9.12-1\r\nBroken (at least) since 4.9.14-2\r\nStill broken: 4.9.25-1\r\n\r\nSo the issue has to be in somewhere between the first to versions which points to 4.9.13 as you already mentioned.\r\n\r\nIs there anything I can run with debugs flags or do you want me to test 4.9.13 specifically?"}}
{"actor":{"display_login":"Crazyachmed"}}