Skip to content
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

Commands not working (Error code 400) #15

Closed
pottio opened this issue Apr 28, 2022 · 0 comments · Fixed by #16
Closed

Commands not working (Error code 400) #15

pottio opened this issue Apr 28, 2022 · 0 comments · Fixed by #16
Assignees
Labels
bug Something isn't working

Comments

@pottio
Copy link
Owner

pottio commented Apr 28, 2022

Describe the bug
Calling commands like resetting the meter values results in error.

To Reproduce
Steps to reproduce the behavior:

  1. Go to objects > warp.0.meter.reset
  2. Set value for reset to true
  3. Meter values are not reset + error result in protocol

Expected behavior
No error in protocol + meter values in WARP should be resetted.

Screenshots & Logfiles

target time level message
warp.0 2022-04-28 19:57:24.257 error [WarpClient] Sending message to WARP charger failed | Error=Error: Request failed with status code 400
warp.0 2022-04-28 19:57:24.212 debug [WarpClient] PUT: http://192.168.150.27/meter/reset
warp.0 2022-04-28 19:57:24.211 info [WarpClient] Send message to WARP charger

Versions:

  • Adapter version: 1.0.0
  • JS-Controller version: 4.0.21
  • Node version: 14.19.1
  • Operating system: linux (docker)
@pottio pottio added the bug Something isn't working label Apr 28, 2022
@pottio pottio self-assigned this Apr 28, 2022
@pottio pottio linked a pull request Apr 28, 2022 that will close this issue
pottio added a commit that referenced this issue Apr 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant