Need to manually reload

[ebagnoli]

Hi,

since a few days i was down with dataplicity.
I tought it was the same problem of Dataplicity service being down, but I have noticed that if I go in the integration and I ask to manually reload the integration it works.
If you open your page on dataplicity and you see your revere in red, disconnected, after you reolad the integration of AlexxIT it becomes green and it works.

Is it something you can do from the integration not to go offline?

Thanks

[ebagnoli]

Tested again this morning, same problem, if you dont't reload manually the device goes offline. You reload and everything works fine.

[almirus]

the same problem

[JSferry]

I have the same problem but now by reloading the integration I can't solve it.

[ebagnoli]

Solved using Ivano suggestion:

in configuration.yaml:

binary_sensor:

• platform: rest
  name: Reachable through Dataplicity
  resource: https://.dataplicity.io
  method: GET
  timeout: 10
  value_template: "{{ not 'Device not Connected' in value }}"
  scan_interval: 60

Then, an automation to reload the integration copy this in Yaml and after pass to the visual editor.

alias: Reload Dataplicity
description: ""
triggers:

• trigger: state
  entity_id:
  • binary_sensor.reachable_through_dataplicity
    from: null
    to: "off"
• trigger: state
  entity_id:
  • binary_sensor.reachable_through_dataplicity
    from: null
    to: unavailable
    for:
    hours: 0
    minutes: 10
    seconds: 0
    conditions: []
    actions:
• action: homeassistant.reload_config_entry
  metadata: {}
  data:
  entry_id:
  mode: single

You will get an error of Unknown ID

Go in the last part in visual editor and in id you scroll until you find the icon of your istance of Dataplicity,
This fixex the problem and it is stable.

[Akszyn]

I also have a similar problem on the computer where I have to use a hard reload of the website because otherwise it doesn't work, and often I get that the device is offline, while in the Home Assistant Companion app on Android, remote access doesn't work for me at all even though before the 1.2.2 update everything worked fine on the phone or PC. here is a complete workaround for this problem