HASS.Agent•5mo ago

Jatoxo - Integration device name mismatch

@Jatoxo

Solution:

Then you need to use something like mqttexplorer to go into the hass.agent topic and clear the old data

Jump to solution

41 Replies

DrR0x•5mo ago

@Amadeo Try configuring it with that name anyway?

Jatoxo•5mo ago

Same as before

Jatoxo•5mo ago

There is this entry in core.device_registry which still has the old name

Jatoxo•5mo ago

Hm I changed that, removed and reinstalled the integration, but again it gets discovered as "JatoxoPC" The only other mention in the registry is in deleted devices ~~If I delete the entry from deleted devices it returns to it after restarting home assistant~~ nvm, that was just not saving properly I think

DrR0x•5mo ago

uh, why does it say LAB02? are you using 2.1 for both the client and the integration? oh nvm delete the entry sry, make sure you dont have the old integration as well

Jatoxo•5mo ago

Probably left over from the previous install

DrR0x•5mo ago

yeah thats my guess, although i was originally thinking you meant that was the current entry 🤣

Jatoxo•5mo ago

It is the current entry still

DrR0x•5mo ago

thats the only one?

Jatoxo•5mo ago

If I go to the device page it still lists the old information

DrR0x•5mo ago

you definitely have this version of the integration?

Jatoxo•5mo ago

Yee

DrR0x•5mo ago

and the old one is uninstalled? Client is 2.x?

Jatoxo•5mo ago

When I setup the device that gets discovered it will show up seperately from this Those are all the downloaded entries

Jatoxo•5mo ago

Solution

DrR0x•5mo ago

Then you need to use something like mqttexplorer to go into the hass.agent topic and clear the old data

Jatoxo•5mo ago

That did it

Jatoxo•5mo ago

Thanks!

Jatoxo•5mo ago

The Lab02 device came back again after deleting There was a sensor with a retained message which was still publishing the old client information

DrR0x•5mo ago

oh, have you still got the old client installed? or did you just need to delete that sensor as well?

Jatoxo•5mo ago

I used the sensor on the old client, but disabled it since so it probably never republished those sensors

DrR0x•5mo ago

ahh okay, so is it working now? or still being a pain?

Jatoxo•5mo ago

Well right now MQTT Explorer doesn't seem to want to delete those messages, I'll see once that works.. Not sure if this is intended now, but the sensors+commands and the media player still get added as seperate devices

DrR0x•5mo ago

if you mean the media player is under hass.agent and sensors/commands are under mqtt then thats right

Jatoxo•5mo ago

Yea, these are the two devices

 {
    "area_id": null,
    "config_entries": [
      "49d91fd7a32d5ed1aa61cc01e707c583"
    ],
    "configuration_url": null,
    "connections": [],
    "disabled_by": null,
    "entry_type": null,
    "hw_version": null,
    "id": "e61c85b8df7862567c75629ba9039199",
    "identifiers": [
      [
        "hass_agent",
        "430c46c3-8da2-4e4e-a137-b478b5bdb3f4"
      ]
    ],
    "labels": [],
    "manufacturer": "HASS.Agent Team",
    "model": "Microsoft Windows NT 10.0.19045.0",
    "name_by_user": null,
    "name": "Jatoxo",
    "serial_number": null,
    "sw_version": "2.0.1",
    "via_device_id": null
  },
  {
    "area_id": null,
    "config_entries": [
      "ec3b792d0706bf4385464c6e6eb688f9"
    ],
    "configuration_url": null,
    "connections": [],
    "disabled_by": null,
    "entry_type": null,
    "hw_version": null,
    "id": "357051eb10bcd2737fb9c5ef0afee6c1",
    "identifiers": [
      [
        "mqtt",
        "hass.agent-Jatoxo"
      ]
    ],
    "labels": [],
    "manufacturer": "HASS.Agent Team",
    "model": "Microsoft Windows NT 10.0.19045.0",
    "name_by_user": null,
    "name": "Jatoxo",
    "serial_number": null,
    "sw_version": "2.0.1",
    "via_device_id": null
  }

 {
    "area_id": null,
    "config_entries": [
      "49d91fd7a32d5ed1aa61cc01e707c583"
    ],
    "configuration_url": null,
    "connections": [],
    "disabled_by": null,
    "entry_type": null,
    "hw_version": null,
    "id": "e61c85b8df7862567c75629ba9039199",
    "identifiers": [
      [
        "hass_agent",
        "430c46c3-8da2-4e4e-a137-b478b5bdb3f4"
      ]
    ],
    "labels": [],
    "manufacturer": "HASS.Agent Team",
    "model": "Microsoft Windows NT 10.0.19045.0",
    "name_by_user": null,
    "name": "Jatoxo",
    "serial_number": null,
    "sw_version": "2.0.1",
    "via_device_id": null
  },
  {
    "area_id": null,
    "config_entries": [
      "ec3b792d0706bf4385464c6e6eb688f9"
    ],
    "configuration_url": null,
    "connections": [],
    "disabled_by": null,
    "entry_type": null,
    "hw_version": null,
    "id": "357051eb10bcd2737fb9c5ef0afee6c1",
    "identifiers": [
      [
        "mqtt",
        "hass.agent-Jatoxo"
      ]
    ],
    "labels": [],
    "manufacturer": "HASS.Agent Team",
    "model": "Microsoft Windows NT 10.0.19045.0",
    "name_by_user": null,
    "name": "Jatoxo",
    "serial_number": null,
    "sw_version": "2.0.1",
    "via_device_id": null
  }

DrR0x•5mo ago

do you just have one sensor/command?

Amadeo•5mo ago

If the message comes back after being deleted in mqttexplorer then something must be publishing it

DrR0x•5mo ago

thats what i was thinking? old client?

Amadeo•5mo ago

It it's intended (old and new instance running) then the ID of one of those will need to be changed in registry

Jatoxo•5mo ago

No I have a couple

DrR0x•5mo ago

Jatoxo•5mo ago

It was just the UI not updating right, once I restarted the program the topics were gone Nope

DrR0x•5mo ago

mine looks like this so its probably fine 🤷‍♂️

Jatoxo•5mo ago

I'll try merging them manually, because with the router's integration there are now 3 devices for this one PC :D Not really sure how hass works under the hood with this, but since they only differ in the identifiers and config_entries shouldn't they automatically have gotten merged?

DrR0x•5mo ago

oh so yours is showing 3 devices? i would try just deleting all of them and reconfiguring, or delete the ones you know are old that way it should fix itself

Jatoxo•5mo ago

Just 2 from Hass.Agent + MQTT and then one from my Router (for presence tracking) with the MAC as connection identifier

DrR0x•5mo ago

okay, so you should just have 1 in the integration and 1 in the MQTT. All sensors/commands are in MQTT and function lik any other '2mqtt` app. While the media player is setup through the integration for more complex features

Jatoxo•5mo ago

I looked into this a bit and home assistant only merges devices based on the connections and identifiers. Since the identifiers for the Hass.Agent and MQTT are different and no connections are provided, it will create different devices for them. The only information provided by the router is the MAC. I think if the client and the integration would report the PC's MAC as part of the device info, all three would automatically merge

DrR0x•4mo ago

@Amadeo could we possibly implement this? @Jatoxo is right afaict, the mac should cause devices to merge. It's not that important but can be added to the list...

Amadeo•4mo ago

Hmm I need to aducate myself about this device merging, I think it's the first time I heard about it

Gaming

Programming

Jatoxo - Integration device name mismatch