first version that can control current locally without enelx servers

[ivanfmartinez]

Not for merging now, but others can start testing to see and give feedback

• It works for setting maximum current to be used on my device which used version 09u

  • we need to see on other versions if the size of command is correct

• Putting 0 in Max Charging Current parameter pauses the charging

  • when the charging is paused the device reset the session energy value
  • if juicebox lost connection with server (or proxy when acting as server) it will cancel the pause and return charging

• The base message code comes from https://github.com/philipkocanda/juicebox-protocol

• There are more information about commands on https://github.com/snicker/juicepassproxy/issues/39

• Maybe the changing can fail if the command is sent when a message arrive from the juicebox overriding the value

  • some synchronization can be made for this case

[ivanfmartinez]

Working to control the charging current based on solar power availability

[ivanfmartinez]

Sample HA automation to Pause/Start charging, working fine in my environment, in my case I resume with 12 amps and other automation that controls current by solar will take place to control.

In my case the minumum value must be 11 because the Bolt use a different behaviour when thinks that are connected to a portable chager when value is 10 or lower.

I dont know if this kind of sample can go on README or we must have a different file for information about this.

alias: EVSE - Enable / Pause Charging by schedule
description: ""
trigger:
  - platform: state
    entity_id:
      - schedule.horario_carregamento_evse
condition: []
action:
  - choose:
      - conditions:
          - condition: and
            conditions:
              - condition: state
                entity_id: schedule.horario_carregamento_evse
                state: "on"
              - condition: numeric_state
                entity_id: number.juicebox_max_charging_current
                below: "1"
        sequence:
          - service: number.set_value
            metadata: {}
            data:
              value: "12"
            target:
              entity_id: number.juicebox_max_charging_current
      - conditions:
          - condition: and
            conditions:
              - condition: state
                entity_id: schedule.horario_carregamento_evse
                state: "off"
              - condition: numeric_state
                entity_id: number.juicebox_max_charging_current
                above: 1
        sequence:
          - service: number.set_value
            metadata: {}
            data:
              value: "0"
            target:
              entity_id: number.juicebox_max_charging_current
mode: single

[ivanfmartinez]

Energy session reset on pause

[markgergely]

do you have a docker tag with these changes? id love to test this as i have a similar usecase to yours

[ivanfmartinez]

@markgergely

do you have a docker tag with these changes? id love to test this as i have a similar usecase to yours

I dont have the environment to build and publish this docker containers, I'm just using -volumes on my docker-compose to override the files.

Maybe @Snuffy2 can create a tag like the async branch.

Here is my docker-compose.override.yaml file

services:
  juicepassproxy_tst:
    volumes:
      - ./tests/juicepassproxy.py:/juicepassproxy/juicepassproxy.py:ro
      - ./tests/juicebox_mqtthandler.py:/juicepassproxy/juicebox_mqtthandler.py
      - ./tests/juicebox_checksum.py:/juicepassproxy/juicebox_checksum.py
      - ./tests/juicebox_exceptions.py:/juicepassproxy/juicebox_exceptions.py
      - ./tests/juicebox_message.py:/juicepassproxy/juicebox_message.py
      - ./tests/juicebox_mitm.py:/juicepassproxy/juicebox_mitm.py

[Snuffy2]

Sure, I can get it into an alternate docker tag. Is it to a point where it is ready for others who are interested to start testing it?

[Snuffy2]

image: ghcr.io/snicker/juicepassproxy:juicebox_commands

[markgergely]

thanks for the quick turnaround, I am already running it, will report back

[ivanfmartinez]

Sure, I can get it into an alternate docker tag. Is it to a point where it is ready for others who are interested to start testing it?

It's working fine in my environment very stable. Sure others can test, but we need to decide if I went to correct direction.

After more people test, with more firmware versions, we will know if the JuiceboxMessage class works for other versions and that code can be used to replace the current parsing of messages.