MyQ (Chamberlain) LOG-Warnings


Can someone else see these warnings? Most probably it’s related to the Chamberlain-Binding (MyQ). I can see this since about 2 days:

2018-06-30 16:58:33.059 [WARN ] [he.commons.httpclient.HttpMethodBase] - Cookie rejected: "$Version=0; TS01b44c2d=01fc40691f0de6dd3f7c0e2c58fdc11b2b45e6a922df84ea1df44c47c826cad3c43784f3d0cf2296a0604190302ba4bbcef5d038acb76c8429864060353b8ae87b101100ac; $Path=/; $". Illegal domain attribute "". Domain of origin: ""
2018-06-30 16:59:33.145 [WARN ] [he.commons.httpclient.HttpMethodBase] - Cookie rejected: "$Version=0; TS01b44c2d=01fc40691f856502f47fc92df326af67a39efcc48dc411375bf1fcb34760fd1172a887f44cc4d41751aae0cced965107845b6a44e9e379cdf888f97f17cbce714bf9767b6b; $Path=/; $". Illegal domain attribute "". Domain of origin: ""


For the sake of confirmation, I just noticed the same errors in my log this morning.

I noticed the same thing yesterday night. I had to change the poll time in the config file to reduce the spam. I can still open / close the garage however.

I am seeing the same too.

Same here, although I can’t confirm when it actually started as haven’t check my logs in a while.

And since I see the error, it made me look back and see still technically a 1.x binding. So is there any plans to get the binding upgraded to a 2.0 binding and not need the external config files?

I did create an issue on Github:

Nothing technical about it. It’s a 1.x binding, full stop.

Yes, I can confirm. I am seeing them as well.

As noted in the tracking issue, this shows every evidence of being a server error not caused by OH.
Unless someone has evidence to the contrary…

Been seeing it too. Finally got fed up enough and started Googling. I’d agree – they made a server change which is trying to set an invalid cookie. Can we set the binding to ignore cookies somehow?

The warning is coming from the apache http client library, which we can’t control in the OH code. Users could eliminate the warning from the logs by either increasing the logging level for the httpclient package to FATAL, or turning it off entirely.

I should also note there are some filtering options that could potentially be used to eliminate these warnings, but I have no knowledge of using them…

Right – I saw that on the GitHub post just now.
Can you provide any guidance on how to do this? I’m not sure where the configuration file is located in the standard openhabian install.

See Rich’s excellent post on taming logging in OH2.

1 Like

@sockmeister If you are on the PI, this should take out the logs.

sudo vim /var/lib/openhab2/etc/org.ops4j.pax.logging.cfg

and add the following lines.

# Http client = org.apache.commons.httpclient.HttpMethodBase
log4j2.logger.httpclient.level = ERROR

No need to restart OH. It seems to work for me; I haven’t seen that cookie entry for 10 minutes now.

1 Like

Thank you! That’s exactly what I was looking for.
I suppose I don’t care too much for HTTPClient Warnings; Error is fine, filters out the noise!

Just checking back in; @yfaway’s fix corrected the issue for me. It simply changes the filter level of the log. That’s good enough for me, just be careful if you’re concerned with seeing HTTPClient warnings.

I am receiving those errors as well but can open both doors. I am not worried about the error, after reading these posts, what my issue is, that when I open the doors no other item is updated on the UI, can someone point me too a solution.
Thanks in advance.

Just wanted to add a bit to this as a newer OH user. I was having a lot of messages in my openhab.log from this and found this thread helpful. I was also getting a Cookie Rejected error:

2019-05-16 10:43:03.509 [WARN ] [he.commons.httpclient.HttpMethodBase] - Cookie rejected: “$Version=0; =; $Path=/; $”. Illegal domain attribute “”. Domain of origin: “

So I added this bit in my org.ops4j.pax.logging.cfg file.

log4j2.appender.out.filter.myq.type = RegexFilter
log4j2.appender.out.filter.myq.regex = .(
log4j2.appender.out.filter.myq.onMatch = DENY
log4j2.appender.out.filter.myq.onMisMatch = ACCEPT

That took care of the rest of that last message for me.