2024-09-17 - dataplicity infrastructure migration issue

[almirus]

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")

[fx-host-assistant]

they started a massive migration: https://status.dataplicity.com/

It should return online by itself... hopefully. My servers are offline at the moment.

[almirus]

[fx-host-assistant]

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.

[fx-host-assistant]

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)")

[fx-host-assistant]

look this: one looks like it is online, but it doesn't load the dashboard. The other dataplicity servers are offline.

[fx-host-assistant]

this is the incident log

[fx-host-assistant]

connected for 2 minutes

now offline again.

[alancik80]

I have the same problem.

There was some maintenance work on the Dataplicity server yesterday.

[fx-host-assistant]

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.

[alancik80]

https://status.dataplicity.com/

Apparently the problem is related to DNS servers.

[fx-host-assistant]

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.

[Phobos1979]

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

[almirus]

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