PrusaLink - problem when printer IP address changes?

Third party integrations
1

Team,

The PrusaLink integration worked fine until I had to change the IP address of the printer from .131 to .18
→ plugin failed.

Searched every file in the /config/.storage folder for “.131” and found 1: core.device_registry.
This file contained:

	      {
	        "area_id": null,
	        "config_entries": [
	          "e9002b00f98d11dad33a61944a4ss0e0"
	        ],
	        "configuration_url": http:// 192.168.1.131",
	        "connections": [],
	        "disabled_by": null,
	        "entry_type": null,
	        "hw_version": null,
	        "id": "e9002b00f98d11dad33a61944a4ss0e0",
	        "identifiers": [
	          [
	            "prusalink",
	            "xxb7d0d9dxxa136bxxx4093xxe4331e0"
	          ]
	        ],
	        "manufacturer": "Prusa",
	        "model": null,
	        "name_by_user": "PrusaMINI 3D",
	        "name": "PrusaMINI",
	        "sw_version": null,
	        "via_device_id": null
	      }

NEXT step:
I updated this file with the new IP address and did a plugin “reload”.
No change. Error message:
Retrying setup: Cannot connect to host 192.168.1.131:80 ssl:default [Connect call failed ('192.168.1.131', 80)]

NEXT step: restart HA server
No change??
The core.device_registry file has the NEW ip address but the plugin for some reason has the old IP address cached somewhere?

QUESTION: What should I do to change the IP address in the PrusaLink integration?
(except for deleting the integration and re-installing it + renaming devices etc)

2

I know I’m a couple of years too late, but in case anyone else finds this forum, here is what worked for me.

Find PrusaLink in “/homeassistant/.storage/core.config_entries” and change the IP address there. After a restart the link should work again.

2 Likes