MMM-HomeAssistant-Sensors (Development) - Show your HA Sensors on your Mirror

Snille

@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?

Ivanov_d

@snille I don’t see any errors in either MM or HA, however I am still getting Error fetching stats in the module front end. Any suggestions for additional places where I could look? I checked the config and all seems fine to me.

Snille

@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?

Ivanov_d

@snille it stopped working after HA version 2021.10 when the API discovery feature was deprecated. I am running HA Supervised on one raspberry pi and MM on another raspberry pi in the same network.

Here is the config of the MM module:

{
  module: 'MMM-homeassistant-sensors',
  position: 'top_right',
  config: {
    title:  'Сензори',
    rowClass: 'normal',
    host: "192.168.1.19",
    port: "8123",
    https: true, //I have SSL enables since my instance is exposed to the Internet
    token: "here_goes_my_token",
    values: [
      {
        sensor: "sensor.bathroom_temp_temperature",
        name: 'Температура',
        icons: [{
          "default": "thermometer"
        }]
      },
      {
        sensor: "sensor.bathroom_temp_humidity",
        name: 'Влажност',
        icons: [{
          "default": "water-percent"
        }]
      },
      {
        sensor: "switch.bathroom_fan_1",
        name: 'Вентилатор 1',
        icons: [{
          "on": "fan",
          "off": "fan-off"
        }],
        replace: [{
          "on": "вкл.",
          "off": "изкл."
        }]
      },
      {
        sensor: "switch.bathroom_fan_2",
        name: 'Вентилатор 2',
        icons: [{
          "on": "fan",
          "off": "fan-off"
        }],
        replace: [{
          "on": "вкл.",
          "off": "изкл."
        }]
      },
    ]
  }
},

Here is the changelog of HA 2021.10:

The API endpoint /api/discovery_info now only return blank values. This endpoint is scheduled to be removed in Home Assistant Core 2022.1.

As a regular user of Home Assistant, this change should not affect you.

(@ludeeus - #56097) (api docs)

In the past I was having issues with https and the local IP address and then I changed it to the DNS hostname blabla.duckdsn.org and the external port for https (443) and it was working fine until the /api/discovery_info endpoint was deprecated.

cowboysdude

@snille Well that’s really not a deal breaker. It works and gaps the bridge. It’s a great module!

Snille

@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

@snille what is the most up-to-date code repo? The one that I pulled from is https://github.com/theskyisthelimit/MMM-homeassistant-sensors.git

Could it be that I have an old code base? I tried with different ports, URL/IP, still the same and still no errors in both logs HA or MM …

EDIT: I tried with another HA instance that I have which doesn’t have SSL enabled and it worked, so now I need to figure out what the difference between the two are :)

Will keep you posted.

Snille

@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… :)

Ivanov_d

@snille lol sorry to hear that. I managed to get it to work on my main HA instance by removing SSL from my HA configuration.yaml file:

However, that doesn’t suit my needs as I control my house through my phone over the Internet and I want SSL to be enabled. I am continuing testing. Will keep you posted.

Snille

@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…