06-28-2023 09:32 AM
Was awakened in the middle of the night to my Nest Secure alarm going off, indicating "Your home network is being jammed". Nest app has various "Home Network Jamming" alerts logged. When it occurred, all of my Nest Detect door sensors went offline.
From that point forward, after multiple resets and reconnecting the Detect sensors, the sensors would go offline and come back online approx every 30 minutes, with a "jamming" alert logged. Nothing else in the house has been impacted. Using Google Wifi and the network tests fine and functions normally, with no issues or errors logged. Nine Nest cameras all remain online without issue through all of this.
I did the only thing I could think of, which was to delete all of my Nest Detects from my system. After doing this, I'm no longer getting any "Home network jamming" alerts logged in the Nest app. So it seems to be some interference between the Nest Guard and the Nest Detects.
The day this started, I relocated my home office from one side of the house to the other. My only thought is that the placement of some of my wireless office equipment is now causing interference with the Nest Detects, which is being interpreted as an attempt to "jam" my home network. I would think the system was robust enough to deal with general wireless interference from other common household devices, but who knows.
Appreciate any advice on how to deal with this. I can effectively no longer use my Nest Secure system (for however long Google permits me to use it before they brick it, at least). Arming my system with the Nest Detects active just repeatedly triggers a "jamming" alert. This obviously isn't ideal, whether we're sleeping or away from the home.
06-29-2023 03:09 PM
Hello. It is very unlikely that your other wireless devices would generate interference with the Neat detects. If that were true, you would have the problem regardless of where you located those devices. First thing I would do is factory reset the nest guard device ( I believe you hold down on the number two for 5 seconds). If the problem doesn’t stop, I would sequentially delete each one of your detects (one at a time, each day) and see if you get the interference errors. You need to rule out a rogue detect Bluetooth radio. If you get the error again with one detect deleted, delete another one the next day. Continue to do this until either all of the detects are disabled and you are still getting the error or until one of deleted detects stop the error. If one of them stops the error, replace it with a new one or just keep it out of the system as deleted.
06-29-2023 05:35 PM
I actually ended up deleting all Detects from the system to start (only three total). Have not had any “jamming” errors logged since doing that yesterday. My plan was to add Detects back one at a time and see if the system is still stable after each one.
And I know interference from other devices doesn’t seem likely, but it can’t just be coincidence that after 6 years of using this system without a single issue, this issue started the same day I moved all of my office equipment into a room that contains one of the Detects. I also moved my primary Google Wifi router to a new location as well. Just seems like I’ve perhaps crossed some streams somewhere and something is interfering with the connection of the Detects.
06-29-2023 05:52 PM
Sounds good. I assume most or all of your office devices operate on WiFi and not Bluetooth (except maybe low power wireless keyboards and mice). The detects are all Bluetooth operating at 49MHz or 27MHz (wireless toy freq) and have about a 30ft range depending upon barriers in your home. The base station has 3 radios inside, cellular, WiFi and Bluetooth and all use different frequencies to communicate with the various devices communicate between each other and you. I’m guessing that you have a failing Bluetooth radio in one of your detects. You’ll know soon enough it sounds. Good luck.
06-30-2023 12:14 PM
Well I went about two days without any additional “jamming” errors after deleting the Nest Detects. But I’m away from home at the moment, and just got another “jamming” alert, even with no Detects installed on the system. So I’m really at a loss now, as I was certain it was the Detects causing the issue. I guess next step is a factory reset of the Guard, before I ultimately just unplug it and put it out to pasture.
As for office equipment, I do have two external lights for video calls, and they each have their own wireless remote which operates via Bluetooth. If nothing else, I had those pegged as the culprits interfering with the Nest Detect signals. But with the Detects no longer in the mix, I’m not sure what the issue is.
I also downloaded Fing and spent a considerable amount of time identifying all 47 devices on my home network. Every device is accounted for and there were no “unknown” devices on my network. Fing is literally designed to determine network security and locate concerns, and it doesn’t detect any issues. So perhaps the Guard unit is just failing.
06-30-2023 12:53 PM
Also, I disconnected my Nest system earlier this week with a ring alarm. I did that because we have already committed to Amazon Echo’s throughout the house and since Amazon now owns Ring, the devices are all integrated.
lastly, another way to isolate the base station is to completely wrap it with aluminum foil which will eliminate any wireless signals from reaching the base and rule out signal interference.
06-30-2023 06:45 PM
Well I did a full factory reset on the Nest Guard, and added back one Nest Detect. Within an hour, got another “jamming” alert. At this point I’ve removed Nest Guard from my system entirely. Not sure what else to do but abandon it at this point. Already looking into Eve and Abode. Such a shame that Google took what was the absolute best security system on the market and drove it into the ground. Replacing all my Google equipment from here.
06-30-2023 06:48 PM
Sorry to hear that. But there does come a time when you have invested too much time in a legacy system with dwindling support and parts. I have never heard of your specific problem but I think you should let it go. Good effort though! Good luck on your next system.