@wmx Hi, this has to do with “cors”, it’s not allowed anymore to load the pictures the way I do it, I have to rewrite stuff to fix it, I just don’t have the time… I’m currently loading the pictures form “internet” using a URL instead… It works, but not as nice as geting them from HA…

Like this:

values: [
	{
		sensor: "person.jane_doe",
		name: "Jane are %v%",
		displayvalue: false,
		icons: [{
			"default": "https://www.snille.net/img/magicmirror/users/jane.png"
		}]
	],
},

@BJK Great to hear!! :)

@BJK I don’t start the xin.sh (with pm2). if you read in the xin.sh file you will find instructions how I did it… :) Here you can download the xin.sh.

The script (if you don’t want to download it):

#!/bin/bash

# Before I just tested with the xinput command directly in the autostart file, but that did not work. So now instead I just created a script called xin.sh.
# nano ~/xin.sh
# Then added
# DISPLAY=:0.0 xinput --set-prop "Multi touch Multi touch overlay device" "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1
# There should actually be 3 spaces between “Multi touch” and “Multi touch overlay device”. For some reason the board removes the extra spaces here.
#
# You can actually find the “name” of the device with this commandDISPLAY=:0.0 xinput list
# Shows something like this:
#
# Virtual core pointer id=2 [master pointer (3)]
#   Virtual core XTEST pointer id=4 [slave pointer (2)]
#   Multi touch Multi touch overlay device id=6 [slave pointer (2)]
# Virtual core keyboard id=3 [master keyboard (2)]
# Virtual core XTEST keyboard id=5 [slave keyboard (3)]
#
# Depending on what you have connected to your RPi. 🙂
# 
# So, after creating the xin.sh I added that to the autostart file for LXDE:
# Like this:
# nano ~/.config/lxsession/LXDE-pi/autostart
# Added at the end of the file.
# @/home/pi/xin.sh
# Restarted and it works.
#
DISPLAY=:0.0 xinput --set-prop "Multi touch   Multi touch overlay device" "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1

You have to figure out your own “matrix” of course… :) Not sure if mine is the same…

@core I also used a IR-Frame in my build. Works very well if you just want “simple” point and click and/or point and drag (even with two fingers)… I have not tested it with more advanced stuff. :) But for the MM it’s great. You can read about my build here and underneath the picture, you can find a link to a full photo album with pictures and text to all pictures about what you see. :)

@asifnabi Hi, not with my module “only”, but if you have the information in HA, you can get it to the mirror using my module. I also believe there are modules that do fetch package data to the mirror directly, I just have not used any. :)
Take a look here: https://github.com/MichMich/MagicMirror/wiki/3rd-Party-Modules

Now it’s working again… On both mu mirrors… I don’t understand why… I fixed the “moment” problem at least, I hope… Pushed that… But I guess it’s still the SSL problems left. But I can’t replicate it. @Ivanov_d Where did you set the debug flag to get the errors?

@ivanov_d Nah… Not really, never been down the SSL rabbit hole… :) I have just forked this module and “fixed” the things I needed… I hope someone else can give some tips (PR:s)… My javascript skills are not that great ether… :)

@ivanov_d Interesting… Maybe it’s a package missing, but that would not explain why the non SSL connections would fail…
I found another ting, if you don’t have the “clock” module enabled, the “moment.js” is not loaded, and therefore errors out my module (that uses the moment function)… So I have to fix that somehow as well… :)

@ivanov_d Interesting, I’m not using SSL in HA (I have a Reverse-proxy) that SSL:s everything… So, internally I can get to HA via http (or https) but externally I’ll always go through the reverse-proxy (and SSL). However, the development MM works both with and without SSL. But my real MM now don’t work with either… Darn! :)
What I CAN do, is use curl from ssh on the real MM and get the “status” from all sensors with this…

curl -X GET -H "Authorization: Bearer VeRy-LoNg-API-ToKen" -H "Content-Type: application/json" http://ha-IP:8123/api/states

And it lists everything… Hm…

@ivanov_d Hmm… In my own adventures to find what’s going on, I managed to “break” my real mirror connection to HA (now getting the fetch-error) but my development mirror is still working (against the same HA instance).
I don’t understand what’s going on. :)

As for codebase I’m using my own fork: https://github.com/Snille/MMM-homeassistant-sensors.git

Let me know if you get it to work again… :)

@asifnabi Hi, if you don’t specify the port, it will default to port 8123. And if you are using ssl (https) you need the port to be set to 443. Otherwise it will not work.

So, either do not use ssl (https) and you can skip the port option (because it will default to 8123).
Or use ssl (https) but then you need to specify the port option to 443.

Both options are working for me at least. I hope this clarify things…

@ivanov_d It’s still working for me, when using https. It got to be something else…
I changed my conf to this and it works…

{
	disabled: false,
	module: 'MMM-homeassistant-sensors',
	hiddenOnStartup: false,
	position: 'top_right',
	config: {
		host: "my.ha.url.com",
		port: "443",
		https: true,
		updateInterval: 60000,
		fade: 0,
		title: "Information",
		noaddress: "Away",
		token: "token...",
		values: [
			{
				sensor: "sensor.living_room_temperature",
				name: "Temp i Vardagsrummet %t%",
				icons: [{
						"default": "thermometer"
					}
				]
			}
		]
	}
}

I’m on Hass.IO (from start), maybe the api is still active there? I don’t get it…
It does not work for me on port 8123, but that’s to be expected when using ssl.

@ivanov_d Strange… I’m running HA on it’s own machine and MM on it’s own machine as well, don’t know if that matters… The HA module works on both my “Development” build and the “Real” mirror…
Oh, I’m NOT using a password for the API, that has in deed been deprecated…
This is my “top” part of the Module:

{
	disabled: false,
	module: 'MMM-homeassistant-sensors',
	hiddenOnStartup: true,
	position: 'top_center',
	classes: "Me Work Weather",
	config: {
		host: "X.X.X.X",
		port: "8123",
		https: false,
		title: "Information",
		updateInterval: 60000,
		fade: 0,
		token: "Very-Long-MM-Token...",
		values: 

When did it stop working?

@asifnabi Where are you getting the errors?
I’m on Core Version core-2022.2.8 and Supervisor Version supervisor-2022.01.1 and it works.

@ivanov_d Hm… Am I missing something? It’s working fine here (except for the pictures), I’m on: Core Version core-2022.2.8 and Supervisor Version supervisor-2022.01.1
Where do you get the error?

@aseadc86 Thank you! :) It is not possible to get two values on the same row (I think) in it’s current form… And also the “pictures” from the sensors does not work. I’m just out of time to fix it… :)

@joecas65 Hi! Yes, I do have this issue as well, I have not yet figured out how to solve it. It has to do with the “CORS Policy”. But I’m not sure how to fix it yet. I have to read up a bit and for the moment I’m out of time… Any PR:s would be appreciated! :)

@bachoo786 Hi, I’m using the module and it’s working. It may be that the “request” module is missing? Have you installed it?
Go the to the module folder and do

npm init

&

npm install request

Let me know if it works.

Looking great! I like the idea! :)

@cowboysdude We had snow here yesterday, it’s suppose to be spring! Can you please fix the weather here as well, It’s not really working… :)

Great work, Looking great!