ESP8266 + DHT22 + Thingspeak in magic mirror

[Gelomidor]

@tosti007 I got it all working! thank you for pointing me in the right direction!! :D

[tosti007]

Thank you so much for your help!

You’re welcome :D

What i dont get it is why are there so many links and why dont all links have a description above it?

There are so many links because you have to retrieve every field by itself. They don’t have a description because just defining a field to retrieve doesn’t display it yet, this is done in the output section.

Should i only use celsius and humidity?

You can use anything you want.

Could you also explain what mapping means?

Using mapping is a way to translate one value into another. For example you retrieve the state of your lamps and it returns a boolean. Just displaying true or false doesn’t look so nice. on or off would be better and make more sense in a human way. So you could use a mapping to translate that. For the example above the mapping would be:

mappings: {
    on_off: {
        true: 'on',
        false: 'off',
    },
},

The urls i replace with my urls: https://api.thingspeak.com/channels/xxxxx/fields/2/last.txt

Don’t forget to make an url for each field.

With configure output you mean: if i have multiple fields i have to change that number.

No, output configures the way you display your sections (after mapping and formatting) on your mirror.
So for example you have defined 3 urls in the sections value. The first url is the state of your lamps (with a mapping), the second is the humidity in your living room and the third the temperature in your living room. And you want to display it like:

Lamps on
Livingroom 21 degrees 52%

Then your output would look like:

output: [
    ['Lamps','@1'], // use number 1 here because you defined that first in sections
    ['Livingroom','@3','@2'] // you defined temperature as third, but we want to display it first,?so we use @3 first and @2 second
],

Does this explain everything? :)

[tosti007]

@Gelomidor ah great! You’re welcome and enjoy it :D

[tosti007]

@Gelomidor I just realised I made a mistake! Setti your channel to public isn’t secure (anyone would be able to check the states of your lamps ect). Instead you should add the api key to the url by using the same url you would use when it’s public and adding &api_key=YOUR_KEY at the end of the url. Please do update this! (also remove the channel id in the url you usef above in post 6)

[schlachtkreuzer6]

@tosti007 Why Thingspeak and not FHEM?