In my experience with the Insignia Voice speakers it is important to understand that the GoogleHome app and almost all 3rd party devices which use it as their GUI are not really as closely coupled as one would assume. By that I mean, Insignia Voice speakers are not really able to tell the generic GoogleHome app exactly what state the device is in at all points in time, especially during setup, so what we see on GoogleHome isn't necessarily what is actually happening on the 3rd party device or even relevant. The GH-app and the device's internal state have diverged, sometimes significantly, which leads to a lot of user confusion, myself included. This doesn't seem to bother Google Inc very much, monopolies are like that.
When properly in sync, GoogleHome can interrogate the device, initiate certain setup tasks, give the device a new name and change other settings used by GoogleHome, indirectly trigger firmware updates, have the device do useful things ...etc, however because I suspect Eric Schmitt and Google really don't feel much obligation to Insignia or maybe any of the device manufacturers, some of these tasks on the device are not reflected accurately by subsequent information displays on GoogleHome (GH). The GH-app is generic and often updated by Google Inc without fully bringing along the various 3rd party devices already sold and in the field.
I have had success updating firmware on my (11), Insignia Voice speakers, (many given to friends & relatives), by keeping this GUI / device divergence in mind. This is especially relevant for those users who like myself want to force a firmware update to happen (from v1.01, v3.10, v3.14, --> newest v3.18)
Initially I try to do a device reset by holding down the rear power button for 20+ seconds. Sometimes this forces the device into the state I need it to be in after answering setup questions in GH-app to connect it to my WiFi network, to force a firmware update: resulting in "LoAd" displayed and blinking on the front. Other times I must do the 20+ second device reset as the second GH-app setup session and go thru two GH-app setup processes before the firmware is updated correctly. FYI - a firmware update file download in progress is indicated on the Insignia Speaker by a blinking "LoAd" displayed on the front, which eventually disappears, displays "Set" then plays a chime sound, (sometimes "Net" is displayed later) which can take a couple minutes,... you must be patient and let the "LoAd" process complete. On other devices if you interrupt a firmware update the device can be left bricked.
When two GH-app GUI setup sessions are required I have to go thru the motions of linking the Insignia Speaker to my local "home" by connecting my iPad running GoogleHome app to the WiFi network emitted by the Insignia Speaker itself then telling GH-app to "add device". This leads the GH-app to ask me setup questions including what local WiFi network selected from a list, I want the Insignia to use permanently (after the setup session). Sometimes after selecting one of my WiFi networks GH-app will ask for the password, but sometimes not maybe because GH-app running on my iPad has cached the password already that I used to setup other Insignia Speakers in my home, I am not really sure.
If it asks for my WiFi password the Insignia Speaker usually goes into the "LoAd" firmware file download state mentioned above during the first GH-app setup session. Wait for this to finish. Expect the GH-app GUI to become de-linked from the Insignia firmware update process. I ignore it's error messages. This first setup session does not really end gracefully from the vantage point of the GH-app GUI, which thinks things have not gone well and says as much, but actually the Insignia Speaker has updated it's firmware if you give it time (a few minutes) to stop displaying "LoAd" and transition to displaying either "Set" or maybe "nEt" .... depends.
You would think this first initial setup task between GH-app GUI and the Insignia Speaker would conclude successfully in a logical step-wise manner, just like the user manual says ... but in my direct experience it most often does not. Never fear, did I mention already I have setup (11) Insignia Speakers successfully to firmware v3.18.
If the first GH-app setup session did display "LoAd" and you waited for it to finish, then you can start a second GH-app setup session with the Insignia Speaker and this time things usually proceed more logically: linking to your local WiFi, asking you GH-app setup questions ...etc. You may have already answered setup questions in the first session which now create confusion with speaker name and other info, in the second session. I was always able to resolve these problems, but it is iterative and difficult to describe or even remember accurately - YMMV.
Sometimes the first GH-app setup session did NOT display "LoAd", but it did sort of lead you to believe the GH-app GUI could at least see the Insignia Speaker over the WiFi. If I remember correctly, in those cases, I began the second GH-app setup session by first factory resetting the device, holding down the rear power/mute button 20+ seconds until the 4 white LED's on the top turned red, began blinking, then stopped blinking. Then I begin the GH-app setup session, answer questions, point it to my local WiFi and the Insignia Speaker displays the "LoAd" and I let it finish downloading the firmware file from internet servers as described above.
In my experience after two disjointed GH-app setup sessions the Insignia Voice Speaker is now at firmware version 3.18 and I can see full time temp displayed, time of day, pair them if I want, simulcast to multiple speakers, use VLC media player (but not iPad iOS VLC) to chromecast to them, even use a wonderful "Chromecast Bridge" plugin installed in my Squeezebox Music Server (LMS) running on my Synology NAS and even LMS on my Raspberry Pi to chromecast music files to the Insignia Voice Speakers !!!
Sorry it has taken me so much digital ink to describe my meandering Insignia Speaker firmware setup methodology, ... but at least you are reading about it, instead of arriving at the destination by trial and error as I did.
Good luck.
