-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
OpenEVSE defaults not working #22
Comments
Hi, it was added as a test and the card is still a release candidate. I depend on someone with EVSE charger to debug and propose template values or I'll have to remove it (bevause I have no clue how it looks). The card is now fully customizable (even if you have selected a template, it can be modified). So it should be easy to fool around with different settings without knowing code. |
I'm able to test it out, just need some pointers. |
Sounds good. I think the easiest way is if you read up on the readme, see especially the 'advanced' part. This will explain what is possible to customize today. Then you could go to the card config, but remember to select 'Show code editor' so that the card config is shown in YAML. Even if the EVSE-setup doesn't work today, you should be able to use it as a template to get you started. I think it should also work if you select Easee as template and then start modifying sensors to what you have in your installation. I could have left the card only with the possibility to edit manually, but since I know this is not always the best for non-advanced YAML'ers, the idea I have with these templates is that by knowing the basic structure of each integration, we can make it a bit easier for people in the future. However, this requires that someone gives input on each integration. Try it out and see if you get a hold of it. If you struggle with something specific, I can try to give some advice. Also, if you want, you could post a complete list of the entities/sensors belonging to the EVSE integration and I can try to make something as a starting point. |
I haven't migrated yet to the new rewritten card, but what I have quickly looked in the code makes sense. I am using @firstof9 integration, so it should work. But please make sure that you have the default "sensor.openevse_charging_status" as you're defining in the config, as the code will rip the _charging_status part to get the 'openevse' string. If you've named it differently, then you have to pass that sensor to the config. |
That's right, the card is using the main sensor to figure out (best guess) the rest of the sensors. But if someone has completely renamed it, the card should work anyway, but will rely on manual configuration of course. |
Does my card config look right? |
Well, not really. Once openESVE is selected together with a main entity it should "translate" the config to something like the below example. Could be more or could be less (I think less, we didn't put to much info in the openEVSE example which is just a work-in-progress). Try to select Easee and modify the example below, or perhaps easier to copy the example and modify it manually to fit your sensors. What the card does when selecting a brand and a main entity is to (try to) figure out CHARGERNAME and replace it in sensornames. So if you send a list of your entities, I can try to update openEVSE to fit more what is there. PS! The example may look overwhelming, and you don't need all of it. But if you study, I think you see the structure more or less. The readme should hopefully explain more or less what each detail means too.
|
These are my sensors openevse Sleep Mode openevse_Ambient Temperature openevse_Charge Time Elapsed openevse_Charging Current openevse_Charging Status openevse_Charging Voltage openevse_Controller Firmware openevse_Current Capacity openevse_Current Power Usage openevse_Divert Active openevse_Divert Mode openevse_ESP32 Temperature openevse_Ethernet Connected openevse_IR Temperature openevse_Manual Override openevse_Max Amps openevse_Min Amps openevse_OTA Update openevse_Protocol Version openevse_PV Available Current openevse_PV Charge Rate openevse_PV Smoothed Available Current openevse_RTC Temperature openevse_Sensor Scale openevse_Service Level openevse_Station Status openevse_Total Usage openevse_Usage this Session openevse_Vehicle Connected openevse_Wifi Fimrware Version openevse_Wifi Signal Strength |
So I came up with something like this: type: custom:charger-card
entity: sensor.openevse_charging_status
brand: openevse
details:
status:
entity_id: sensor.openevse_charging_status
substatus:
entity_id: sensor.openevse_station_status
currentlimits:
- 0
- 10
- 12
- 25
- 30
- 32
- 48
statetext:
disconnected: not connected
awaiting_start: sleeping
completed: connected
charging: charging
collapsiblebuttons:
group1:
text: Set Limits
icon: mdi:speedometer
group2:
text: Firmware
icon: mdi:information
group3:
text: Configuration
icon: mdi:cog
info_left:
- entity_id: sensor.openevse_wifi_signal_strength
text: online
info_right:
- entity_id: sensor.openevse_charging_voltage
text: Voltage
unit_show: true
- entity_id: sensor.openevse_charging_current
text: Charging Current
unit_show: true
- entity_id: sensor.openevse_current_power_usage
text: Power
unit_show: true
group1:
- entity_id: sensor.openevse_max_amps
text: Max Amps
group2:
- entity_id: sensor.openevse_wifi_fimrware_version
text: Firmware Version
group3:
- entity_id: switch.openevse_manual_override
text: Manual Override
stats:
default:
- entity_id: sensor.openevse_usage_this_session
text: Session Energy
unit_show: true
- entity_id: sensor.openevse_total_usage
text: Lifetime Energy
unit_show: true
- entity_id: sensor.openevse_charge_time_elapsed
text: Charge Time
unit_show: true
disconnected:
- entity_id: sensor.openevse_usage_this_session
text: Session Energy
unit_show: true
- entity_id: sensor.openevse_total_usage
text: Lifetime Energy
unit_show: true
- entity_id: sensor.openevse_charge_time_elapsed
text: Charge Time
unit_show: true
awaiting_start:
- entity_id: sensor.openevse_usage_this_session
text: Session Energy
unit_show: true
- entity_id: sensor.openevse_total_usage
text: Lifetime Energy
unit_show: true
- entity_id: sensor.openevse_charge_time_elapsed
text: Charge Time
unit_show: true
charging:
- entity_id: select.openevse_max_current
text: Current Limit
unit_show: true
completed:
- entity_id: sensor.openevse_usage_this_session
text: Session Energy
unit_show: true
- entity_id: sensor.openevse_total_usage
text: Lifetime Energy
unit_show: true
- entity_id: sensor.openevse_charge_time_elapsed
text: Charge Time
unit_show: true
error:
- entity_id: sensor.openevse_usage_this_session
text: Session Energy
unit_show: true
- entity_id: sensor.openevse_total_usage
text: Lifetime Energy
unit_show: true
- entity_id: sensor.openevse_charge_time_elapsed
text: Charge Time
unit_show: true
ready_to_charge:
- entity_id: sensor.openevse_usage_this_session
text: Session Energy
unit_show: true
- entity_id: sensor.openevse_total_usage
text: Lifetime Energy
unit_show: true
- entity_id: sensor.openevse_charge_time_elapsed
text: Charge Time
unit_show: true
toolbar_left:
default:
- {}
disconnected:
- {}
awaiting_start:
- service: switch.turn_off
service_data:
target:
entity_id: switch.openevse_manual_override
text: stop
icon: hass:stop
- service: switch.turn_on
service_data:
target:
entity_id: switch.openevse_manual_override
text: start
icon: hass:play
charging:
- service: switch.turn_off
service_data:
target:
entity_id: switch.openevse_manual_override
text: stop
icon: hass:stop
completed:
- {}
error:
- {}
ready_to_charge:
- {}
Here's the output: |
Starting to look good! I am aware of the glitch you see in current selection dropdown, there is a problem in my css that I didn't manage to fix yet. See #21 as well. PS! You would probably want to add a service to the current selection too so that you can actually change it? |
I've made a few tweaks that may work as defaults: type: custom:charger-card
entity: sensor.openevse_charging_status
brand: openevse
customCardTheme: theme_custom
details:
status:
entity_id: sensor.openevse_charging_status
substatus:
entity_id: sensor.openevse_station_status
currentlimits:
- 6
- 10
- 12
- 25
- 30
- 32
- 48
statetext:
awaiting_start: sleeping
completed: connected
charging: charging
collapsiblebuttons:
group1:
text: Set Limits
icon: mdi:speedometer
group2:
text: Firmware
icon: mdi:information
group3:
text: Configuration
icon: mdi:cog
info_left:
- entity_id: sensor.openevse_wifi_signal_strength
text: online
info_right:
- entity_id: sensor.openevse_charging_voltage
text: Voltage
unit_show: true
- entity_id: sensor.openevse_charging_current
text: Charging Current
unit_show: true
- entity_id: sensor.openevse_current_power_usage
text: Power
unit_show: true
group1:
- entity_id: select.openevse_max_current
text: Max Amps
icon: mdi:sine-wave
service: select.select_option
service_data:
option: '#SERVICEVAL#'
group2:
- entity_id: sensor.openevse_wifi_fimrware_version
text: Firmware Version
- entity_id: sensor.openevse_controller_firmware
text: Controller Firmware
group3:
- entity_id: select.openevse_service_level
icon: mdi:leaf
text: Service Level
stats:
default:
- entity_id: sensor.openevse_ambient_temperature
text: Ambient Temp
unit_show: true
- entity_id: sensor.openevse_total_usage
text: Lifetime Energy
unit_show: true
- entity_id: sensor.openevse_charge_time_elapsed
text: Charge Time
unit_show: true
awaiting_start:
- entity_id: select.openevse_max_current
text: Current Limit
unit_show: true
- entity_id: sensor.openevse_total_usage
text: Lifetime Energy
unit_show: true
- entity_id: sensor.openevse_ambient_temperature
text: Ambient Temp
unit_show: true
charging:
- entity_id: select.openevse_max_current
text: Current Limit
unit_show: true
- entity_id: sensor.openevse_esp32_temperature
text: Station Temp
unit_show: true
completed:
- entity_id: sensor.openevse_usage_this_session
text: Session Energy
unit_show: true
- entity_id: sensor.openevse_total_usage
text: Lifetime Energy
unit_show: true
- entity_id: sensor.openevse_charge_time_elapsed
text: Charge Time
unit_show: true
error:
- entity_id: sensor.openevse_esp32_temperature
text: Station Temp
unit_show: true
- entity_id: sensor.openevse_ambient_temperature
text: Ambient Temp
unit_show: true
- entity_id: select.openevse_max_current
text: Current Limit
unit_show: true
toolbar_left:
awaiting_start:
- service: switch.turn_off
service_data:
target:
entity_id: switch.openevse_manual_override
text: stop
icon: hass:stop
- service: switch.turn_on
service_data:
target:
entity_id: switch.openevse_manual_override
text: start
icon: hass:play
charging:
- service: switch.turn_off
service_data:
target:
entity_id: switch.openevse_manual_override
text: stop
icon: hass:stop |
Looking good! Does it seem to work as you expected? @jcsogo: Does this cover your needs and expectation as well? If you both I agree, I can update the openEVSE template to reflect this solution. |
@tmjo I couldn't get the "disconnected" state using the "not connected" sensor state to work it always used "default" for some reason. |
Sorry, I didn't follow. You mean the state text below the charger image doesn't follow your sensor.openevse_charging_status? |
When I hope this clears up what I was trying to convey. |
Has the openEVSE template been updated? |
No idea, I've been using what I've posted and it's been working fine. |
Hi! I'd love to add support for this charger, but kindly read the wiki on how-to. Let me know if anything is unclear and I'll update it or try to explain. Cheers! |
When using
brand
set toopenevse
the card doesn't display any data except the charger status.Card config:
The text was updated successfully, but these errors were encountered: