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

Snille

@Karlberg Great! :)

fribse

@Snille Looks very nice, good job!

vageesh79

anyway to use https with self signed. I am getting error "“Error Fetching Stats”. No error on homeassistant and MM

bachoo786

@karlberg hey man thanks for the module. However I am getting “Error fetching stats” there is no error in HA.

Can you please help? thnaks

Snille

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

hedmik

@snille Hi, trying to use this module but getting below error.
I followed your instructions i hope :-)
[07.01.2022 17:10.13.062] [ERROR] (node:30547) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading ‘body’)
at /home/pi/MagicMirror/modules/MMM-homeassistant-sensors/node_helper.js:40:83
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
[07.01.2022 17:10.13.067] [ERROR] (node:30547) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 46)

cowboysdude

@hedmik Been trying to get it to work for a couple weeks now… no luck for me either… @Snille where you at? LOL

sdetweil

@cowboysdude that error doesn’t line up with the code on GitHub

line 40 col 83 is inside a routine making the url string, not handling a request response

so, what code is actually being run?

hedmik

@sdetweil my code looks like this, perhaps it’s a need for an update…?

sdetweil

@hedmik well, only the error part at the moment

typically on error there is no body

   error.response.body

I would change that to

  JSON.stringify(error,null,2)

that way u see the whole error object

then, on e we know the error, we can work on the cause