Install Gladys on the same machine as Home Assistant

[Papashultz]

I have a clue by looking at the logs:

The protocol requested by Gladys is EZSP while it should be set to Ember.

Where and how can I switch to Ember?

[mutmut]

in a config file in the zigbee2mqtt directory which is itself in the gladys directory I think (I have an external z2m at home).

[Papashultz]

So it works — you will just need to let the creator know to change EZSP to ember in those scripts.

For your information, access path: /var/lib/gladysassistant/zigbee2mqtt/z2m/configuration.yaml

homeassistant:
  enabled: false
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://localhost:1884
  user: gladys
  password: gHBDp8JgxyKmbNEKByLK
serial:
  port: /dev/ttyACM0
  adapter: ember
map_options:
  graphviz:
    colors:
      fill:
        enddevice: '#fff8ce'
        coordinator: '#e04e5d'
        router: '#4ea3e0'
      font:
        coordinator: '#ffffff'
        router: '#ffffff'
        enddevice: '#000000'
      line:
        active: '#009900'
        inactive: '#994444'
frontend:
  enabled: true
  port: 12000
version: 4

Thanks again for your help — I just spent the morning on it.

[Will_71]

@Papashultz

, We’ll just need to notify the great creator to change EZSP to ember in those scripts

It’s planned but not available yet

[pierre-gilles]

@Papashultz

We just need to warn the great creator to change EZSP to Ember in those scripts.

I don’t know if there’s a feature request for that?

We had a Gladys developer who had offered to do it, but he has since left the project.

We need to add lines for each dongle + Ember, so as not to break existing backward compatibility: each dongle will appear twice in the list, once for « EZSP », once for « Ember ».

If anyone wants to take this on, volunteers welcome

[pierre-gilles]

@Terdious

I wanted to start looking, but I think it has to be @pierre-gilles who does it because you need to create an “Add-on repository” (e.g.: « gladys-haos-addon »)

It’s done in my latest YouTube video

Zéro code : Je créé un Add-on Home Assistant avec l'IA (45 min chrono)

@Papashultz

So it works, you’ll just need to warn the great creator to change EZSP to ember in these scripts.

So, @cicoub13 took this topic and made a PR here :

Zigbee - Mise à jour driver ezsp vers ember

Bonjour, Comme beaucoup de personnes semblent affectées par ce retard, j’ai fini le développement du driver z2m ember et l’image Docker est disponible pour test ici : docker pull cicoub13/gladys:z2m-ember Détails : pour permettre aux gens qui n’ont pas mis à jour, j’ai gardé l’option (legacy) driver ezsp la migration est automatique pour les personnes qui ont un dongle de la liste (sans vérification du firmware). Je pense que la majorité des personnes n’auront pas de souci, mais ce…

it will quickly go into Gladys on master !

[McFlyPartages]

@pierre-gilles I know this isn’t necessarily your priority, but I just installed the Gladys add-on directly in Home Assistant, and according to the add-on’s information, it’s not really clear if we’re on the latest version. Granted, the add-on itself is version 2.0.2, but it can be confusing when Gladys is on 4.80.

Do you think you could update the add-on’s info with Gladys’s version, but I’m not sure if that won’t update the add-on and potentially break things.

Or simply add a note that the add-on downloads the latest version of Gladys and that Gladys updates are automatic.

Nothing urgent, of course

[pierre-gilles]

Thanks for the feedback, it’s fixed

I’ve set up a GitHub Action that runs every morning at 6 a.m. and automatically updates the Hassio add-on version to match Gladys’s when a new version is released.

Thus, Home Assistant will automatically propose an add-on update when it’s available.

If you get a chance to test, feel free to let me know if you notice any issues!

Note that there are still some limitations with this add-on:

All integrations where Gladys directly manages Docker containers will not work. Indeed, it’s Home Assistant that controls Docker, and Gladys doesn’t have the necessary permissions to create or manage other containers.

That said, in the context of Home Assistant, this is generally not very problematic. For example, for Zigbee2MQTT, you’ll just need to connect Gladys to your existing MQTT broker.

[McFlyPartages]

Awesome,

Yeah, I was already using external stuff anyway, so it’s not a problem.

I’ll see how it behaves after the update and let you know.