Atome sensors have stopped working (several subscriptions) #8
Labels
explanation
Explanation given
Comments
|
Hello, When |
|
Pease have you several subscriptions within your account ? |
|
Yes, I have 4 subscriptions in my account. Only the first one has a key
atome.
Le jeu. 3 févr. 2022 à 09:23, jugla ***@***.***> a écrit :
… Pease have you several subscriptions within your account ?
—
Reply to this email directly, view it on GitHub
<#8 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASPFAH2INIE6QFF5HSR3AALUZI3RJANCNFSM5NNGD63Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I have checked with the Android Atome app and I would say it does not work
(I saw this after the last keyatome integration release) but I did not care
as I had the data from HA. But now I have nothing from both sides :-( :
In the android atome app,I have the "realtime" data during some seconds and
after it seems to be disconnected. If I switch between the different tabs
of the app, the data are not refreshed and then I finally have the login
form that appears.
Le jeu. 3 févr. 2022 à 09:21, jugla ***@***.***> a écrit :
… Hello,
Thanks for your report.
When {'isConnected': False, 'time': '2022-02-02T22:17:59+01:00', it means
that the linky is not connected , but TotalEnergy server still answers.
Please can you check on total energy application if everything is going
well ?
—
Reply to this email directly, view it on GitHub
<#8 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASPFAH2AOJATNZ6UKZLSGELUZI3HPANCNFSM5NNGD63Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Hello, |
|
Hi the LED is green and flashing which means it is correctly functionning
Le jeu. 3 févr. 2022 à 12:09, jugla ***@***.***> a écrit :
… Hello,
An hint : can you check the light on the atome (linky).
It must green to be connected to the server. (Perhaps you already know)
—
Reply to this email directly, view it on GitHub
<#8 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASPFAH4Q7U5YKS5PFNCLG2LUZJPADANCNFSM5NNGD63Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I'm puzzled :
|
|
I will contact the Total support to ask.
Le jeu. 3 févr. 2022 à 15:23, jugla ***@***.***> a écrit :
… I'm puzzled :
- linky LED is ok
- the android apps is ko
Let's wait a little if on server side, they solve the issue.
—
Reply to this email directly, view it on GitHub
<#8 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASPFAHYWYKHBMHMLINSKAZ3UZKFUTANCNFSM5NNGD63Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
For my knowledge, is the key atome integration using the
https://esoftlink.esoftthings.com/login web service ?
Le jeu. 3 févr. 2022 à 17:24, Chanavat Christophe <
***@***.***> a écrit :
… I will contact the Total support to ask.
Le jeu. 3 févr. 2022 à 15:23, jugla ***@***.***> a écrit :
> I'm puzzled :
>
> - linky LED is ok
> - the android apps is ko
> Let's wait a little if on server side, they solve the issue.
>
> —
> Reply to this email directly, view it on GitHub
> <#8 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ASPFAHYWYKHBMHMLINSKAZ3UZKFUTANCNFSM5NNGD63Q>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
|
I have discussed with the support. If I understood correctly they want to
progressively remove the atome application and to replace it with the
"conso live" available in the totalenergies android application. Could it
be that they have cut off the service for me ?:
I cant connect anymore to the atome api service
https://esoftlink.esoftthings.com/login and the atome android app is not
working more than 5 seconds.
The conso live of the totalenergies android app is working correctly.
Le jeu. 3 févr. 2022 à 17:39, Chanavat Christophe <
***@***.***> a écrit :
… For my knowledge, is the key atome integration using the
https://esoftlink.esoftthings.com/login web service ?
Le jeu. 3 févr. 2022 à 17:24, Chanavat Christophe <
***@***.***> a écrit :
> I will contact the Total support to ask.
>
> Le jeu. 3 févr. 2022 à 15:23, jugla ***@***.***> a écrit :
>
>> I'm puzzled :
>>
>> - linky LED is ok
>> - the android apps is ko
>> Let's wait a little if on server side, they solve the issue.
>>
>> —
>> Reply to this email directly, view it on GitHub
>> <#8 (comment)>,
>> or unsubscribe
>> <https://github.com/notifications/unsubscribe-auth/ASPFAHYWYKHBMHMLINSKAZ3UZKFUTANCNFSM5NNGD63Q>
>> .
>> Triage notifications on the go with GitHub Mobile for iOS
>> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
>> or Android
>> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>>
>> You are receiving this because you authored the thread.Message ID:
>> ***@***.***>
>>
>
|
|
Hello, Just to try can you check if by declare under UI, keyatome for link1 /2 /3 and 4, one gives live consumption. Definitively I have to add a sensor showing which subscription it retrieves |
|
some time ago, a successful login was redirecting to some atome pages like :
/graph-query-last-consumption
/profile
/logout
... etc but it does not work anymore
You were right to ask to try as it works now with link number 3 => I have
my atome data integrated into HA.
I dont know why suddenly during Tuesday night, the atome service suddenly
changed ...
Cheers,
Christophe
Le jeu. 3 févr. 2022 à 19:28, jugla ***@***.***> a écrit :
… Hello,
I've moved towards their new application.
It still work for me.
https://esoftlink.esoftthings.com/login is not intended to be used
directly. This link is used by application.
Just to try can you check if by declare under UI, keyatome for link1 /2 /3
and 4, one gives live consumption.
Definitively I have to add a sensor showing which subscription it retrieves
—
Reply to this email directly, view it on GitHub
<#8 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASPFAH4IRCXSO7IEXD5B2ETUZLCNDANCNFSM5NNGD63Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Thanks for your feedback. Philippe |
|
It is back :-(
2022-02-04 18:16:02 WARNING (SyncWorker_0)
[custom_components.keyatome.sensor] Live Data : Missing last value in
values: {'isConnected': True, 'time': '2022-02-04T18:16:02+01:00',
'timeLimitBeforePowerFailure': -1}2022-02-04 18:16:03 ERROR
(SyncWorker_0) [custom_components.keyatome.sensor] Live Data : Missing
last value in values: {'isConnected': True, 'time':
'2022-02-04T18:16:03+01:00', 'timeLimitBeforePowerFailure': -1}
Le ven. 4 févr. 2022 à 08:25, jugla ***@***.***> a écrit :
… Closed #8 <#8>.
—
Reply to this email directly, view it on GitHub
<#8 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASPFAH64LMRXTKXSD4U3QF3UZN5NFANCNFSM5NNGD63Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
The atome is connected on server. |
|
Can you wait a little. |
|
I have the problem with the Android atome app and the conso live app ... it
seems to be a Total service issue.
You dont have the same problem ?
Le ven. 4 févr. 2022 à 18:43, jugla ***@***.***> a écrit :
… Can you wait a little.
If still there, restart HA and tell me if it works
—
Reply to this email directly, view it on GitHub
<#8 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASPFAHZ2RTEWHKMFFWNHVJ3UZQF2VANCNFSM5NNGD63Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
No it works fine at home ... NB: I have lot of pb at a time since atome disconnects from my wifi router. I put a wifi router closer, and now no more issue. |
jugla
changed the title
|
I phoned again to the Total support as the Live Power was not working. They
told me that they were experiencing a service issue this week, it is not
yet solved and they are working on it.
We have to wait expecting that it will solve the keyAtome as well.
Le sam. 5 févr. 2022 à 11:31, jugla ***@***.***> a écrit :
… @tofgun <https://github.com/tofgun> , please see #9
<#9>
—
Reply to this email directly, view it on GitHub
<#8 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASPFAH4VQBKCGZF6UXAO7XTUZT4ABANCNFSM5NNGD63Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Thanks a lot for your feedback |
|
it's now ok for me |
|
In keyatome V5.0.0 , I have added a "login_stat" sensor . Thus you can check the user_ref to know if you have addressed the right linky. |
|
Hello, in keyatome V5.1.0, I have added the list of user reference within the user account. |
|
My data are back since ~14h today. |
|
Thanks for your feed back :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Atome sensors have stopped working ...
2022-02-02 22:17:59 WARNING (SyncWorker_4) [custom_components.keyatome.sensor] Live Data : Missing last value in values: {'isConnected': False, 'time': '2022-02-02T22:17:59+01:00', 'timeLimitBeforePowerFailure': -1}
2022-02-02 22:18:00 ERROR (SyncWorker_4) [custom_components.keyatome.sensor] Live Data : Missing last value in values: {'isConnected': False, 'time': '2022-02-02T22:18:00+01:00', 'timeLimitBeforePowerFailure': -1}
Screenshots
The text was updated successfully, but these errors were encountered: