Jump to content
RESET Forums (homeservershow.com)

LUMA and Sonos


pk1
 Share

Recommended Posts

As LUMA's wireless mesh devices start to roll out, I imagine this topic will come up more than once so permit me to relate my experiences getting LUMA to play nicely in the sandbox with Sonos.  Because there is so little literature on the topic at this point, my experience (and ultimate success) was mostly the product of trial and error.  My setup is the ubiquitous antiquated MI424WR Verizon Actiontec cable modem/router.  I have the following paired Sonos components:  2 sets of paired Play 1s, 1 set of paired Play 5s (1st edition), and 2 Sonos Connects.  With the new wireless network, I had previously removed the Ethernet cable from my Play 5 located closest to the router.  Once I installed all 3 LUMAs from my newly arrived 3-pack, and without any adjustments to my Verizon router settings, my Sonos app could no longer find the Sonos network.  I tinkered with a variety of solutions, getting one pair of Play 1's to be recognized when my phone was in close proximity to them.  However, as soon as I walked about 30 feet away, the phone app. could once again no longer find the Sonos network.

 

Well to make a long story short, with several solutions proving to be dead ends, I decided to plug an ethernet cable from the back of one of my Play 5 stereo pairs (the one that had formerly been plugged into the Actiontec router before Sonos went completely wireless) into the OUT port on the back of the LUMA,  The In port of that device was plugged into my Actiontec router. All my Sonos components magically appeared.  Moreover, I was able to travel throughout the house and even into my backyard without losing the connection to the Sonos components. I note that I did this first without disabling the wireless on the Actiontec router.  That's the curious thing about LUMA - although you can run it as your only wireless, it appears you don't have to. Effectively, this means you can have some components on your 192.168.1.XX Actiontec DNS range, and others on the LUMA 192.168.55.XX range.  

 

But my next test was to see if it would still work when I turned off the wireless on the Actiontec router. (I note that keeping the Actiontec wireless enabled effectively circumvented LUMA's ability to cut off internet service; devices would just reroute to the Actiontec router.)  So I wanted to see if I could maintain my Sonos connection after disabling the wireless on the router.  With the Play 5 now plugged into the LUMA and the LUMA, in turn, plugged into an open LAN port in the back of my router, I was pleased to see that the Sonos app continued to work even after the Actiontec wireless was set to off.  

 

In sum, the simple, if not intuitive, solution turned out to be the best.  No resetting the controllers or fooling around with the DNS server ended up being necessary.  Just a spare ethernet cord was all it took. 

 

Incidentally, while I am not blown away by the speed of the LUMA (which never seems to change according to the app and seems to be about double what my Speedtest app says it is), I am impressed by its range.  I have a 4000 square foot house with very poor wifi range using the Actiontec router.  With the 3 LUMAs strategically placed on the left, center and right sides of the houses, I was able to get excellent coverage throughout the house and a good 50 feet into the backyard.  That alone has made the purchase worthwhile.  

 

Hope this helps.

 

 

Link to comment
Share on other sites

As LUMA's wireless mesh devices start to roll out, I imagine this topic will come up more than once so permit me to relate my experiences getting LUMA to play nicely in the sandbox with Sonos.  Because there is so little literature on the topic at this point, my experience (and ultimate success) was mostly the product of trial and error.  My setup is the ubiquitous antiquated MI424WR Verizon Actiontec cable modem/router.  I have the following paired Sonos components:  2 sets of paired Play 1s, 1 set of paired Play 5s (1st edition), and 2 Sonos Connects.  With the new wireless network, I had previously removed the Ethernet cable from my Play 5 located closest to the router.  Once I installed all 3 LUMAs from my newly arrived 3-pack, and without any adjustments to my Verizon router settings, my Sonos app could no longer find the Sonos network.  I tinkered with a variety of solutions, getting one pair of Play 1's to be recognized when my phone was in close proximity to them.  However, as soon as I walked about 30 feet away, the phone app. could once again no longer find the Sonos network.

 

Well to make a long story short, with several solutions proving to be dead ends, I decided to plug an ethernet cable from the back of one of my Play 5 stereo pairs (the one that had formerly been plugged into the Actiontec router before Sonos went completely wireless) into the OUT port on the back of the LUMA,  The In port of that device was plugged into my Actiontec router. All my Sonos components magically appeared.  Moreover, I was able to travel throughout the house and even into my backyard without losing the connection to the Sonos components. I note that I did this first without disabling the wireless on the Actiontec router.  That's the curious thing about LUMA - although you can run it as your only wireless, it appears you don't have to. Effectively, this means you can have some components on your 192.168.1.XX Actiontec DNS range, and others on the LUMA 192.168.55.XX range.  

 

But my next test was to see if it would still work when I turned off the wireless on the Actiontec router. (I note that keeping the Actiontec wireless enabled effectively circumvented LUMA's ability to cut off internet service; devices would just reroute to the Actiontec router.)  So I wanted to see if I could maintain my Sonos connection after disabling the wireless on the router.  With the Play 5 now plugged into the LUMA and the LUMA, in turn, plugged into an open LAN port in the back of my router, I was pleased to see that the Sonos app continued to work even after the Actiontec wireless was set to off.  

 

In sum, the simple, if not intuitive, solution turned out to be the best.  No resetting the controllers or fooling around with the DNS server ended up being necessary.  Just a spare ethernet cord was all it took. 

 

Incidentally, while I am not blown away by the speed of the LUMA (which never seems to change according to the app and seems to be about double what my Speedtest app says it is), I am impressed by its range.  I have a 4000 square foot house with very poor wifi range using the Actiontec router.  With the 3 LUMAs strategically placed on the left, center and right sides of the houses, I was able to get excellent coverage throughout the house and a good 50 feet into the backyard.  That alone has made the purchase worthwhile.  

 

Hope this helps.

Welcome to the forums!

 

Thanks for taking the time to share, I am sure this info will help someone down the road.

Link to comment
Share on other sites

Thanks for the write-up!   I also have an extensive Sonos network, and have been concerned about the ability to play nice.  While I'm still leaning towards cancelling my order, I am looking for some real reviews and comparisons of speed and range against some of the better standalone routers out there.

 

So in your case you have to put one of your Play 5's next to the Luma?   What if you remove the cable, does it not work?    I do have a Sonos Bridge, so I'm assuming as long as that is plugged into the Luma it would serve the same purpose.

Link to comment
Share on other sites

I think I know what went wrong with your Sonos setup.  I can hopefully explain this using snippets from your original post.

 

As LUMA's wireless mesh devices start to roll out, I imagine this topic will come up more than once so permit me to relate my experiences getting LUMA to play nicely in the sandbox with Sonos.  Because there is so little literature on the topic at this point, my experience (and ultimate success) was mostly the product of trial and error.  My setup is the ubiquitous antiquated MI424WR Verizon Actiontec cable modem/router.  I have the following paired Sonos components:  2 sets of paired Play 1s, 1 set of paired Play 5s (1st edition), and 2 Sonos Connects.  With the new wireless network, I had previously removed the Ethernet cable from my Play 5 located closest to the router.  Once I installed all 3 LUMAs from my newly arrived 3-pack, and without any adjustments to my Verizon router settings, my Sonos app could no longer find the Sonos network.  I tinkered with a variety of solutions, getting one pair of Play 1's to be recognized when my phone was in close proximity to them.  However, as soon as I walked about 30 feet away, the phone app. could once again no longer find the Sonos network.

My guess is your Sonos system is running in BOOST mode.  This appears to require one Sonos device is hardwired to your network (which is what you originally had setup with the Actiontec).  As soon as you removed the ethernet cable your Sonos system was isolated.

 

I can't explain why you were able to connect to one pair of Play 1's when you were within 30 ft except they may have some built in intelligence with the APP.  This may be a fallback to allow you to get into the system and reconfigure the setup (say to switch from BOOST to Standard setup).

 

 

Well to make a long story short, with several solutions proving to be dead ends, I decided to plug an ethernet cable from the back of one of my Play 5 stereo pairs (the one that had formerly been plugged into the Actiontec router before Sonos went completely wireless) into the OUT port on the back of the LUMA,  The In port of that device was plugged into my Actiontec router. All my Sonos components magically appeared.  Moreover, I was able to travel throughout the house and even into my backyard without losing the connection to the Sonos components. I note that I did this first without disabling the wireless on the Actiontec router.  That's the curious thing about LUMA - although you can run it as your only wireless, it appears you don't have to. Effectively, this means you can have some components on your 192.168.1.XX Actiontec DNS range, and others on the LUMA 192.168.55.XX range.  

As soon as you plugged the Play 5 into the Luma with the ethernet cable you re-established the connection between the Sonos system and the Luma network.  It did not matter that the ActionTec router was still transmitting it's own wireless network since the Sonos system was now connected to the Luma network.

 

In regards to the comment about the Luma and Actiontec being on different subnets and having some components on one subnet while others are on the other subnet.  I am pretty sure that it won't work that way.  I don't have a Sonos systems but I am willing to bet as soon as you plugged that ethernet cable into the Luma router the Sonos system reconfigured all the remote devices onto the same subnet.  If you wanted to be sure you can look at the devices listed as connected to the Actiontec subnet and also to the Luma subnet and I think you will find all the devices were on the Luma network.

 

 

But my next test was to see if it would still work when I turned off the wireless on the Actiontec router. (I note that keeping the Actiontec wireless enabled effectively circumvented LUMA's ability to cut off internet service; devices would just reroute to the Actiontec router.)  So I wanted to see if I could maintain my Sonos connection after disabling the wireless on the router.  With the Play 5 now plugged into the LUMA and the LUMA, in turn, plugged into an open LAN port in the back of my router, I was pleased to see that the Sonos app continued to work even after the Actiontec wireless was set to off.  

That worked because of my explanation above.  The Sonos system configured itself to use the Luma network and not the ActionTec.

BTW, if you don't want to turn off the ActionTec wireless radio and you don't want anyone connecting to it, just change the password.  Anyone who previously was using it will now need a new password to get back on it.

 

 

In sum, the simple, if not intuitive, solution turned out to be the best.  No resetting the controllers or fooling around with the DNS server ended up being necessary.  Just a spare ethernet cord was all it took. 

 

Incidentally, while I am not blown away by the speed of the LUMA (which never seems to change according to the app and seems to be about double what my Speedtest app says it is), I am impressed by its range.  I have a 4000 square foot house with very poor wifi range using the Actiontec router.  With the 3 LUMAs strategically placed on the left, center and right sides of the houses, I was able to get excellent coverage throughout the house and a good 50 feet into the backyard.  That alone has made the purchase worthwhile.  

 

Hope this helps.

The solution worked because it was how you had your Sonos configured.  It needed the ethernet cable to have access to the Luma network (just like it needed the ethernet cable to have access to the ActionTec network).

 

4000 sq ft house is a lot to cover with one router so the Luma mesh network sounds like a good solution for you to improve the coverage.

 

Thanks for posting here in the forums.  If I have any of my assumptions wrong please let me know.  If someone else stumbles across this thread I want to be sure that they can find the answers they are seeking.

Link to comment
Share on other sites

Although not required I still have a Sonos Bridge which works very well to bridge my WiFi and Sonos networks. Your WiFi devices need to have a path to get to the Sonos system/network. Thanks for sharing your experience.

Link to comment
Share on other sites

I just went through the Sonosnet part.  If your Sonos has a hardwired connection to your router it is supposed to use Sonosnet - Sonos wireless mesh network on a channel that you can assign it through advanced settings.  If the connection is wireless to the router it is supposed to go through your wifi network and not create its own mesh network.  This was an update early last year I believe.  If you happen to cable into one somewhere down the line to use as say an access point I've read it can get confused, consume bandwidth while trying to do both mesh and wifi.  

Link to comment
Share on other sites

I will add it appears once the Sonos changes to wifi instead of Sonosnet it's a bugger to get it to go back to Sonosnet.  I had to literally reset all my Sonos units to get them to stick to the Sonosnet network and not sneak over to wifi when they wanted.  

Link to comment
Share on other sites

  • 2 months later...

Brilliant! I hooked up my downstairs first gen Play:5 to a Luma with an ethernet cord, and my problem was solved. Thanks for saving my relationship with Luma. 

Link to comment
Share on other sites

  • 2 months later...

Correction - It stopped working again. I finally bit the bullet and called Luma. We created a static IP address for my sonos bridge, which did the trick. It seems to work wirelessly with no need for ethernet cord. For now. I'll update if it stops working. 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Similar Content

    • Dave
      By Dave
      I learned this at CES 2018 and First Alert didn't like it.  Didn't like it at all.  In fact, they brought over someone else for me to speak with so they could try to save face and hush me up.
       
       
      Luma was once a darling in the Wi-Fi industry.  Well, all the way up to releasing their product.  It seems they couldn't fill orders fast enough and when they did the folks waiting the longest still stood empty handed.  It was feature short and owners and fans quickly realized it would be consumed by another product.  It didn't have the features or the customer service to keep up with companies like Eero and Netgear.  Fast forward to January 2018 and First Alert now is the proud owner of a mesh Wi-Fi company!  Can you guess what they will put in their smoke alarm next?
       
      I ask the person I was handed off to, "Why no announcement?"  Answer, "We don't announce these type of things."  He air-quoted, "Corporate."  I grilled him more and encouraged an announcement if for anything, the people who have purchased Luma devices.  They deserve to know.  I got nowhere with First Alert.  They were not going to budge and politely asked me not to write it.  No scoop for you!  I like this company so I obliged.  Did they follow up? No. Did they thank me? No.  I don't need a thank you but I kept my word.  Well, I did call @jcollison to file the report with him so someone would believe me when the news finally did break.  I knew it would, but I made a promise to a company, and I kept it.
       
      This is a good fit for Luma because as I stated earlier they were no match for their rivals.  I don't know if it is a good fit for their customers, early adopters, and fans however.  I sold my Luma gear so nobody contacted me telling me the roadmap.  Did they contact you?
      It could be a better product now, I have no idea! I spoke with them at CES 2017 and they were excited for the new year but with reservation as they knew the road behind them was bumpy.  
       
      But hey, now we can have a smoke alarm with Wi-Fi in it!   Let's just hope they don't do anything silly like put Alexa in it or make it a speaker.  
      https://www.firstalert.com/product/safe-sound/
       
       

       
      Oh, guess I'm too late on that request.  I hear it sounds "Onederful."  All kidding aside, I like the idea of Wi-Fi in a product like this.  Their roadmap will bear that fruit.  I don't like "Alexa in the sky" and the sound of this speaker at CES was abysmal and will not compete with Sonos and all the new countertop smart speakers.  Maybe it was just show floor noise but let's hope they improve upon that sound.
       
      They hurriedly packaged the Luma app into their own in order to demo the Wi-Fi enabled Smart Smoke Alarm Combo device.  So hurried in fact that they failed to remove a  Luma Logo.  Ya, busted.  I knew prior to that though.  I kept telling the demo person that this app looks familiar.  "Isn't this the Luma app I asked?"  Wow, did she freeze and stammer throughout the rest of the demo.  "This looks like the Luma app," I proclaimed, and then boom.  One little screen deep into the app. Luma Logo. BUSTED!!!
       
      Not even a demo unit. You think they would at least send me a demo unit to hush me up!
       
      There is a bright side for you Luma fans!  
      You can get a 3 Pack for $99
      https://computers.woot.com/offers/luma-whole-home-wi-fi-router-3-pack-9?ref=w_cnt_wp_1_16

       
      Source:  Me, at CES 2018
      These guys published first though. I kept my word.
      https://www.axios.com/scoop-first-alert-buys-wifi-system-maker-luma-1515771029-93e9ef01-4345-4f42-884b-b86b1f437628.html
       
    • cmccomas
      By cmccomas
      Hi guys and gals, new listener to the pod cast and first time posting here.  Anyway I finally took delivery of my Luma 3 pack.  So far it’s been a bit bumpy road like the rest of you. I can vouch for it’s speed when it’s actually working!  I have mine setup behind a Sophos UTM, I allow TCP 4242, TCP 4505 and TCP 4506 out so that they can connect back to the cloud.  The odd thing is that they seem to be working in bridge mode!  This is something I want them to do but it’s something I don’t think they should be doing with this current firmware. Is anyone else getting behavior like this? Any ideas as to why?  I also get about 3 days of use before they decide to lock up.  Not sure if this is a bug in the internet pause feature or they just wonk out.  It doesn’t kill my wired network traffic just the wifi. The only way to restore connectivity is to unplug them one at a time. Just for the record I have not used the pause feature so it is not user error on my part!
       
      Side note, I see a lot of dropped packets in the logs of Sophos and backup pfSense box.  I will snoop around in the log files and check wireshark this weekend and see what I can see.  Anyone have any ideas/solutions or similar experiences?
       
       
       
       
    • boats4chris
      By boats4chris
      New Luma owner here. Have to say that I am not that impressed with the Luma system as a whole. I like the WiFi signal, but frankly that is only a part of a home network. I am really disappointed in the lack of visibility to the system. I get that it might gear more toward "Plug and Forget" type people, but you still have to have some visibility to troubleshoot problems.
       
      So... here is mine...
       
      Setup the new Luma 3-Pack last night throughout my house. The main Luma is connected to the cable modem on the in port and the out port is connected to an 8 port 10/100/1000 switch (#1). It seems like the other wired devices on the switch are working fine. I have another hub/switch (#2) connected to #1. I have a Tivo box that I plugged into #2 and it does not seem to pick up a DHCP address.
       
      For troubleshooting purposes I moved the Tivo connection to #1 and still no DHCP. I reset the master Luma (pulled the power) and it eventually came back online and did offer a DHCP address to the Tivo. I thought that was the trick and so I reconnected Tivo back to #2 and no DHCP. So... I connected back to #1 and still no DHCP. I ran out of time to try the whole reset Luma thing again, but I was wondering if anyone else has seen issues with DHCP and wired devices? It seems like once it sends them out, it does not try again. 
       
      It is also very disappointing that there is no visibility to any of the configuration aspects of the Luma settings. Like how long the lease time is, etc.
       
      I guess I might have to spend the weekend using wireshark to see if I can see what is going on, just wondering if anyone else has worked through any DHCP issues with them.
       
      On a side note... very nice site, lots of great information! Thanks!
       
×
×
  • Create New...