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

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

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

Verify / Translate "nl" 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.

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

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

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

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)

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
    }
  ]
}