search

ricott / homey-no.easee

Easee app for Homey
GNU General Public License v3.0
5 stars 5 forks source link

Cant start charging timeout #69

Open Abbiz00 opened 7 months ago

Abbiz00 commented 7 months ago

The app not working with the new homey pro. Works fine with the old one.

58c7f85a-59b0-4cab-b99d-8f73464d9235

ricott commented 6 months ago

The app works fine on the new Homey Pro, I have one myself with two Easee chargers. There are however sometimes communication problems between Easee cloud and the charger. As you probably know the Homey app doesn't communicate directly with the charger, it talks to Easee cloud which in turn talks to the charger.

What I can see in your diag reports is that you seem to check the charger status very frequently. Every 5 seconds you check twice (different flows?) if the charger is charging. Don't know what you want to achieve with this logic, but I would probably use the trigger instead and filter for the Charging status.

Then I see a few entires of errors which I saw for the first time the other day. This is the same problem as this ticket. Error: Command didn't return a state after '50' attempts!

Could it be that you are sending commands to the charger frequently to fill up the queue on the Easee cloud side?

Abbiz00 commented 6 months ago

Thank you for your reply. I will test change my settings./AlbinSkickat från min Galaxy -------- Originalmeddelande --------Från: Richard Barkestam @.> Datum: 2024-02-06 09:19 (GMT+01:00) Till: "ricott/homey-no.easee" @.> Kopia: Abbiz00 @.>, Author @.> Ämne: Re: [ricott/homey-no.easee] Cant start charging timeout (Issue #69) The app works fine on the new Homey Pro, I have one myself with two Easee chargers. There are however sometimes communication problems between Easee cloud and the charger. As you probably know the Homey app doesn't communicate directly with the charger, it talks to Easee cloud which in turn talks to the charger. What I can see in your diag reports is that you seem to check the charger status very frequently. Every 5 seconds you check twice (different flows?) if the charger is charging. Don't know what you want to achieve with this logic, but I would probably use the trigger instead and filter for the Charging status. Then I see a few entires of errors which I saw for the first time the other day. This is the same problem as this ticket. Error: Command didn't return a state after '50' attempts! Could it be that you are sending commands to the charger frequently to fill up the queue on the Easee cloud side?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>