2024-09-17 - dataplicity infrastructure migration issue
2024-09-18 11:11:08.318 ERROR (m2m) [agent] unable to associate m2m identity ("m2m.associate"=-32603, "Internal error. device is offline")
2024-09-18 11:11:14.260 ERROR (m2m) [agent] unable to associate m2m identity ("m2m.associate"=-32603, "Internal error. device is offline")
2024-09-18 11:11:20.271 ERROR (m2m) [agent] unable to associate m2m identity ("m2m.associate"=-32603, "Internal error. device is offline")
2024-09-18 11:11:26.207 ERROR (m2m) [agent] unable to associate m2m identity ("m2m.associate"=-32603, "Internal error. device is offline")
2024-09-18 11:11:32.180 ERROR (m2m) [agent] unable to associate m2m identity ("m2m.associate"=-32603, "Internal error. device is offline")
2024-09-18 11:11:36.203 ERROR (m2m) [agent] unable to associate m2m identity ("m2m.associate"=-32603, "Internal error. device is offline")
2024-09-18 11:11:38.193 ERROR (m2m) [agent] unable to associate m2m identity ("m2m.associate"=-32603, "Internal error. device is offline")
2024-09-18 11:11:42.266 ERROR (m2m) [agent] unable to associate m2m identity ("m2m.associate"=-32603, "Internal error. device is offline")
2024-09-18 11:11:44.133 ERROR (m2m) [agent] unable to associate m2m identity ("m2m.associate"=-32603, "Internal error. device is offline")
2024-09-18 11:11:49.039 ERROR (m2m) [agent] unable to associate m2m identity ("m2m.associate"=-32603, "Internal error. device is offline")
2024-09-18 11:11:51.130 ERROR (m2m) [agent] unable to associate m2m identity ("m2m.associate"=-32603, "Internal error. device is offline")
2024-09-18 11:11:55.045 ERROR (m2m) [agent] unable to associate m2m identity ("m2m.associate"=-32603, "Internal error. device is offline")
2024-09-18 11:11:57.142 ERROR (m2m) [agent] unable to associate m2m identity ("m2m.associate"=-32603, "Internal error. device is offline")
2024-09-18 11:12:01.220 ERROR (m2m) [agent] unable to associate m2m identity ("m2m.associate"=-32603, "Internal error. device is offline")
2024-09-18 11:12:03.175 ERROR (m2m) [agent] unable to associate m2m identity ("m2m.associate"=-32603, "Internal error. device is offline")
2024-09-18 11:22:52.783 ERROR (m2m) [agent] unable to associate m2m identity ("m2m.associate"=-32603, "Internal error. device is offline")
2024-09-18 11:22:54.861 ERROR (m2m) [agent] unable to associate m2m identity ("m2m.associate"=-32603, "Internal error. device is offline")
2024-09-18 11:22:57.481 ERROR (m2m) [agent] unable to associate m2m identity ("device.check_auth"=1, "authorization failed (code 99)")
2024-09-18 11:22:57.655 ERROR (m2m) [agent] unable to associate m2m identity ("device.check_auth"=1, "authorization failed (code 99)")
2024-09-18 11:22:58.067 ERROR (m2m) [agent] unable to associate m2m identity ("device.check_auth"=1, "authorization failed (code 99)")
2024-09-18 11:22:58.364 ERROR (m2m) [agent] unable to associate m2m identity ("device.check_auth"=1, "authorization failed (code 99)")
2024-09-18 11:22:58.848 ERROR (m2m) [agent] unable to associate m2m identity ("m2m.associate"=-32603, "Internal error. device is offline")
they started a massive migration: https://status.dataplicity.com/
It should return online by itself... hopefully. My servers are offline at the moment.
yes, I read it too... but still nothing works :-( I have some uptimerobot sensors checking my dataplicity servers and, time to time, they get online for a couple of minutes, but not usable. I really don't know if the problem is the dns propagation and we still need to wait.
Fonte: /usr/local/lib/python3.12/site-packages/dataplicity/client.py:308 Prima occorrenza: 09:36:23 (571 occorrenze) Ultima registrazione: 10:41:38
unable to associate m2m identity ("m2m.associate"=-32603, "Internal error. device is offline")
unable to associate m2m identity ("device.check_auth"=429, "Too many requests: 300 reqs/ 300 in 10 seconds")
unable to associate m2m identity ("m2m.associate"=-32603, "Internal error. unable to connect to 'https://m2m.dataplicity.com/m2m/devices/a9263fbf-26af-4de0-a25b-4a18a3b54b8b/'; HTTPSConnectionPool(host='eu.m2m.dataplicity.com', port=443): Read timed out. (read timeout=10)")
look this: one looks like it is online, but it doesn't load the dashboard. The other dataplicity servers are offline.
this is the incident log
connected for 2 minutes
now offline again.
I have the same problem.
There was some maintenance work on the Dataplicity server yesterday.
I can confirm it is a problem on their side. I was able to connect to one of my server and work on it for some minutes, but now it is again offline. So, the component works.
https://status.dataplicity.com/
Apparently the problem is related to DNS servers.
Update - We are aware that some users have reported continued glitchiness in relation to device connections today.
Investigation has determined that some corners of the internet were running a longer DNS TTL than we had anticipated. A workaround has been put in place for the next few days while we wait for any remaining systems to catch up.
Hi, I have the same problem from yesterday... 504 Gateway Time-out My homeassistant goes online but I can't open the dashboard and I can't connect to homeassistant server by dataplicity site :( Hope they'll solve soon the problem
new error
2024-09-18 20:31:11.065 ERROR (dataplicity) [agent] sync failed unable to contact JSONRPC server 'https://api.dataplicity.com' (HTTP Error 502: Bad Gateway)
2024-09-18 20:32:53.838 ERROR (MainThread) [custom_components.dataplicity.utils] Can't register dataplicity device: 500
It is extremely slow. So slow that almost everything times out while waiting for a response. It's not just a DNS problem. I can see some Home Assistant servers online, but the dashboards are not fully loading.
My HA receives data from mobile devices. I receive geodata, sensor status.. But the mobile devices themselves do not have access to my HA. One-way data transfer :( I suspect the problem may be in the wormhole.
hi, i have the same problem.. just to investigate, where do you run your home assistant?
This night I was able to see a couple of HA servers loading, but very slowly. Now again they are offline.
The migration was a disaster
but the Wormhole is not working. It doesn't connect to the server.
and DNS problem too: look at the different IPs
ciao raga. e io che ho perso la testa convito fosse un problema di hassio.
ancora niente? a me continua a non funzionare.
ciao raga. e io che ho perso la testa convito fosse un problema di hassio.
ancora niente? a me continua a non funzionare.
Non me ne parlare vah! π Stavo per buttare tutto all'aria, aggiornato, riavviato, reinstallato dataplicity su HA, poi una vocina mi ha detto di cercare su internet se qualcuno stava riscontrando gli stessi problemi ed eccomi qui.
Stessa trafila mia ππ
Il giorno ven 20 set 2024 alle 00:19 Phobos1979 @.***> ha scritto:
ciao raga. e io che ho perso la testa convito fosse un problema di hassio.
ancora niente? a me continua a non funzionare.
Non me ne parlare vah! π Stavo per buttare tutto all'aria, aggiornato, riavviato, reinstallato dataplicity su HA, poi una vocina mi ha detto di cercare su internet se qualcuno stava riscontrando gli stessi problemi ed eccomi qui.
β Reply to this email directly, view it on GitHub https://github.com/AlexxIT/Dataplicity/issues/30#issuecomment-2362299855, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASMOCGYLHU43OKWROGSV7ZTZXNEYFAVCNFSM6AAAAABONDWHB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRSGI4TSOBVGU . You are receiving this because you commented.Message ID: @.***>
Anch'io lo stesso problema. Qualcuno sa se Γ¨ un problema che riguarda solo la zona Italia?
No, the problem does not depend on the region. Everything started working fine for me last night. But this morning it doesn't work again. I don't understand what they are doing there, but it is unprofessional.
The main problem is they started this migration without sending any advice before and they are not communicating anything since 18th
Hoping that the problem was fixed, just in case, I removed Dataplicity from HACS and installed it again, but it does not appear in the list of integrations, neither from the browser nor in the application. I cleared the cache - it didn't help. Not only have I been unable to access the server remotely for three days, but now I donβt even have the opportunity to try it again. Help
Ora sta funzionando ππΌππΌ π€ π€
Il giorno ven 20 set 2024 alle 12:37 pelik911 @.***> ha scritto:
Hoping that the problem was fixed, just in case, I removed Dataplicity from HACS and installed it again, but it does not appear in the list of integrations, neither from the browser nor in the application. I cleared the cache - it didn't help. Not only have I been unable to access the server remotely for three days, but now I donβt even have the opportunity to try it again. Help
β Reply to this email directly, view it on GitHub https://github.com/AlexxIT/Dataplicity/issues/30#issuecomment-2363410305, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASMOCG7RCWEIANLKD23Z2D3ZXP3E5AVCNFSM6AAAAABONDWHB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRTGQYTAMZQGU . You are receiving this because you commented.Message ID: @.***>
It's working for me now as well.
@Spiderandroid @emanueledonatoni @Phobos1979 vi siete accorti che qui si scrive in inglese? PerchΓ© dobbiamo farci sempre riconoscere? :faceplam:
Some of my servers are back up, others are still not available
My HA is still disconnected. However, I don't understand why there are so few reports online. It seems to be an issue limited to a few users.