oh2th / com.go-e.charger Goto Github PK

Hi!

is there a chance or plan to extend the app for Fronius wattpilot?
Since there is Nieder-Olm communication for 11kw wallbox it wld be great to sync my car (Audi, already exists) with the wallbox
Cheers a thx
Oli

Verify / Translate "de" objects in translations-directory.

Please refer to this key:

e3c215c6-4143-4d10-a60f-befa2aa3d647

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.
I check if my car is charging with the AND-card. When it charges, the AND-statement returns 'false. When the car isn't charging, the AND-card 'is charging' returns true.

Screenshots
If applicable, add screenshots to help explain your problem.

App (please complete the following information):

• Test or Live version: [e.g. Test] Live version
• Installed version: [e.g. 2.2.2] 2.7.2

Desktop (please complete the following information):

• OS: [e.g. iOS] Windows 11
• Browser [e.g. chrome, safari] Chrome
• Version [e.g. 22] Latest

Smartphone (please complete the following information):

• Device: [e.g. iPhone6] Android 13
• OS: [e.g. iOS8.1] Android
• Browser [e.g. stock browser, safari] Chrome
• Version [e.g. 22] 13

Additional context
Add any other context about the problem here.

Switch from V1 mqtt set queries to V2 api/set queries for devices that support API v2.

• Set amperage http://1.2.3.4/api/set?amp=(6-32)
• Allow/ disallow charging http://1.2.3.4/api/set?alw=(0|1)

Changing between single phase and all phases charging has been suggested

• set 1-phase - http://1.2.3.4/api/set?psm=1
• set 3-phase - http://1.2.3.4/api/set?psm=2

https://community.homey.app/t/app-pro-go-e-charger-electric-car-charger/14162/78

          Hallo Tapio,

Thanks for the fix again, appreciated! I’ve got another one, not about the electric current, but voltage. For single phase charging sessions, the go-e charger homey app adds up all available voltages provided by the Go-E charger. That would be something like 700 to 710V, which is odd. See the screenshot of the Go-e charger app in Homey. Voltage in single phase should be in the range of about 225-240V. I think this can be solved by retrieving the phase (L1,L2 or L3) where there is (or was in previous charging sessin) a electric current present.

For charging at three phases, 700-710V is not corrent either. It is a bit more complicated to get it right, it should typically be in the range of about 380-410V. A suggestion how to fix it: You can roughly calculate the correct voltage by mutliplying an active single phase by the square root of 3 (approximately 1,73). As an example:

234V * 1,73 = 405V (L1-phase)

When there are three phase active, you can take roughly calculate the mean of the three voltages and multiply it by 1,73. As an example the voltages in the screenshot of the original android Go-E charger app:

((234V+239+239)/3 ) * 1,73 = 410,6V.

Can the voltages in your go-e charger homey app be fixed for sinlge and three phases charging?

Thanks,

Norbert

Van: Tapio Heiskanen @.>
Verzonden: maandag 4 december 2023 05:30
Aan: oh2th/com.go-e.charger @.>
CC: NCVervaet @.>; Author @.>
Onderwerp: Re: [oh2th/com.go-e.charger] Electric current - 1 phase (Issue #25)

Closed #25 #25 as completed via #26 #26 .

—
Reply to this email directly, view it on GitHub #25 (comment) , or unsubscribe https://github.com/notifications/unsubscribe-auth/AP6KB36XP2VDUUCBKD7S2XTYHVGTDAVCNFSM6AAAAAA7ZGN3L6VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGEZTGOJTGQ2TAOA .
You are receiving this because you authored the thread. https://github.com/notifications/beacon/AP6KB33DSSCC2ZDGSYYZYUTYHVGTDA5CNFSM6AAAAAA7ZGN3L6WGG33NNVSW45C7OR4XAZNWJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XKUY3PNVWWK3TUL5UWJTYAAAAAFF5CLOWA.gif Message ID: @.*** @.***> >

Originally posted by @NCVervaet in #25 (comment)

Newly added go-eCharger device fail with error Invalid capability "current_limit" on Homey Pro 2023. This is not an issue in previous Homey Pro models.

There is a issue with the SDK with HP2023 devices where Device.getCapabilityOptions() fails with said error.

Issue opened to Athom
athombv/homey-apps-sdk-issues#296

On APIv1 - RFID cards are single variables in the response to "status" query

For example first card would have:

• rca: "1" - card index of the paired RFID card or empty
• rna: "Tapio" - name given, max 10 chars
• eca: "5835" - energy counter (= 583.5 kWh)

"eca": "5835",
"ecr": "0",
"ecd": "0",
"ec4": "0",
"ec5": "0",
"ec6": "0",
"ec7": "0",
"ec8": "0",
"ec9": "0",
"ec1": "0",
"rca": "1",
"rcr": "",
"rcd": "",
"rc4": "",
"rc5": "",
"rc6": "",
"rc7": "",
"rc8": "",
"rc9": "",
"rc1": "",
"rna": "Tapio",
"rnm": "n/a",
"rne": "n/a",
"rn4": "n/a",
"rn5": "n/a",
"rn6": "n/a",
"rn7": "n/a",
"rn8": "n/a",
"rn9": "n/a",
"rn1": "n/a",

On APIv2 - RFID cards are in a JSON-array in response to "/api/status?filter=cards,trx" query

• trx
  • null, for no transaction
  • 0, active transaction without RFID card
  • 1-10, active transaction with RFID card
• cards-array - ten groups of
  • name - name given, max 10 chars
  • energy - energy counter in Wh (583524 = 583.524 kWh)
  • cardId - true or false if a RFID card is paired to the slot or not

{
  "trx":null,
  "cards":[
    {
      "name":"Tapio",
      "energy":583524,
      "cardId":true
    },
    {
      "name":"n/a",
      "energy":0,
      "cardId":false
    },
    {
      "name":"n/a",
      "energy":0,
      "cardId":false
    },
    {
      "name":"n/a",
      "energy":0,
      "cardId":false
    },
    {
      "name":"n/a",
      "energy":0,
      "cardId":false
    },
    {
      "name":"n/a",
      "energy":0,
      "cardId":false
    },
    {
      "name":"n/a",
      "energy":0,
      "cardId":false
    },
    {
      "name":"n/a",
      "energy":0,
      "cardId":false
    },
    {
      "name":"n/a",
      "energy":0,
      "cardId":false
    },
    {
      "name":"n/a",
      "energy":0,
      "cardId":false
    }
  ]
}

Describe the bug

Changing allow_charging mode has no effect, if authentication is required (v2-api-key: acs=1) from the go-eCharger security settings. Works fine when authentication is disabled (v2-api-key: acs=0)

Workaround

For now, disable authentication, and the allow_charging works as expected from Homey.

Expected behavior

allow_charging changes in Homey, should work also with authentication.

Related information

• Check weather V2 API key acs is 0=Open or 1=Wait
• If Open, no additional logic needed
• If Wait, add logic to issue trx=0, before allow_charge, to authenticate an anonymous transaction, if not authenticated trx=null yet.
• This will start the support for using RFID cards to authenticate RFID based transactions also.

Hello Tapio, first of all, thanks for the great go-e app for homey, I am exploring it, being the owner of go-e charger (gemini 4th gen).

I have a nissan leaf (2012), which I have charge at 1 phase, 3 phases is not possibl. When I use the 'when-card' 'the electric current changed' and connect it with a timeline card with the present current, it seems to work incorect: it returns 1/3 of the present current. So for instance, if the current set is 6 amperes, the 'tag' current returns 2A. Is there something I do wrong? Or is this really a bug? Thanks, Norbert

Verify / Translate "nl" objects in translations-directory.

It would be nice to have the informative capability values screen as first and default screen.

Hello Tapio
I’d like to start by wishing you a very happy new year in 2024 :slight_smile:
I just wanted to let you know about a bug that has been going on for a few days now and which is causing all the flows to stop working with the go-e charger. I’ve created the following report: a3b6fa51-1a03-4c60-a92a-33f804297ce7
I don’t know if this is the case, but I have the impression that the problem appeared following the last update to the charging station. Thank you very much in advance for a correction, and happy new year!

Screenshot 2024-01-01 at 11.02.57
776×1578 47.7 KB

Verify / Translate "fr" objects in translations-directory.

Describe the bug
Directly after installation I have seen the actions turn on/turn off but after a minute or so when creating a flow, no actions are displayed. For “If/And” actions are listed, but also had those disappeared ones.

To Reproduce
Steps to reproduce the behavior:

1. Clean install of app
2. Create a flow
3. Choose “new card” new ticket?
4. Under “Then” go to Go-e charger
5. Empty list displayed

Expected behavior
At least 2 choices displayed “turn on” and “turn off”

Screenshots
Can add later if needed

Desktop (please complete the following information):

• OS: iOS latest (Jan 2023) 16.1.1
• Homey app latest 8.1.1
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: iPhone 13
• OS: [e.g. iOS 16.1.1
• Browser chrome (not used)
• Version [e.g. 22]

Additional context
Add any other context about the problem here.