MMM-FHEM no Fhem statusdisplay

[Woody]

in fhem you have to disable “basicAuth” in fhem.cfg like this…
#attr allowed_WEB basicAuth shjedIOhbn6BHFJjGH

[dominic]

@Woody said in MMM-FHEM no Fhem statusdisplay:

attr allowed_WEB basicAuth shjedIOhbn6BHFJjGH

Hi Woody, thanky you for your answer. Can you explain it?
I have defined WEB and than ? Sorry i am very new in FHEM what means " shjedIOhbn6BHFJjGH"?

[dominic]

@Woody
So i now there is this entrie in the config.cfg “define allowed_WEB allowed
#attr allowed_WEB basicAuth xxxxxxxxxxxxxxx
#attr allowed_WEB validFor WEB”

and my config.js looks like this

{
    module: 'MMM-FHEM',
    position: 'top_right',
    config: {
      host: 'localhost',
      port: '8083',
      https: false,
	        devices: [
                  { deviceName: 'ESPEasy_ESP_Test_DHT',
                    deviceReadings: [
                                      { name: 'Temperatur', icon: 'wi wi-thermometer', suffix: '°' },
                                      { name: 'Humidity', icon: 'wi wi-humidity', suffix: '%' },
                                    ],
                  },
                  { deviceName: '',
                    deviceReadings: [
                                      { name: 'Temperatur', icon: 'wi wi-thermometer', suffix: '°' },
                                      { name: 'Humidity', icon: 'fa fa-battery-half', suffix: '' },                                      
                                    ],
                  },
                ],
    },
  },

And this is in FHEM…

where is the mistake?

[Woody]

@dominic said in MMM-FHEM no Fhem statusdisplay:
shjedIOhbn6BHFJjGH is your base64 encoded string of user:password in your fhem.cfg.
In your forelast post it seems to be out commented with a # as i recommended in my last post. For me this means that you’ve no authentication in place and your original problem seems not to be an authorization issue.

[dominic]

@Woody Thank you, yes i think my originlproblem is not the authorization.
Do you have any idea., what it could be ?

[Hotstepper]

Hello,

it seems to be a problem with fhem’s security mechanism “csrfToken”.

You can define a new Web in fhem with a different port and set this up as follws:

fhem.cfg:
define MagicM FHEMWEB 8086 global
attr MagicM allowfrom 192.168.1.14
attr MagicM csrfToken none

Explanation:

• This define’s a new listening port at your fhem server on port 8086
• The only allowed ip is 192.168.1.14 This is the ip of your MagicMirror Device. Choose your ip.
• Disable the use of csrfToken. https://fhem.de/commandref.html or https://wiki.fhem.de/wiki/CsrfToken-HowTo

After fhem restart your readings will be shown at your MagicMirror.

Hope it helps.

Greetz, Hotstepper.