rasssta

Example data from my installation: Users: `{"isOwner":true,"siteUsers":[{"userId":,"email":"","name":"","phoneNumber":"","userRole":1},{"userId":,"email":"","name":"","phoneNumber":"","userRole":2}]}` Consumption for user 1: `[{"year":2021,"month":7,"totalEnergyUsage":68.873278},{"year":2021,"month":8,"totalEnergyUsage":79.796578},{"year":2021,"month":9,"totalEnergyUsage":33.639319},{"year":2021,"month":10,"totalEnergyUsage":17.445987},{"year":2022,"month":1,"totalEnergyUsage":24.233064}]` For the yearly command the result is: `[{"year":2021,"totalEnergyUsage":199.755162},{"year":2022,"totalEnergyUsage":24.233064}]`

Yeah, almost. My data for those cmds: https://api.easee.cloud/api/sessions/charger/{chargerId}/monthly `[{"year":2020,"month":11,"totalEnergyUsage":0.210707,"totalCost":0.0,"currencyId":"NOK"},{"year":2020,"month":12,"totalEnergyUsage":0.185231,"totalCost":0.0,"currencyId":"NOK"},{"year":2021,"month":2,"totalEnergyUsage":13.810430000000002,"totalCost":15.8819945,"currencyId":"SEK"},{"year":2021,"month":5,"totalEnergyUsage":39.567758,"totalCost":49.4596975,"currencyId":"SEK"},{"year":2021,"month":6,"totalEnergyUsage":51.836552,"totalCost":64.79569,"currencyId":"SEK"},{"year":2021,"month":7,"totalEnergyUsage":125.592364,"totalCost":156.990455,"currencyId":"SEK"},{"year":2021,"month":8,"totalEnergyUsage":120.28828300000002,"totalCost":150.36035375,"currencyId":"SEK"},{"year":2021,"month":9,"totalEnergyUsage":47.52681,"totalCost":59.4085125,"currencyId":"SEK"},{"year":2021,"month":10,"totalEnergyUsage":17.445987,"totalCost":27.442537551,"currencyId":"SEK"},{"year":2022,"month":1,"totalEnergyUsage":24.233064,"totalCost":38.118609672,"currencyId":"SEK"}]` I think I, by mistake, had it set to NOK instead of SEK in the beginning hence the crap data above....

@tijunoi : Do you have S5 or S5 Max? I have S5 with .2008 and just tried get_room_mapping and got: > INFO Device found, making call INFO Got result: []

Should really be merged ASAP as attribute naming inconsistency problems just gets bigger the longer it takes (=the more people using it and will have stuff break when it changes)

I have the same issue. I tried the workaround by re-downloading master and restarting twice but that didn't work. The proper way to handle new features is by releasing a...

I'm using the main version. Not sure who the question was directed to? :)

Same issue for me

Re-created the app, but selected "Accounts in any organization directory" instead of "Personal account" - worked.

I'm having the same issue with 10.16.3 :/

Hi, sorry for the late reply, my Easee isn't located at my permanent residence so takes some "calendar time" to test stuff this time of the year :-) Unfortunately I...