@Jumpingtrees Please hlep me calculate. I really dont know which price you expect here.
153.18 EUR/MWh, shold be 0,15318 EUR/kWh, which is 15,3 cents/kWh, right ?
@bwa Yes. This is seems to be correct. The difficulty is and maybe should be somewhere noted, that these prices have nothing to do with end customer prices in Germany as e.g. taxes are not included.
Hi. There is no way to set âbattery capacityâ with flow?
I need this because I have to different cars
@arovik No, but it should be easy to add that option. Will look into it
@arovik Remeber that yo may also create multiple devices to hold this
@arovik You migth try the v2.2.0 from test
Nice 
but Iâm still not able to get the app to work. Charging will not work when charge controller is active. a plan is created and things look ok, but the charging never starts
The charger goes to âcar connectedâ and does not start, but I found out that if i press the lock button on the key it will start charging. Looks like the car needs to be waked up. Itâs a Skoda enyaq
Look more like a car and easee issue.
But there is several modes to utilize here. read this : Homey Easy Charge Controller Homepage - Homey Easy Charger - Confluence
If you use the local scheduler the charger is always on, but different schedules are sent to the charger, you may try that stategy ?
Im not sure what that script actually does , or try to do. I think that might be a unintentional copy paste from @bwa 
?
Could you try and check if this does the job for you @arovik ?
const devices = await Homey.devices.getDevices(); // Retrieve all devices
const evChargerDeviceIds = [];
// Loop through the devices and filter based on class
for (const [id, device] of Object.entries(devices)) {
if (device.class === 'evcharger') {
// Collect the device name and ID
evChargerDeviceIds.push({
id: device.id,
name: device.name
});
}
}
// Log the result
if (evChargerDeviceIds.length > 0) {
log('EV chargers found:');
evChargerDeviceIds.forEach(device => log(`${device.name} - ID: ${device.id}`));
} else {
log('No EV chargers found.');
}
thanks but I found the ID in homey developer tools None of the scripts on the wiki works. I took the script from another person on the Facebook page
1 Like
I will try to help, but is very busy at work for this and next week
Seems like there is a bug when you have 2 chargers (easse in my case) and 2 seperate controllers (one for each charger). I have posted same question about âhow is a new plan triggeredâ in the norwegian FB group, but this might be a âbugâ, since I (figured out) can now trigger the first charger with âresumeâ ECC card, but it only seems to affect the first charger, even its the other charger that sends the resume.
Screenshot shows that when I resume controller for charger B, but its creating new plan for charger A (as you can see the naming doesnât match). If I try resume ECC for charger A it also creating new plan for charger A:
My workaround has been to complete restart the ECC app on certain time of the day, when I know its soon time to charge both cars. As you can see in this screenshot both chargers then get new plans after restarting app, like it should be:
Donât know if this is only me, but I noticed that when I pause âPause ECCâ or resume âResumes ECCâ ECC using a flow card, the trigger âController was pausedâ or âController has resumed operationsâ is not triggered.
I am using such a setup to update a display independent from the way how ECC was paused or resumed.
execute the operation and send a diag after that, and I can see if someting strange is logging
@Jumpingtrees
Iâm seeing a lot of errors reporting in from onOffChanged, and that may be your issue. So check your devices. This is aprox one hours ago
Stack trace
Error: Not Found: Device with ID ee50c0f7-d8b3-40ab-a383-4f28d2c442c3
at Remote Process
at HomeyClient.emit (/node_modules/@athombv/homey-apps-sdk-v3/lib/HomeyClient.js:44:23)
at Object.emit (/node_modules/@athombv/homey-apps-sdk-v3/manager/drivers.js:78:54)
at Object.emit (/node_modules/@athombv/homey-apps-sdk-v3/lib/Driver.js:126:50)
at /node_modules/@athombv/homey-apps-sdk-v3/lib/Device.js:570:27
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at ChargeControllerDevice.setCapabilityValue (/node_modules/@athombv/homey-apps-sdk-v3/lib/Device.js:562:23)
at Utils.emptyAllChargingHours (/app/drivers/controller/utils.js:1117:26)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Utils.updateMeasureChargingHours (/app/drivers/controller/utils.js:1123:9)
at async onOffChanged (/app/drivers/controller/capabilityactions.js:339:17)
I have released a new version that will log devicenames and device idâs. That may help if someting is wrong or odd with the device id
Hi, Could you please share the script that works? I cannot get the script to work either unfortunately. Was able to get the Easee charger ID from the script made by Torstein above
Hi,
I am trying to create a local easee schedule from the script as was given in the documentation website. However I get an error when trying to run the script from a flow. I have been trying to troubleshoot, but unable to find out what is not working,
I am running this script:
try {
console.log(âcreateEaseeChargerSchedule argsâ, args);
const obj = JSON.parse(args);
await Homey.flow.runFlowCardAction({
uri: âhomey:device:98e4c17c-0860-465d-85c8-d492924d725bâ,
id: âcreateScheduleâ,
args: {
âstartTimeâ: ââ+obj.start,
âendTimeâ: ââ+obj.stop,
ârepeatâ: true
}
});
} catch (err) {
throw Error(âError occured with createEaseeChargerSchedule : " + err + " args: 'â + args + â'â);
}
with a flow that looks like this:
I have also tried to input start and stop times directly in the script as agruments, but that does not work either. Not sure what I am doing wrong.
Help is much appreciated
