MMM-homeassistant-sensors no icons after MM upgrade to 2.19.0

sdetweil

@Snille you should be able to see the CORS error in the dev window.

however the url gets built now for the image, should be able to change it

wmx

@karsten13 , @Snille
Sorry for the delay, but hanks for your feedback.

Yes, I’m running MM on a raspi 3.
One more point I figured out:
The display connected to the raspi an showing THE mm on the wall has these problems with missing images.
If I connect with a browser from my desltop to the mm URL the images are visible.

I’ll try to test your given notes this weekend and return the results back here.

wmx

@Snille said in MMM-homeassistant-sensors no icons after MM upgrade to 2.19.0:

  icons: [{
  	"default": "https://www.snille.net/img/magicmirror/users/jane.png"
  }]

(think in the example there is one closing bracket missing “]”)

Had the time right now to test this one issue. I insertet the URL to the image from ha :-) (which is a static one here)

http://<my-ha-url>:8123/local/images/hem.png

but after restart of MM the problem still exists.

karsten13

@wmx

should be

icons: [{
  "default": "http://localhost:8080/cors?url=http://<my-ha-url>:8123/local/images/hem.png"
}]

wmx

@karsten13
Ok, tried this new config, but it does not change anything. :-(

borrmi

@karsten13

I tried this(in the brackets)

default": "http://mm_url:8080/cors?url=http://ha_url:8123/media/borrmi.png but this doesn’t work. :-(

can i also use a local path on my mm instead? (e.g. ‘~/MagicMirror/pictures/person.png’)

sdetweil

@borrmi said in MMM-homeassistant-sensors no icons after MM upgrade to 2.19.0:

http://ha_url:8123/media/borrmi.png

does that work from a browser or curl on the system running MagicMirror?

curl -sL http://ha_url:8123/media/borrmi.png >borrmi.png

borrmi

@sdetweil said in MMM-homeassistant-sensors no icons after MM upgrade to 2.19.0:

curl -sL http://ha_url:8123/media/borrmi.png >borrmi.png

no “404: Not Found”

sdetweil

@borrmi u replaced ha_url with the right value, correct?

borrmi

@sdetweil yes. My ha is under 192.168.2.100 and reachable via Browser(8123) and also in ssh

sdetweil

@borrmi ok, I just copy/pasted your url…

if it says 404, then thats the wrong URL to get the image

http://192.168.2.100:8123/

is right… its the rest that is not

borrmi

@sdetweil
i checked the ha path via ssh
the pictures are in /media.
should i put them in another directory (e.g. /home/borrmi/pictures)

sdetweil

@borrmi i have no idea where ha server makes them available to outside the ha machine consumers…

what did u have before this latest MM update?

borrmi

nothing, it is a new installation. first time with a running ha instance in the house

funfact:

in a browser on my pc i can see the pictures with only

{
                            sensor: "person.borrmi",
                            name: "Borrmi ist %v%",
                            displayvalue: false,
                            replace: [{
                                            "home": "zu Hause",
                                            "not_home": "nicht zu Hause",
                                    }
                            ]
                    },

sdetweil

@borrmi ok never ha for me

that is the image definitions, what to use for what…

but not the image itself, which is what mm needs

I don’t know if u request it by name (sensor) or filename (person.borrmi)

borrmi

@sdetweil person.borrmi ist a sensor

Snille

@sdetweil This is what you get back (as a picture) from HA when adding a person as a sensor looks like this:

https://your.haipaddress.here:443/api/image/serve/d5b50f6cf5e15d2e1d3f5457293458f6/512x512

So, before “cors” I just did:

<img src="https://your.haipaddress.here:443/api/image/serve/d5b50f6cf5e15d2e1d3f5457293458f6/512x512" class="ha-img">

And it worked (still does in a browser), but not on the mirror.

The whole “person”-object looks like this:

{
    "entity_id": "person.firstname_lastname",
    "state": "at Some Place",
    "attributes": {
        "editable": false,
        "id": "9cd6gj3a4eb8ds4d0bfd2b0e1e57804ea",
        "latitude": 16.1241928,
        "longitude": 82.9718906,
        "gps_accuracy": 18,
        "source": "device_tracker.google_maps_105082325327346729172",
        "user_id": "402df0jd89b84230bf8fe3g7ff653048",
        "entity_picture": "/api/image/serve/a2dc96037s5b9dg86s4cc6336b62d742/512x512",
        "friendly_name": "FirstName LastName"
    },
    "last_changed": "2022-04-11T18:17:53.738567+00:00",
    "last_updated": "2022-04-11T19:53:55.043510+00:00",
    "context": {
        "id": "2489fb6bas56fgdds142155e5668093a28",
        "parent_id": null,
        "user_id": null
    }
}

Don’t know if this helps… :)

sdetweil

@Snille said in MMM-homeassistant-sensors no icons after MM upgrade to 2.19.0:

“entity_picture”: “/api/image/serve/a2dc96037s5b9dg86s4cc6336b62d742/512x512”

right, there is the url to use

Snille

@sdetweil Correct, and in a normal browser it works. And for me, the “person.sensor” works too (now?)…

Anyway, here you have the “Map-extract” from HA, also using my module for showing the picture of the vacuum-map… In the browser it works, on the Mirror it does not… :)

Browser:

Mirror:

Here is “part” of the extract object (including the picture):

...
        ],
            "model": "roborock.vacuum.s5",
            "used_api": "xiaomi",
            "entity_picture": "/api/camera_proxy/camera.xiaomi_cloud_map_extractor?token=1e870c95e944a30b0731ae4b3a3bc8dsf65231b6ba03fd91d8s96af38d05c6ce",
            "friendly_name": "Xiaomi Cloud Map Extractor",
            "supported_features": 1
        },
...

For some reson the Browser works… Confused yet? :)

wmx

@sdetweil, @Snille
same here.
The urls to the icons work in browser sessions showing MM, but do not work local in raspi with MM.

I tested access from raspi console with

curl -sL http://<ma-ha-url>:8123/local/images/person.jpg >person.jpg

and this works too.

I also have the same problem, the local MM is not able to access a remote_compliments.conf file via URL in the local module\defaults\compliments folder, but I can access it from a browser. Seems to be the same problem!?