{"id":210,"date":"2026-03-19T12:13:09","date_gmt":"2026-03-19T12:13:09","guid":{"rendered":"https:\/\/www.myuremote.com\/website\/?page_id=210"},"modified":"2026-03-19T12:13:47","modified_gmt":"2026-03-19T12:13:47","slug":"network-scanner","status":"publish","type":"page","link":"https:\/\/www.myuremote.com\/website\/docs\/technical\/network-scanner\/","title":{"rendered":"Network Scanner"},"content":{"rendered":"\n
\n\n
\n

\n Using the MyURemote Network Scanner\n <\/h1>\n\n

\n This page explains how to use the MyURemote Network Scanner<\/strong> to inspect the local network,\n verify whether devices are reachable, and retrieve extra protocol-based information such as\n DLNA<\/strong> or Global Cach\u00e9<\/strong> identification.\n It is intended as a practical technical reference for installers, advanced users,\n and for internal support\/debugging.\n <\/p>\n\n

\n Key idea: the Network Scanner is a support and diagnostic tool, not a device onboarding wizard.<\/strong>\n <\/p>\n <\/header>\n\n

\n\n \n
\n

1. What the Network Scanner is for<\/h2>\n\n

\n The MyURemote Network Scanner is designed as a general local network inspection tool<\/strong>.\n It helps determine which hosts are active on the LAN and can optionally enrich those hosts with\n protocol-specific information.\n <\/p>\n\n

\n In practice, the scanner is useful when you want to answer questions such as:\n <\/p>\n\n

    \n
  • is the device still visible on the local network?<\/li>\n
  • does it still have the expected IP address?<\/li>\n
  • does a Global Cach\u00e9 unit still appear where it should?<\/li>\n
  • does the device respond to a direct ping test?<\/li>\n
  • does the device expose DLNA \/ UPnP information?<\/li>\n <\/ul>\n\n

    \n This is especially helpful during installation, support, troubleshooting,\n or when a previously working integration appears to stop responding.\n <\/p>\n <\/section>\n\n

    \n\n \n
    \n

    2. Core principle<\/h2>\n\n

    \n The scanner is built around a clear separation of responsibilities:\n <\/p>\n\n

      \n
    • Scan<\/strong> = detect hosts on the subnet<\/li>\n
    • Ping<\/strong> = test one specific host for support\/debugging<\/li>\n
    • DLNA \/ GC<\/strong> = enrichment, not the base scan itself<\/li>\n <\/ul>\n\n

      \n This distinction is important.\n A device may be perfectly visible on the network even if it does not support DLNA,\n and a device may support a certain protocol while still requiring a separate support check.\n <\/p>\n\n

      \n In other words: host visibility comes first; protocol-specific identification comes afterwards.<\/strong>\n <\/p>\n <\/section>\n\n

      \n\n \n
      \n

      3. How it works<\/h2>\n\n

      \n The Network Scanner runs through the local MyURemote server on localhost:9090<\/strong>.\n The frontend in the WebView calls local endpoints, and the native side performs the actual scan.\n <\/p>\n\n

      \n The high-level flow is:\n <\/p>\n\n

        \n
      1. The Network Scanner page is opened.<\/li>\n
      2. The frontend starts the scan.<\/li>\n
      3. The native backend begins scanning the local subnet.<\/li>\n
      4. The frontend polls the current results repeatedly.<\/li>\n
      5. Hosts appear progressively in the list.<\/li>\n
      6. Extra protocol-based information is added later where available.<\/li>\n <\/ol>\n\n 
        Frontend (WebView) \u2192 localhost:9090 \u2192 NetworkScannerHandler \u2192 NetworkScannerManager<\/code><\/pre>\n  <\/section>\n\n  
        \n\n  \n  
        \n    
        4. Local endpoints used by the scanner<\/h2>\n\n    
        \n      The scanner communicates through a small set of local endpoints:\n    <\/p>\n\n    
        4.1 Start scan<\/h3>\n    
        \/networkscanner?mode=start<\/code><\/pre>\n\n    
        \n      Starts the scan and returns basic scan metadata such as subnet and IP range.\n    <\/p>\n\n    
        4.2 Poll scan results<\/h3>\n    
        \/networkscanner?mode=results<\/code><\/pre>\n\n    
        \n      Returns the current state of the scan, including the list of hosts found so far.\n    <\/p>\n\n    
        4.3 Ping one host<\/h3>\n    
        \/networkscanner?mode=ping&ip=192.168.0.125<\/code><\/pre>\n\n    
        \n      Performs a direct reachability \/ latency test on one selected host.\n    <\/p>\n\n    
        4.4 DLNA info for one host<\/h3>\n    
        \/networkscanner?mode=dlnainfo&ip=192.168.0.125<\/code><\/pre>\n\n    
        \n      Attempts a DLNA \/ SSDP lookup for a single host and returns model-related information if available.\n    <\/p>\n  <\/section>\n\n  
        \n\n  \n  
        \n    
        5. What the scanner shows<\/h2>\n\n    
        \n      Each host typically appears with a subset of the following data:\n    <\/p>\n\n    
          \n      
        • IP address<\/li>\n      
        • hostname<\/li>\n      
        • latency<\/li>\n      
        • MAC address (if available)<\/li>\n      
        • DLNA status and device information<\/li>\n      
        • Global Cach\u00e9 identification, where detected<\/li>\n    <\/ul>\n\n    
          \n      Example host object:\n    <\/p>\n\n    
          {\n  \"ip\": \"192.168.0.125\",\n  \"hostname\": \"192.168.0.125\",\n  \"latency\": 6,\n  \"mac\": \"\",\n  \"hasDlna\": true,\n  \"friendlyName\": \"Yamaha Receiver\",\n  \"manufacturer\": \"Yamaha Corporation\",\n  \"modelName\": \"RX-A1080\",\n  \"modelNumber\": \"A1080\"\n}<\/code><\/pre>\n\n    
          \n      Not all fields are always present.\n      Basic host data usually appears first, while DLNA or Global Cach\u00e9 details may appear later.\n    <\/p>\n  <\/section>\n\n  
          \n\n  \n  
          \n    
          6. Global Cach\u00e9 detection<\/h2>\n\n    
          \n      The scanner can also recognise Global Cach\u00e9<\/strong> devices.\n      This is especially useful in MyURemote environments because those devices are frequently used as network controllers.\n    <\/p>\n\n    
          \n      Global Cach\u00e9 detection is not based on DLNA.\n      It uses a separate multicast discovery mechanism.\n    <\/p>\n\n    
          \n      In practice, this means the scanner can:\n    <\/p>\n\n    
            \n      
          • identify that a host is a Global Cach\u00e9 unit<\/li>\n      
          • preserve that identification while the rest of the scan continues<\/li>\n      
          • show extra information such as model\/type where available<\/li>\n    <\/ul>\n\n    
            \n      Typical examples include:\n    <\/p>\n\n    
              \n      
            • GC-100<\/li>\n      
            • iTach IP2IR<\/li>\n      
            • iTach IP2SL<\/li>\n      
            • other Global Cach\u00e9 variants<\/li>\n    <\/ul>\n\n    
              \n      This is particularly helpful when a system no longer responds as expected and you first need to verify\n      whether the correct Global Cach\u00e9 still exists on the expected IP address.\n    <\/p>\n  <\/section>\n\n  
              \n\n  \n  
              \n    
              7. DLNA \/ UPnP enrichment<\/h2>\n\n    
              \n      The scanner can optionally enrich hosts with DLNA \/ UPnP information.\n      This is useful for receivers, amplifiers, media renderers and similar devices.\n    <\/p>\n\n    
              \n      Typical DLNA fields include:\n    <\/p>\n\n    
                \n      
              • friendlyName<\/code><\/li>\n      
              • manufacturer<\/code><\/li>\n      
              • modelName<\/code><\/li>\n      
              • modelNumber<\/code><\/li>\n      
              • deviceType<\/code><\/li>\n      
              • udn<\/code><\/li>\n    <\/ul>\n\n    
                \n      However, DLNA is best understood as enrichment<\/strong>, not as the basis of the scan.\n      A host may be active and useful even if it exposes no DLNA information at all.\n    <\/p>\n\n    
                \n      Also note that DLNA responses may appear later than the basic host entry,\n      because multicast responses can arrive asynchronously and some devices answer more slowly than others.\n    <\/p>\n  <\/section>\n\n  
                \n\n  \n  
                \n    
                8. Typical workflow in the app<\/h2>\n\n    
                  \n      
                1. Open the Network Scanner<\/strong> page from the Tools menu.<\/li>\n      
                2. Start a scan.<\/li>\n      
                3. Wait for hosts to appear progressively.<\/li>\n      
                4. Use the PING<\/strong> action if you want to validate direct reachability.<\/li>\n      
                5. Use the DLNA<\/strong> action when you want protocol-specific details for one host.<\/li>\n    <\/ol>\n\n    
                  \n      This makes the scanner useful both as:\n    <\/p>\n\n    
                    \n      
                  • a quick local network overview<\/li>\n      
                  • a support\/debug tool for problematic devices<\/li>\n    <\/ul>\n  <\/section>\n\n  
                    \n\n  \n  
                    \n    
                    9. Practical use cases<\/h2>\n\n    
                    9.1 Verifying whether a device still exists on the network<\/h3>\n    
                    \n      If a previously working device stops responding, the first question is often whether the host is still visible at all.\n      The scanner gives a quick answer.\n    <\/p>\n\n    
                    9.2 Confirming the IP address of a Global Cach\u00e9 unit<\/h3>\n    
                    \n      A Global Cach\u00e9 controller may still exist but no longer be reachable under the expected IP address.\n      The scanner helps confirm whether the correct unit is still present.\n    <\/p>\n\n    
                    9.3 Checking whether a receiver exposes DLNA information<\/h3>\n    
                    \n      Some amplifiers and receivers can be identified through DLNA, making it easier to confirm brand, model and role.\n    <\/p>\n\n    
                    9.4 Support and debugging<\/h3>\n    
                    \n      The separate ping action gives a direct, host-level test.\n      This can help distinguish network reachability problems from protocol-specific issues.\n    <\/p>\n  <\/section>\n\n  
                    \n\n  \n  
                    \n    
                    10. Performance principles<\/h2>\n\n    
                    \n      The scanner is designed to show useful information quickly.\n    <\/p>\n\n    
                      \n      
                    • the first hosts should appear fast<\/li>\n      
                    • the UI should not block while scanning continues<\/li>\n      
                    • protocol enrichment should not prevent basic host visibility<\/li>\n      
                    • slow devices should not make the scanner feel unusable<\/li>\n    <\/ul>\n\n    
                      \n      In practice, this means that scan logic and enrichment logic should remain clearly separated.\n    <\/p>\n  <\/section>\n\n  
                      \n\n  \n  
                      \n    
                      11. Important limitations<\/h2>\n\n    
                        \n      
                      • not every host responds reliably to every reachability method<\/li>\n      
                      • not every host supports DLNA<\/li>\n      
                      • not every host exposes a meaningful hostname<\/li>\n      
                      • multicast-based discovery depends on the local network and platform behaviour<\/li>\n      
                      • different platforms may behave differently for the same device<\/li>\n    <\/ul>\n\n    
                        \n      In particular:\n    <\/p>\n\n    
                          \n      
                        • Android uses host detection based mainly on InetAddress.isReachable(...)<\/code><\/li>\n      
                        • iOS does not offer an identical equivalent and may rely more on hybrid detection techniques<\/li>\n      
                        • Android multicast discovery requires a MulticastLock<\/strong><\/li>\n    <\/ul>\n\n    
                          \n      This means the Network Scanner is best understood as a practical support tool,\n      not as a perfect network inventory engine.\n    <\/p>\n  <\/section>\n\n  
                          \n\n  \n  
                          \n    
                          12. Quick debugging guide<\/h2>\n\n    
                          \n      When a device does not behave as expected, this is a useful order of checks:\n    <\/p>\n\n    
                            \n      
                          1. Does the IP address appear in the scan?<\/li>\n      
                          2. Does the host respond to a direct ping test?<\/li>\n      
                          3. Does manual DLNA info retrieval return anything?<\/li>\n      
                          4. Does Global Cach\u00e9 discovery identify the host correctly?<\/li>\n    <\/ol>\n\n    
                            \n      This helps separate:\n    <\/p>\n\n    
                              \n      
                            • network visibility problems<\/li>\n      
                            • reachability problems<\/li>\n      
                            • protocol support problems<\/li>\n      
                            • device identification problems<\/li>\n    <\/ul>\n  <\/section>\n\n  
                              \n\n  \n  
                              \n    
                              13. Summary<\/h2>\n\n    
                                \n      
                              • The MyURemote Network Scanner is a local support and diagnostic tool.<\/li>\n      
                              • It detects hosts on the subnet and displays them progressively.<\/li>\n      
                              • It offers a separate PING action for support\/debugging.<\/li>\n      
                              • It can enrich hosts with DLNA \/ UPnP information where available.<\/li>\n      
                              • It can identify Global Cach\u00e9 devices independently of DLNA.<\/li>\n      
                              • It should always be understood as: scan first, enrichment later<\/strong>.<\/li>\n    <\/ul>\n\n    
                                \n      Bottom line: the Network Scanner helps distinguish basic network visibility from protocol-specific device behaviour.<\/strong>\n    <\/p>\n  <\/section>\n\n<\/section>\n","protected":false},"excerpt":{"rendered":"
                                Using the MyURemote Network Scanner This page explains how to use the MyURemote Network Scanner to inspect the local network, verify whether devices are reachable, and retrieve extra protocol-based information such as DLNA or Global Cach\u00e9 identification. It is intended as a practical technical reference for installers, advanced users, and for internal support\/debugging. Key idea: […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":144,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-210","page","type-page","status-publish","hentry"],"blocksy_meta":{"has_hero_section":"disabled","styles_descriptor":{"styles":{"desktop":"","tablet":"","mobile":""},"google_fonts":[],"version":6}},"_links":{"self":[{"href":"https:\/\/www.myuremote.com\/website\/wp-json\/wp\/v2\/pages\/210","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.myuremote.com\/website\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.myuremote.com\/website\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.myuremote.com\/website\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.myuremote.com\/website\/wp-json\/wp\/v2\/comments?post=210"}],"version-history":[{"count":1,"href":"https:\/\/www.myuremote.com\/website\/wp-json\/wp\/v2\/pages\/210\/revisions"}],"predecessor-version":[{"id":211,"href":"https:\/\/www.myuremote.com\/website\/wp-json\/wp\/v2\/pages\/210\/revisions\/211"}],"up":[{"embeddable":true,"href":"https:\/\/www.myuremote.com\/website\/wp-json\/wp\/v2\/pages\/144"}],"wp:attachment":[{"href":"https:\/\/www.myuremote.com\/website\/wp-json\/wp\/v2\/media?parent=210"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}