Autonomo 4 - How to run on a different environment than production for testing? (internal)

Steps to install Autonomo to a non-production environment

1. Environments
   1. Production - nothing has to be used, default has everything, so NOTHING has to be added, created, changed by the user. 
   2. staging, qa, dev - each are their own environment, with their own data and their own resources (CPU, Memory, Storage).
2. Uninstall what is running on your asset
   1. You can only do this via the command line  (ie quiet install) on 4.x - see KB on installation options below, the uninstall is in the same doc
3. Prep for doing the install
   1. Autonomo 4 Overview
   2. Autonomo - Asset Category and Asset Sub-Category options
   3. Autonomo - Asset Groups
   4. Autonomo - Auto-provisioning
4. If using UI installer 
   1. See Autonomo 4 - Installation via UI
   2. type \\staging\ in front of your username
      1. 
      2. THIS SHOULD never be given to a customer.
5. If using quiet install Autonomo 4 - Installation via command line (quiet install) 
   1.  ENV="staging" 
      1. Please read the KB link above, you need to fill in the "<>" items as they are required
6. Re-start the Autonomo service
   1. Hit windows key
   2. Type "service"
   3. Open service manager
      1. 
   4. Click on the Autonomo service (one of the listings)
   5. Right-click (or use the icon at the top) and restart the service (you can also stop, then start...does the same thing)
      1. 
   6. This will make the service restart, launches the 2 applications.

Notes

1. Your machine must be Windows, can be 10 or 11; it must have a wifi adaptor and it must be enabled. You must be connected to the internet via wifi or ethernet (if ethernet, you must have a wifi adaptor and it must be enabled)
2. Autonomo logs are in Event View under the "Applications service and logs" folder - it is called Troverlo Autonomo
3. See this doc for an overview of the Autonomo theory of operations - Autonomo 4 - Operational insights (Internal).
4. You must use credentials for a CUSTOMER user, you can't use a Troverlo user's credentials.
5. If you want to test on the Staging environment, replace the "qa" with "staging" above in the two files or in the quiet install command line instructions.
6. If you want to test on the Development environment, replace the "qa" with "dev" above in the two files or in the quiet install command line instructions.

Validation

1. The Asset name will be your hostname + serial number
2. Go to Troverlo portal,
   1. Look on the All Assets page, search for your Asset name, it should be in the active state.
   2. Look on the observations page, search for your Asset name, you should see an observation every 5 minutes (this is the default)

Example Config.json Mark Arrington uses for testing drops and release candidates

1. 1. Observation Window
      1. "dataTranmissionRate": { "VERY_SLOW_data_speed": 60 }, 
      2. Change value of "VERY_SLOW_data_speed": 
      3. Default is 5 min (300)
      4. The unit is seconds
      5. This defines the time Autonomo looks for a unique MAC (TagID) and SSID (Tag Data) combination, and it grabs the highest RSSI (signal strength) in that time window.
   2. Turning on debug logging in event viewer logs
      1. We have 12 logging sources, 6 of them are for debug
      2. We turn these off by default to reduce burden on the Asset
      3. We can turn these on for testing or to do diagnostics on a customer
      4. Add this to the file
         
         1. "logging": { "autonomo": { "debug": true }, "autonomoWifiAgent": { "debug": true } },    
   3. Example

      1. {  
         "logging": {  
            "autonomo": {  
               "debug": true  
             },  
            "autonomoWifiAgent": {  
               "debug": true  }  
         },  
         "dataTranmissionRate": {  
            "VERY_SLOW_data_speed": 60  
         }