JPP repeatedly crashing on invalid temperature #115
Comments
|
The Enel X Way app reports model 2JBO401RNA |
|
I turned on |
|
Fascinating... Does that mean that JuiceBox pushed an update to my device after the company was shut down? (it was last working on November 7th) What is the current status of that branch? Does it have current documentation? If I understand correctly, it uses the same setup as the base image, but requires option C (redirect UDP at the router level)? |
|
A friend in Brazil also received yesterday that change, they are not updating the device but sending a different configuration. The branch is working, all information is on the #69 . Should works like main with all options. I dont use ENEL X servers for months. |
|
Option C is not required. I do option A. I block ALL internet traffic to the JB. My JB then fails to contact the directory service and it defaults to using jbv1.emotorwerks.com on port 8042. I set up a local DNS override to return my local JPP IP for jbv1.emotorwerks.com. Voila. juicebox_commands branch made it really easy for me. |
|
I switched my Docker image to pull from Do I need to set |
|
I don't believe the latest docker image has the latest code. Check out the 6th (and 1st) posts in #69 for instructions for overriding files with the latest. (Also, take care as some file names seem to have changed since the post was originally posted.) |
|
The images in my docker repository are updated first message of #69 was updated with the correct address, I dont known if niharmeta or others are updated. The juicebox needs to be restarted without internet connection to work to return to unencrypted mode. I will check later if I can do better checking when device sends the encrypted messages to dont generate exceptions. |
|
Just made a new commit with the procedure and workaround to dont get this errors when JPP receives encrypted messages : Updated my docker images |
|
Updated my docker image as well for x86 as well as arm users (Pi) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From the logs:
And the
Car Charger Statusentity in HA readsunknown S\x13\xe3\x04\xbc\xec\x08\xb7(the exact value changes every 2-3 hours).For a few days before that, it was not reporting when I plugged in my car.
The text was updated successfully, but these errors were encountered: