• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
MagicMirror Forum
  • Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.

MMM-xiaomi - Temperature and Humidity from your smarthome

Scheduled Pinned Locked Moved Utilities
141 Posts 27 Posters 169.7k Views 27 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    mirko3000
    last edited by Nov 1, 2017, 11:36 AM

    Well the IDs show up in your magic mirror - the problem is to identify which ID belongs to which sensor. I guessed them by checking the temperature, still I agree that this is not very convenient so far. Looking out for a better solution…

    1 Reply Last reply Reply Quote 0
    • A Offline
      Albert2002
      last edited by Nov 1, 2017, 1:44 PM

      Thank you for your replay!

      When I do so I get a “Connecting to XIAOMI gatway…”
      Connecting to XIAOMI gatway..

      As far as I understand "ENETUNREACH " means Network unreachable. I can successfully ping the Gatway at 192.168.2.107 via VNC & LX Terminal.
      Do I have to set up something on my Gateway first?
      Any idea what to do?

      This is what my error log says:

      ERROR! Could not find main module js file for RepositoryForRC
      ERROR! Could not find main module js file for async
      { Error: send ENETUNREACH 192.168.2.107:54321
          at Object.exports._errnoException (util.js:1050:11)
          at exports._exceptionWithHostPort (util.js:1073:20)
          at SendWrap.afterSend [as oncomplete] (dgram.js:402:11)
        code: 'ENETUNREACH',
        errno: 'ENETUNREACH',
        syscall: 'send',
        address: '192.168.2.107',
        port: 54321 }
      

      My mm out:

      Starting MagicMirror: v2.1.3
      Loading config ...
      Loading module helpers ...
      No helper found for module: alert.
      No helper found for module: clock.
      Initializing new module helper ...
      Module helper loaded: MMM-Remote-Control
      Initializing new module helper ...
      Module helper loaded: MMM-xiaomi
      All module helpers loaded.
      Starting server on port 8080 ... 
      Server started ...
      Connecting socket for: MMM-Remote-Control
      Starting node helper for: MMM-Remote-Control
      Connecting socket for: MMM-xiaomi
      Starting xiaomi helper
      Sockets connected & modules started ...
      Launching application.
      Triggering Xiaomi Gateway upate
      
      1 Reply Last reply Reply Quote 0
      • A Offline
        Albert2002
        last edited by Nov 2, 2017, 9:42 PM

        I’ve made a completely new Raspian & MM installation. No other modules installed. the default modules disabled in the config.js.

        I Still get no connection. Im running the Home Gatewy V3 in Dev mode. Do I have to change any settings on my router or somewhere else?

        Right now I get different error messages. Maybe it helps. I would love to see this module running!

        mm-out:

        > magicmirror@2.1.3 start /home/pi/MagicMirror
        > sh run-start.sh
        
        Starting MagicMirror: v2.1.3
        Loading config ...
        Loading module helpers ...
        Initializing new module helper ...
        Module helper loaded: MMM-xiaomi
        All module helpers loaded.
        Starting server on port 8080 ... 
        You're using a full whitelist configuration to allow for all IPs
        Server started ...
        Connecting socket for: MMM-xiaomi
        Starting xiaomi helper
        Sockets connected & modules started ...
        Whoops! There was an uncaught exception...
        MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
        If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues
        Launching application.
        

        MagicMirror error log:

        Error: Token could not be auto-discovered
            at Device._tokenResolve (/home/pi/MagicMirror/modules/MMM-xiaomi/node_modules/miio/lib/device.js:141:13)
            at Device._onMessage (/home/pi/MagicMirror/modules/MMM-xiaomi/node_modules/miio/lib/device.js:80:9)
            at emitTwo (events.js:106:13)
            at Socket.emit (events.js:194:7)
            at UDP.onMessage [as onmessage] (dgram.js:545:8)
        

        MagicMirror out:

         magicmirror@2.1.3 start /home/pi/MagicMirror
        > sh run-start.sh
        
        Starting MagicMirror: v2.1.3
        Loading config ...
        Loading module helpers ...
        Initializing new module helper ...
        Module helper loaded: MMM-xiaomi
        All module helpers loaded.
        Starting server on port 8080 ... 
        You're using a full whitelist configuration to allow for all IPs
        Server started ...
        Connecting socket for: MMM-xiaomi
        Starting xiaomi helper
        Sockets connected & modules started ...
        Launching application.
        Triggering Xiaomi Gateway upate
        Triggering Xiaomi Gateway upate
        

        mm error log:

        { Error: listen EADDRINUSE 127.0.0.1:8080
            at Object.exports._errnoException (util.js:1050:11)
            at exports._exceptionWithHostPort (util.js:1073:20)
            at Server.setupListenHandle [as _listen2] (net.js:1263:14)
            at listenInCluster (net.js:1304:12)
            at doListen (net.js:1428:7)
            at GetAddrInfoReqWrap.asyncCallback [as callback] (dns.js:62:16)
            at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:78:10)
          code: 'EADDRINUSE',
          errno: 'EADDRINUSE',
          syscall: 'listen',
          address: '127.0.0.1',
          port: 8080 }
        
        
        1 Reply Last reply Reply Quote 0
        • M Offline
          mirko3000
          last edited by Nov 2, 2017, 11:12 PM

          Hey Albert,

          I think I have solved your issue: not all gateways seem to allow auto-discovery without authentification via a security token. I have added an additional configuration parameter now where you can provide your token:
          https://github.com/mirko3000/MMM-xiaomi

          Update the module and follow the description at the bottom:
          https://github.com/mirko3000/MMM-xiaomi#authentification

          Hope that works.

          Best regards.

          1 Reply Last reply Reply Quote 1
          • A Offline
            Albert2002
            last edited by Nov 3, 2017, 8:43 AM

            Hi Mirko,

            thank you for your work! I really appreciate this!

            I’ve updated the module and installed the miio command line tools (with sudo)in the same directory. Or do I Have to install the miio command line tools in a different directory?
            How ever, when am running miio command line tools i get

            pi@raspberrypi:~/MagicMirror/modules/MMM-xiaomi $ miio --discover
             INFO  Discovering devices. Press Ctrl+C to stop.
            
            Device ID: 52238776
            Model info: Unknown 
            Address: 192.168.2.107 
            Token: ???
            Support: Unknown
            
            

            My id I’ve discovered seams to be a different style then the one in your example.
            After this I added the device id to my config:

            devices: [{ id: '52238776', name: 'Wohnzimmer' }]
            
            

            I still see the same as before.

            mm error:

            Error: Token could not be auto-discovered
                at Device._tokenResolve (/home/pi/MagicMirror/modules/MMM-xiaomi/node_modules/miio/lib/device.js:141:13)
                at Device._onMessage (/home/pi/MagicMirror/modules/MMM-xiaomi/node_modules/miio/lib/device.js:80:9)
                at emitTwo (events.js:106:13)
                at Socket.emit (events.js:194:7)
                at UDP.onMessage [as onmessage] (dgram.js:545:8)
            

            mm-out:

            
            > magicmirror@2.1.3 start /home/pi/MagicMirror
            > sh run-start.sh
            
            Starting MagicMirror: v2.1.3
            Loading config ...
            Loading module helpers ...
            Initializing new module helper ...
            Module helper loaded: MMM-xiaomi
            All module helpers loaded.
            Starting server on port 8080 ... 
            You're using a full whitelist configuration to allow for all IPs
            Server started ...
            Connecting socket for: MMM-xiaomi
            Starting xiaomi helper
            Sockets connected & modules started ...
            Launching application.
            Triggering Xiaomi Gateway upate
            Triggering Xiaomi Gateway upate
            
            

            MagicMirror error:

            { Error: listen EADDRINUSE 127.0.0.1:8080
                at Object.exports._errnoException (util.js:1050:11)
                at exports._exceptionWithHostPort (util.js:1073:20)
                at Server.setupListenHandle [as _listen2] (net.js:1263:14)
                at listenInCluster (net.js:1304:12)
                at doListen (net.js:1428:7)
                at GetAddrInfoReqWrap.asyncCallback [as callback] (dns.js:62:16)
                at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:78:10)
              code: 'EADDRINUSE',
              errno: 'EADDRINUSE',
              syscall: 'listen',
              address: '127.0.0.1',
              port: 8080 }
            

            MagicMirror out:

            
            > magicmirror@2.1.3 start /home/pi/MagicMirror
            > sh run-start.sh
            
            Starting MagicMirror: v2.1.3
            Loading config ...
            Loading module helpers ...
            Initializing new module helper ...
            Module helper loaded: MMM-xiaomi
            All module helpers loaded.
            Starting server on port 8080 ... 
            You're using a full whitelist configuration to allow for all IPs
            Server started ...
            Connecting socket for: MMM-xiaomi
            Starting xiaomi helper
            Sockets connected & modules started ...
            Whoops! There was an uncaught exception...
            MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
            If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues
            Launching application.
            
            1 Reply Last reply Reply Quote 0
            • B Offline
              barnosch
              last edited by barnosch Nov 3, 2017, 4:54 PM Nov 3, 2017, 4:52 PM

              God damnit.
              Got a letter from the customs today, that my package from China arrived.
              Sadly they are closing Fridays at 2.30pm. The letter arrived at 2.45pm.
              So no chance to fetch it anymore.

              The whole weekend is now useless!

              Let`s see if i have also trouble …

              1 Reply Last reply Reply Quote 0
              • A Offline
                Albert2002
                last edited by Nov 3, 2017, 6:01 PM

                Maybe you can get it tomorrow? Would be great to figure out.

                Something crossed my mind. When I set up the Developer mode in the Gateway there is a password too. I know that I need this one for OpenHAB. Maybe I need it for this module as well?

                M 1 Reply Last reply Nov 3, 2017, 8:06 PM Reply Quote 0
                • M Offline
                  mirko3000 @Albert2002
                  last edited by Nov 3, 2017, 8:06 PM

                  So I just read through the documentation of miio and found this:
                  https://github.com/aholstenson/miio/blob/master/docs/management.md#getting-the-token-of-a-device
                  or:
                  https://github.com/aholstenson/miio/blob/master/docs/management.md#setting-the-token-of-a-device

                  My device seems to provide the token “via auto-token”, in your case it seems it does not. Maybe try either of the above.

                  IDs are same with me, maybe my documentation is wrong here.

                  1 Reply Last reply Reply Quote 0
                  • M Offline
                    mirko3000
                    last edited by Nov 3, 2017, 8:17 PM

                    When I run the discover tool I get the following:

                    Device ID: 56804143
                    Model info: Unknown 
                    Address: 192.168.0.9 (xiaomi-gateway.fritz.box)
                    Token: cfbdb315c0825ccc971918e36923febe via auto-token
                    Support: Unknown
                    
                    Device ID: 158d0001635bb3
                    Model info: lumi.sensor_ht (sensor)
                    Address: Owned by 56804143
                    Token: Automatic via parent device
                    Support: At least basic
                    
                    1 Reply Last reply Reply Quote 0
                    • A Offline
                      Albert2002
                      last edited by Nov 4, 2017, 10:47 AM

                      I am a step ahead!

                      I followed the instructions to get the token “Getting the token when using the Mi Home app”
                      This was working. I could see all the connected devices to the Gateway.

                      pi@raspberrypi:~/MagicMirror/modules/MMM-xiaomi $ miio --discover --sync
                       INFO  Discovering devices. Press Ctrl+C to stop.
                      
                      Device ID: 52238776
                      Model info: Unknown 
                      Address: 192.168.13.1 
                      Token: 6eea5ac1eb475bfedbfff98aab7c2bc7 via auto-token
                      Support: Unknown
                      
                      Device ID: 158d000119fcb2
                      Model info: lumi.magnet (magnet)
                      Address: Owned by 52238776
                      Token: Automatic via parent device
                      Support: At least basic
                      
                      Device ID: 158d00013e28ee
                      Model info: lumi.plug (power-plug)
                      Address: Owned by 52238776
                      Token: Automatic via parent device
                      Support: At least basic
                      
                      Device ID: 158d00015aa973
                      Model info: lumi.switch (controller)
                      Address: Owned by 52238776
                      Token: Automatic via parent device
                      Support: At least basic
                      
                      Device ID: 158d00015736a8
                      Model info: lumi.sensor_ht (sensor)
                      Address: Owned by 52238776
                      Token: Automatic via parent device
                      Support: At least basic
                      

                      At this point I had to switch over to the Pi with the installed MagicMirror:

                      pi@MagicMirror:~ $ miio --discover
                       INFO  Discovering devices. Press Ctrl+C to stop.
                      
                      Device ID: 52238776
                      Model info: Unknown 
                      Address: 192.168.2.107 
                      Token: ???
                      Support: Unknown
                      

                      I’ve updated the Token as described:

                      pi@MagicMirror:~ $ miio --update 52238776 --token 6eea5ac1eb475bfedbfff98aab7c2bc7
                       INFO  Attempting to update 52238776
                       INFO  Device updated
                      

                      I’ve searched for devices again. Now with success!

                      
                      pi@MagicMirror:~ $ miio --discover
                      
                       INFO  Discovering devices. Press Ctrl+C to stop.
                      
                      Device ID: 52238776
                      Model info: Unknown 
                      Address: 192.168.2.107 
                      Token: 6eea5ac1eb475bfedbfff98aab7c2bc7 via stored token
                      Support: Unknown
                      
                      Device ID: 158d000119fcb2
                      Model info: lumi.magnet (magnet)
                      Address: Owned by 52238776
                      Token: Automatic via parent device
                      Support: At least basic
                      
                      Device ID: 158d00013e28ee
                      Model info: lumi.plug (power-plug)
                      Address: Owned by 52238776
                      Token: Automatic via parent device
                      Support: At least basic
                      
                      Device ID: 158d00015aa973
                      Model info: lumi.switch (controller)
                      Address: Owned by 52238776
                      Token: Automatic via parent device
                      Support: At least basic
                      
                      Device ID: 158d00015736a8
                      Model info: lumi.sensor_ht (sensor)
                      Address: Owned by 52238776
                      Token: Automatic via parent device
                      Support: At least basic
                      
                      

                      The problem so far is, that I still don’t get any informations visible in MM. I’ve tried ‘158d00015736a8’ and as well ‘52238776’ as id.
                      The second problem is, that I’ve lost the Gateway in my Mi Home app after updating the Token!

                      The question is, how to copy ( Store?) over the Token to a different Machine?

                      mm error:

                      error: Token could not be auto-discovered
                          at Device._tokenResolve (/home/pi/MagicMirror/modules/MMM-xiaomi/node_modules/miio/lib/device.js:141:13)
                          at Device._onMessage (/home/pi/MagicMirror/modules/MMM-xiaomi/node_modules/miio/lib/device.js:80:9)
                          at emitTwo (events.js:106:13)
                          at Socket.emit (events.js:194:7)
                          at UDP.onMessage [as onmessage] (dgram.js:545:8)
                      
                      1 Reply Last reply Reply Quote 0
                      • 1
                      • 2
                      • 3
                      • 4
                      • 5
                      • 14
                      • 15
                      • 2 / 15
                      2 / 15
                      • First post
                        16/141
                        Last post
                      Enjoying MagicMirror? Please consider a donation!
                      MagicMirror created by Michael Teeuw.
                      Forum managed by Sam, technical setup by Karsten.
                      This forum is using NodeBB as its core | Contributors
                      Contact | Privacy Policy