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

Snille

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

karsten13

@snille

the cors policies are more restricted with newer chromium releases and therefore in electron too.

There are already some issues here 1, 2 …

If HomeAssistent and mm are running on the same pi this may works when changing the host in the module config to localhost or 127.0.01.

In other cases it will be difficult to access the picture urls from inside the <module-name>.js file, accessing them from the node_helper.js should work. So one solution could be to fetch them with node_helper.js to a mm directory and use these urls in <module-name>.js.

Because I have no HomeAssistant I can not test this so this are only my thoughts so far …

aseadc86

I just set this module up and I love it. Great job. I was wondering if there was anyway to bring in 2 sensors on the same row? I’m mostly using it for temperature and humidity sensors in different rooms. Just to streamline, eliminate redundancy and save space.

This:
Master Bedroom: 70 / 40 F / %
Instead of:
Master Bedroom Temp: 70 F
Master Bedroom Humidity: 40 %

It would be really cool to have the icons directly after the value and then the units could be set to false:

Master Bedroom: 70 mdi:thermostat / 40 mdi:water-percent

I just comically dove through the code thinking I might be able to copy/paste my way through the changes. I know my limits…

cowboysdude

This works so nice :) Thank you @Snille

Snille

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

Ivanov_d

I have the same issue as some of the other users here “Error fetching stats” with no errors in MM or HA. I generated a new token and changed it in the config, still no luck.

What version of HA are you running?

It was working for me until HA 2021.10: https://forum.magicmirror.builders/topic/15751/mmm-homeassistant-sensors-stopped-working-after-ha-2021-10-update?_=1645122750604

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.