Comments (17)
Unfortunately, I have no experience with Home Assistant development, so to add support for Device Actions and/or Switch Entities, is a bit above what I would like to commit to. If the chargerbase.py had support for Device Actions and/or Switch Entities, then I should be able to make an OCPP realization. Actually, to add start and stop services to the OCPP integration seem like an easier path for me...
from hass-peaq.
I'll backlog it. Myself or someone else will handle it. Aim must be agnosticity for it to be an aggregator worth developing.
Thanks for heads up again
from hass-peaq.
@andreasropel i have yet to examine the existing repo (https://github.com/lbbrhzn/ocpp), but the working process to get a new chargertype into peaqev is basically to copy paste chargeamps.py for example, and go from there. I should write up a guide on how to implement new ones for other devs.
I'd be happy to do it, but the reason as to why I haven't started is because it's very hard for me to QA the chargertypes (i've had many many rounds with easee for example since i haven't got one myself to test with) and therefore have been more focusing on general improvements as of now.
What is needed, unless we re-write a larger piece of the aggregating part that is chargertype-folder is:
- Service calls for at least on/off
- Sensor that reports the current state of the charger
- Sensor (or attribute) that reports the current wattage
- If updatemaxcurrent is gonna work, we also do require sensors/attributes for such things, plus a service-call to alter it if applicable.
Alright! Will see if I can manage to dig into the chargeamps.py and see if I can replace specific parts so they can match OCPP.
I am glad if I can help to QA the OCPP charger type since I have one myself.
from hass-peaq.
I ll start and determine where i need to alter stuff (generic for switch instead of service call) first. Made a branch just now. Will get back to you asap.
from hass-peaq.
Thanks @elden1337!
will dig into this tomorrow.
from hass-peaq.
yes please, do a pull-request.
from hass-peaq.
I checked the code a bit, and I noticed that this integration is using Services to start and stop charging. The OCPP integration does not provide that today. Instead one can either use Device Actions or a Switch Entity. Would it be reasonable for this integration to support either Device Actions or Switch Entity for controlling the charger?
from hass-peaq.
Yes, absolutely. The aggregator-part of it (for locale and chargertype) should be as low-level and type-agnostic as possible.
So we nudge it in that direction, either together with the community (faster) or in slower pace with just me coding ;).
from hass-peaq.
@elden1337 Can you please give a hint on a workaround to get OCPP working with your fantastic piece of code you have? I guess focus is not OCPP in near future..
from hass-peaq.
@andreasropel i have yet to examine the existing repo (https://github.com/lbbrhzn/ocpp), but the working process to get a new chargertype into peaqev is basically to copy paste chargeamps.py for example, and go from there. I should write up a guide on how to implement new ones for other devs.
I'd be happy to do it, but the reason as to why I haven't started is because it's very hard for me to QA the chargertypes (i've had many many rounds with easee for example since i haven't got one myself to test with) and therefore have been more focusing on general improvements as of now.
What is needed, unless we re-write a larger piece of the aggregating part that is chargertype-folder is:
- Service calls for at least on/off
- Sensor that reports the current state of the charger
- Sensor (or attribute) that reports the current wattage
- If updatemaxcurrent is gonna work, we also do require sensors/attributes for such things, plus a service-call to alter it if applicable.
from hass-peaq.
ie, no workaround possible as the types are being wired into the code specicially per chargertype. But you are right, i should get started soon-ish on this. ocpp probably brings a lot of users that are able to utilize this.
from hass-peaq.
@andreasropel i've pushed a first boilerplate for this in a separate branch. feel free to fork and continue if you wish. I've added todo's in the ocpp.py-file mainly.
from hass-peaq.
@elden1337 As I see, there is no switch for on and off. The OCPP integration has option for availability and to have the ability to controlling the box but not start and pause as Easee has. Controlling the current seems to be controlled in the same way as Easee. Not sure on how to proceed as this is not my strongest skill :)
from hass-peaq.
I'll have a think about it and continue a bit more first then. No worries
from hass-peaq.
I have edited the code a bit.
I need to test all the states to see what they say.
Shall I upload what I have done until now?
from hass-peaq.
Made some adds to the code. I guess I cannot come any further without your support now @elden1337
from hass-peaq.
if you do that, i think i can release a first alpha for you to test. the init testing then would be to just see that it loads, and if not, why, and if it loads, check that the charger will turn on/off.
from hass-peaq.
Related Issues (20)
- Create service call to alter the current peak
- Mysterious error in chargecontroller HOT 1
- Bug on dynamic caution hour getter
- If Errorstate on chargecontroller, always try to kill charging.
- Soc-service
- Ultra suave setting (peaqhvac bound)
- Add stdev to average spotprice data
- Extra stop clause
- Max min should never operate on current hour if settings arent updated
- Unable to specify power sensor during configuration HOT 9
- Add updatecurrent to zaptec HOT 1
- Refactor Zaptec setup (breaking change on their part) HOT 4
- Control 2 Easee chargers? HOT 3
- Peaks history at new year
- Kia connect (and Hyundai)
- Max min calculates wrong.
- Display star for the max-min affected hours (frontend)
- investigate issue with savingscontroller
- Emergency fallback if nordpool unavailable
- Faulty average month on 1st of month
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from hass-peaq.