Myq issues

Setup, Configuration and Use Beginners
1

Anyone having issues MyQ? I got it working last week and it worked for several days, now I get the error pasted below.

2017-12-16 10:58:37.139 [ERROR] [nhab.binding.myq.internal.MyqBinding] - Could not connect to MyQ service
java.io.IOException: Could not parse response
at org.openhab.binding.myq.internal.MyqData.request(MyqData.java:251)[214:org.openhab.binding.myq:1.10.0]
at org.openhab.binding.myq.internal.MyqData.getMyqData(MyqData.java:128)[214:org.openhab.binding.myq:1.10.0]
at org.openhab.binding.myq.internal.MyqBinding.poll(MyqBinding.java:210)[214:org.openhab.binding.myq:1.10.0]
at org.openhab.binding.myq.internal.MyqBinding.access$0(MyqBinding.java:202)[214:org.openhab.binding.myq:1.10.0]
at org.openhab.binding.myq.internal.MyqBinding$1.run(MyqBinding.java:407)[214:org.openhab.binding.myq:1.10.0]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_151]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)[:1.8.0_151]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)[:1.8.0_151]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)[:1.8.0_151]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_151]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_151]
at java.lang.Thread.run(Thread.java:748)[:1.8.0_151]
Caused by: org.codehaus.jackson.JsonParseException: Unexpected character (’<’ (code 60)): expected a valid value (number, String, array, object, ‘true’, ‘false’ or ‘null’)
at [Source: java.io.StringReader@7dccdb9b; line: 1, column: 2]
at org.codehaus.jackson.JsonParser._constructError(JsonParser.java:1432)[185:org.openhab.core.compat1x:2.1.0]
at org.codehaus.jackson.impl.JsonParserMinimalBase._reportError(JsonParserMinimalBase.java:385)[185:org.openhab.core.compat1x:2.1.0]
at org.codehaus.jackson.impl.JsonParserMinimalBase._reportUnexpectedChar(JsonParserMinimalBase.java:306)[185:org.openhab.core.compat1x:2.1.0]
at org.codehaus.jackson.impl.ReaderBasedParser._handleUnexpectedValue(ReaderBasedParser.java:1192)[185:org.openhab.core.compat1x:2.1.0]
at org.codehaus.jackson.impl.ReaderBasedParser.nextToken(ReaderBasedParser.java:479)[185:org.openhab.core.compat1x:2.1.0]
at org.codehaus.jackson.map.ObjectMapper._initForReading(ObjectMapper.java:2761)[185:org.openhab.core.compat1x:2.1.0]
at org.codehaus.jackson.map.ObjectMapper._readMapAndClose(ObjectMapper.java:2709)[185:org.openhab.core.compat1x:2.1.0]
at org.codehaus.jackson.map.ObjectMapper.readTree(ObjectMapper.java:1533)[185:org.openhab.core.compat1x:2.1.0]
at org.openhab.binding.myq.internal.MyqData.request(MyqData.java:222)[214:org.openhab.binding.myq:1.10.0]
… 11 more

2

Just noticed the same issue today. nothing changed on either end for me and yet it wont connect. Anyone know what might be going on?

3

I see the above error, as well as the following error, from time to time in my logs. While I have no proof, I’ve attributed these issues to errors or slow response from the MyQ server.

2017-12-18 18:47:51.349 [ERROR] [org.openhab.io.net.http.HttpUtil    ] - Fatal transport error: java.net.SocketTimeoutException: Read timed out
2017-12-18 18:47:51.350 [ERROR] [nhab.binding.myq.internal.MyqBinding] - Could not connect to MyQ service
java.io.IOException: Null response from MyQ server
        at org.openhab.binding.myq.internal.MyqData.request(MyqData.java:217) [225:org.openhab.binding.myq:1.11.0.201712150210]
        at org.openhab.binding.myq.internal.MyqData.getMyqData(MyqData.java:128) [225:org.openhab.binding.myq:1.11.0.201712150210]
        at org.openhab.binding.myq.internal.MyqBinding.poll(MyqBinding.java:210) [225:org.openhab.binding.myq:1.11.0.201712150210]
        at org.openhab.binding.myq.internal.MyqBinding.access$0(MyqBinding.java:202) [225:org.openhab.binding.myq:1.11.0.201712150210]
        at org.openhab.binding.myq.internal.MyqBinding$1.run(MyqBinding.java:407) [225:org.openhab.binding.myq:1.11.0.201712150210]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
        at java.lang.Thread.run(Thread.java:748) [?:?]
4

I am having the same issue on my installation. Has anyone been able to figure anything out yet in regards to this?

5

I agree with @mhilbush’s conclusion. The root cause appears to be failures in the myq service.

However, we should still address the null pointer exceptions from the binding. Does someone want to open a ticket?