Giter Club home page Giter Club logo

home-assistant-garo-chargebox's People

Contributors

endor-force avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

Forkers

grinco

home-assistant-garo-chargebox's Issues

A few comments

This applies to software version 1.3.1.

I think that the best way to get the explicit status from the charger is by using "chargeStatus". This is an integer in the json response but the Garo GUI decodes it as a hex value (in index.jsp) according to the function/switch below. I've also attached the function used to display the LED representation in the Garo GUI.

`charging.status.notconnected = Fordon ej anslutet
charging.status.connected = Väntar på startsignal från bil
charging.status.charging = Laddning pågår
charging.status.wait = Laddare initieras...
charging.status.rcdfault = Skyddbrytare utlöst
charging.status.chargecancelled = Laddning avbruten
charging.status.chargepaused = Laddning pausad av lastbalanseringssystem
charging.status.chargefinished = Laddning avslutad av bil
charging.status.overheat = Övertemperatur, laddning tillfälligt begränsad till 6A
charging.status.criticaltemperature = Övertemperatur, laddning avbruten
charging.status.lockingfault = Eluttag kan ej låsas
charging.status.contactorfault = Kontaktorfel
charging.status.ventfault = Ventilation krävs
charging.status.cablefault = Felaktig kabel
charging.status.generalfault = Kommunikationsfel
charging.sessionAccumulatedEnergy= Laddat sedan fordon anslöts

charging.status.notconnected = Vehicle not connected
charging.status.connected = Waiting for startsignal from car
charging.status.charging = Charging
charging.status.wait = Initialization...
charging.status.rcdfault = RCD fault
charging.status.chargecancelled = Charging cancelled
charging.status.chargepaused = Charge process paused by loadbalancing system
charging.status.chargefinished = Charging ended by car
charging.status.overheat = Overtemperature, charging temporarily restricted to 6A
charging.status.criticaltemperature = Overtemperature, charging cancelled
charging.status.lockingfault = Lock fault
charging.status.contactorfault = Contactor fault
charging.status.ventfault = Ventilation required
charging.status.cablefault = Cable fault
charging.status.generalfault = Communication error
charging.sessionAccumulatedEnergy= Charged since connected

function chargeCodeToText(status)
{
	switch(status)
	{
		case 0x00:
		case 0x10:
			return "<fmt:message key="charging.status.notconnected" />";
			break;
		case 0x30:
			return "<fmt:message key="charging.status.connected" />&nbsp;<a href='javascript:openChargePauseHelp()'>?</a>";
			break;
		case 0x40:
			return "<fmt:message key="charging.status.charging" />";
			break;
		case 0x42:
			return "<fmt:message key="charging.status.chargepaused" />";
			break;
		case 0x50:
			return "<fmt:message key="charging.status.chargefinished" />&nbsp;<a href='javascript:openChargePauseHelp()'>?</a>";
			break;
		case 0x60:
			return "<fmt:message key="charging.status.chargecancelled" />";
			break;
		case 0x70:
			return "<fmt:message key="charging.status.overheat" />";
			break;
		case 0x80:
			return "<fmt:message key="charging.status.criticaltemperature" />";
			break;
		case 0x90:
			return "<fmt:message key="charging.status.unavailable" />";
			break;
		case 0x91:
			return "<fmt:message key="charging.status.reserved" />";
			break;
		case 0x95:
			return "<fmt:message key="charging.status.dcfault" />";
			break;
		case 0x96:
			return "<fmt:message key="charging.status.dchardwarefault" />";
			break;
		case 0x9A:
			return "<fmt:message key="charging.status.cpfault" />";
			break;
		case 0x9B:
			return "<fmt:message key="charging.status.cpshorted" />";
			break;
		case 0x9C:
			return "<fmt:message key="charging.status.remotedisabled" />";
			break;
		case 0x9D:
			return "<fmt:message key="charging.status.dlmfault" />";
			break;
		case 0xA0:
			return "<fmt:message key="charging.status.cablefault" />";
			break;
		case 0xA1:
		case 0xA2:
			return "<fmt:message key="charging.status.lockingfault" />";
			break;
		case 0xA3:
		case 0xA4:
			return "<fmt:message key="charging.status.contactorfault" />";
			break;
		case 0xA8:
			return "<fmt:message key="charging.status.rcdfault" />";
			break;
		case 0xF0:
			return "<fmt:message key="charging.status.wait" />";
			break;
		case 0xF1:
			return "<fmt:message key="charging.status.ventfault" />";
			break;
		default:
			return "<fmt:message key="charging.status.generalfault" />";
	}
}
function chargeCodeToIndication(status)
{
	switch(status)
	{
		case 0x00:
		case 0x10:
			return "G";
			break;
		case 0x30:
			return "G";
			break;
		case 0x40:
			return "B";
			break;
		case 0x42:
			return "G";
			break;
		case 0x50:
			return "G";
			break;
		case 0x60:
			return "G";
			break;
		case 0x70:
			return "B";
			break;
		case 0x80:
			return "P";
			break;
		case 0x90:
			return "B";
			break;
		case 0x91:
			return "W";
			break;
		case 0x95:
			return "R";
			break;
		case 0x9A:
			return "R";
			break;
		case 0x9B:
			return "R";
			break;
		case 0x9C:
			return "B";
			break;
		case 0xA0:
			return "Y";
			break;
		case 0xA1:
		case 0xA2:
			return "Y";
			break;
		case 0xA3:
		case 0xA4:
			return "R";
			break;
		case 0xA8:
			return "R";
			break;
		case 0xF0:
			return "G";
			break;
		case 0xF1:
			return "R";
			break;
		default:
			return "R";
	}
}`

IT also seems that a few more "connector" possibilities has been added to recent software versions.

Garo GLB+?

Hi!
Is this integration also compatible with the OCPP controlled Garo GLB+ charger? (This charger lacks a user interface and is only controlled through OCPP).
Thanks // Marcus

Can't get the switch for "mode setting" to work

Thank's for a nice tool set in order to avoid the Garo integration which seems to no longer being maintained!

However, I have problems to get the mode switch working.

First question is if there is a typo in the Readme. A bit down in the code for switch you have written:
command_state: '/usr/bin/curl -X GET http://192.168.xxx.yyy:2222/rest/chargebox/status'
But I assume also this line should change the url to:
command_state: '/usr/bin/curl -X GET http://192.168.xxx.yyy:8080/servlet/rest/chargebox/status'

But after correcting this, I still can't get the switch to work. Have you tried it with the Garo FW 1.3.1?

/Kenneth

Failed to restart Home Assistant

Failed to restart Home Assistant
The system cannot restart because the configuration is not valid: Error loading /config/configuration.yaml: in "/config/configuration.yaml", line 23, column 23: Unable to read file /config/garo_chargebox/pkg_garo_chargebox.yaml.
i get this error if i add this text to /config/configuration.yaml
can you help me ?

homeassistant:

packages:

  ### GARO CHARGEBOX ###
  garo_chargebox: !include garo_chargebox/pkg_garo_chargebox.yaml

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.