Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[pynetgear] Can't parse attached devices string
See original GitHub issueHi again.
On hassbian 84.3:
Running either 0.5.1, v1-default or master (with latest commit a7a6974) I still have the same errors as before:
2018-12-19 04:51:53 ERROR (Thread-7) [pynetgear] Can't parse attached devices string 2018-12-19 04:59:53 ERROR (Thread-9) [pynetgear] Can't parse attached devices string 2018-12-19 05:02:33 ERROR (Thread-2) [pynetgear] Can't parse attached devices string 2018-12-19 05:06:33 ERROR (Thread-5) [pynetgear] Can't parse attached devices string 2018-12-19 05:13:13 ERROR (Thread-20) [pynetgear] Can't parse attached devices string 2018-12-19 05:39:52 ERROR (Thread-7) [pynetgear] Can't parse attached devices string 2018-12-19 08:07:15 ERROR (Thread-6) [pynetgear] Can't parse attached devices string 2018-12-19 08:33:39 ERROR (Thread-14) [pynetgear] Can't parse attached devices string 2018-12-19 08:50:42 ERROR (Thread-4) [pynetgear] Can't parse attached devices string 2018-12-19 08:52:18 ERROR (Thread-5) [pynetgear] Can't parse attached devices string 2018-12-19 09:34:41 ERROR (Thread-5) [pynetgear] Can't parse attached devices string 2018-12-19 11:25:03 ERROR (Thread-7) [pynetgear] Can't parse attached devices string 2018-12-19 12:02:07 ERROR (Thread-5) [pynetgear] Can't parse attached devices #string
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
On 0.4.0 I have no errors and on 0.4.1 they start. It was fairly easy to find the reason too 😃 In 0.4.1 more logging where added and this showed up in the code after “0”:
if not decoded or decoded == "0": _LOGGER.error("Can't parse attached devices string") _LOGGER.debug(node.text.strip())Seems like my router (or maybe all R7800) gives this respons. I will leave it up to you to either find a fix or let me keep the error. At least I now know what is happening 👍
? It works as expected you just get an error because your router wrongly returns 0, your code does nothing expect using another log message instead… I’ll be frank I don’t care, send a PR if you want I’ll merge it.