-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hass-cli state history ENTITY
fails with bad escape \d at position 7
#394
Comments
same here : |
same issue here too
|
If you installed with homebrew: The following worked for me, for now...
|
Has someone found out more on this ? Still same error on hass-cli version: 0.9.7 when invoked like |
ok, so I figured it out ... the websocket response to to large for the default max of the library... I've put together a PR here but I am having trouble getting the tests to pass... If you want to install my branch you will just need to add an env var to increase the max websocket response. The default seems to be 4mb and I got it working when I went to 5mb |
This is because of some regex behavior change introduced in regex 2022.3.15, which breaks dateparser: dateparser >= 1.1.4 should be fixed but unfortunately homeassistant-cli locks dateparser at (>=0.7.1,<0.8): The dev-Branch lifts that restriction but unfortunately there is no released version yet. |
@leo-b odd... I'm curious how my max payload size fix for websockets was able to get around this issue then? I ask because I've been using my fork for a while now with zero reocurance of the issue since my "fix" .... Possible we might have been having similar but different issues? |
On macOS, if you install via pipx ( |
Just ran into the same issue. $ pip3 uninstall dateparser -y
$ pip install "dateparser>=1.2.0" Edit: it seems that this d4e2312 commit fixed the incorrect |
p.s. if you run into this issue, you'll probably also run into the issue that my unaccepted PR #418 also addresses. At the moment |
Running a
hass-cli state history ENTITY
command for any entity fails:I ran it with the
-x
option as suggested:I've had no issues running basically any other command (the tool is great!).
hass-cli version: 0.9.4
hass core version: 2022.12.1
The text was updated successfully, but these errors were encountered: