https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3014752#M23524 <P>Keith that is a matter of design when it comes to Tuya products.&nbsp; They will each individually store the network information of the wireless router (and SSID) that they were previously connected to. I'm assuming you don't own any of these devices, so this is probably news to you? The only way these devices can usually be reset is by initiating the reset process individually on all of these devices. This involves either depressing the on/off button, or inserting a paper clip (or pin) into a small hole on the device for 5 seconds, until a light begins to flash.</P><P>&nbsp;</P><P>I have done this literally thousands of times, both for myself and for friends, neighbours and families. Normally this isn't a problem, because doing this should reset the stored WiFi data on the device, so when it is added again in the app on a new router, you are then required to enter the new network information (SSID/password) in order to enable the device to connect to the new router.</P><P>&nbsp;</P><P>However, once again, perhaps I should explain that after having done this thousands of times in the past without issues, this simply did not work on this occasion. Moreover, the problems first emerged not due to WiFi interference, but due to regular kernel panics in the router's firmware, hence the title of this thread. This is what TalkTalk originally tried to fix with a new firmware for this router. This proved ineffective and indeed it caused a number of my IOt devices to no longer be able to connect to the network at all, no matter what I tried. It was at that point TalkTalk agreed to send a new router.<BR /><BR />I understand that you prefer to take a methodical approach to solving these kinds of problems. I have no doubt you were a good, competent and highly reliable engineer. But there are (as I'm sure you recognise) many instances where just sheer instinct will win out over logic, or methodology. In this instance, my reasoning led me to conclude that since this was not a networking interference issue to begin with (rather, as I said, it was a kernel panic issue), it was unlikely to have suddenly become one immediately after firstly a firmware upgrade and a subsequent router replacement. Rather, my instinct led me to conclude that it was far more likely that it was of these first two factors that was the culprit, rather than issues with the network.</P><P>&nbsp;</P><P>I nevertheless followed your advice, since rather bizarrely in my view, TalkTalk staff appear to prefer to rely on their customers to help solve other customers problems, rather than have their own qualified (and paid) engineers in situ to tackle what in many instances can be really quite complex networking issues. Moreover, while in many cases your advice would apply, it was clear from the outset that my difficulties were not the result of network interference - and that treating it as such would be likely to lead to an unhelpful blind ally. I agree that it is useful to run these tests, even if just to eliminate this single factor from the equation. But I do not like the implication from either your good self, or from TalkTalk staff that if I didn't treat it as exclusively a network interference issue, no further assistance would be forthcoming. That's a lot of power to put in the hands of one customer. Nor is it very helpful to imply that if it isn't network interference that's to blame, then it must be my hardware, or in other words, my large collection of IOt devices, all of which incidentally worked flawlessly up until the firmware upgrade and the subsequent router swap. How likely do you really feel it is that all 46 of my iOT devices would have developed an identical fault, immediately after a firmware and subsequent router change?<BR /><BR />It doesn't take much reasoning to conclude that the chances of this happening must be infinitesimally low. Moreover, in fairness, the advice you gave can be found repeated ad-infinitum through millions of web pages through a bog-standard Google search. I'm not taking anything away from you, Keith. You are as I said clearly a very competent individual (and clearly fiercely loyal to this company, which I probably understand a little less). But it's clear that if I had followed this chain of reasoning verbatim, as many customers might, it may well have ended with a very unsatisfactory conclusion, even if your advice disproved network interference as a cause. There was clearly a tendency in your conclusions (and perhaps in the conclusions of TalkTalk staff as a result of this), that it was my equipment that was at fault in that case and in that instance, they were under no obligation to act any further. This of course would save them money. However, I don't feel that it is an appropriate role for customers on this forum to essentially write this company a 'free pass', when clearly other more subtle factors may be at play and this advice could potentially lead to a detrimental outcome for the customer who is experiencing difficulty.<BR /><BR />Now as to the 'solution' I uncovered, this is one of those occasions where networking really does defy logic and instead depends on an engineer's instinct, built up over many years. I reasoned that somehow, despite working reliably many, many times in the past and despite having gone through this resent process an equally large number of times, there was something in the 'ether' that was causing the network details of my IOt devices to not be fully wiped. so that even though I was entering the new SSID and password information on the reset devices, there was still something that wasn't being fully reset in this particular hardware combination. I'm tempted to say that one possible candidate could have been the Mac address of the new router I was trying to connect to. For example, while it was possible to change the SSID and the password of my reset IOt devices, it is conceivable that since the old network and the new network/router shared the same SSID, that resetting these devices did not fully reset the Mac address that these devices were previously connected to. Some details on these devices do survive a reset. Like the name, location and device type of each device. But perhaps unless the SSID changes they will not scan for a new Mac address and will assume that the router (and hence the Mac address) is the same as the old router. But I fear you might leap on this to say 'you see, it was your hardware!' There is simply not possible to confirm or refute this either way. It is one possibility among many, in a complex interplay between code, individual devices and the black arts that are usually involved in dealing with complex networking issues of this nature. But it is at least a reasonable assumption that something about my configuration was being 'remembered' and was not fully wiped during the reset process.<BR /><BR />In fairness, you did touch on this briefly in your above post. My concern is that if we had pursued this as purely a network interference issue only (as many customers might be tempted to do), it would simply have amounted to time wasted with no favourable final outcome. However, as a professional courtesy (and as one former networking engineer to another) and to assist in honing your own knowledge of an area of networking, by sharing the results of my experiences with you and with the wider TT customer base - and their engineering team.<BR /><BR />Again, I wish to take nothing away from Keith, or any other contributor to this topic. My intention is simply to broaden the collective knowledge base on these topics, so that other customers in future can benefit from this information. However, it remains a concern that in our ever-changing word TT do not seem to be on top of a revolution that has now been taking place for several years, in the form of the ever-growing use of IOt connected devices that&nbsp; are now increasingly in use by large numbers of the general public. This is no longer a 'niche product', even many OAP's are using IOt smart plugs, lights and other connected devices to help combat the limitations of advancing age and illness. It TT really wanted to demonstrate they were ahead of the curve in this regard, they should perhaps take IKEA's approach and embrace this market wholeheartedly, while providing qualified, experienced engineers to help customers to tackle issues whenever they encounter them.<BR /><BR />PS<BR /><BR />That said, I have sent the data you requested to finally and for all to eliminate 'network interference' as a valid area of investigation for these issues. You can clearly see from what I sent that my network (SONOS) has both high signal strength, low latency and almost no interference. It's literally head and shoulders above all other WIFI signals near my home.<BR /><BR />PS<BR /><BR />Just to update the knowledge base on these topics in case other customers have similar problems, and to demonstrate that even someone like myself can get caught out by doing things the same way I have always done them and expecting the same results every time. It turns out that all Tuya enabled devices have two connection modes. There is the "Smart Connect" mode that basically scans the network around you for any Tuya devices in pairing mode (rapidly flashing light/LED) and that then adds any such device to the app and your network. Then there's the AP (or access point) mode (slowly flashing light/led), which sets up a temporary WIFI access point for you to connect to. AP mode is it seems a preferred mode for when the Smart Connect Mode doesn't work, due to the vagaries of various network configurations.&nbsp; In Smart Connect mode, one simply needs to pick the type of device you wish to add to the app (light, smart plug, smart power strip, camera, motion sensor or whatever), then enter your default WIFI SSID information, then begin a scan of your local environment. If a device is detected in paring mode, The app (Smart Life) will add it and enter your WIFI details automatically on the device and connect your device to the network.<BR /><BR />In AP mode the process is very similar, but rather than simply depress the reset button (or switch) for 5 seconds to enter smart connect mode, once smart connect mode is enabled and the LED/Light is flashing rapidly, at that point you should take your finger off the reset button and then depress this button for a further 5 seconds. At this point the LED/light will begin to blink slowly, indicating that the device is now in AP mode. Once in this mode go to the Smart Life (or Tuya) app, select your type of device, confirm your WIFI/SSID details, then on the following set up page select "Light is blinking slowly" (in Smart Connect Mode, the light will blink rapidly). Once you select this option you will be instructed to connect to the devices temporary AP network. Once done and once you have confirmed that you want to 'always connect' to this network (selecting connect 'only this time may cause repeated connection requests), then hit the back button at the bottom of your Android Screen (or whatever the equivalent in Apple iPhone is) to return to the main Smart Life device setup screen. When you do this, the app will once again initiate a scan for any device in paring mode on this temporary network - and since there is usually only one device on the network, it should connect your device to the app (and your home network) very quickly.<BR /><BR />Part of the fault in this regard lay with me. Because in the past I had never had to use AP mode, I never even bothered to look into it, or consider it this time around. I was barely even aware that this mode existed.<BR /><BR />It still does not excuse the very evident lack of knowledge from TalkTalk staff, who it seems were only too happy to throw in the towel at a very early point, while calling on the services of one of their preferred patrons to write the issue off as network interference, or failing this to claim that despite half the modern world now using this kind of equipment, that they somehow 'don't support IOt devices'. This seems the equivalent to me to an electricity/utility company saying 'they don't support lightbulbs', when a customer can't get any of their lights to work! In the letter of the law this may be correct, but in spirit, it is simply mean!<BR /><BR />However to show goodwill, I would be more than happy to write a guide for your engineers (and perhaps your customers) on how to deal with and how to troubleshoot issues like this in the future. What I will not require however is privileged access to details of anyone's network setup, or any other potentially private or personal information that I don't have any really valid reason to be looking at, particularly when it may be evident that any starting assumptions are likely to be erroneous. Nor will I make any potentially very damaging claims that I am immune to restrictions imposed by the GDPR, or other privacy laws and regulations. (Indeed if I were a TalkTalk manager, I would be concerned at how many other people may have been exposed to similar claims?)<BR /><BR />In any case, TalkTalk and other UK ISPs cannot afford to be left out in the cold when it comes to dealing with IOt connected devices. If you cannot answer customer's queries in this regard, this will only lead to significant dissatisfaction with your service and an increasing flight to more progressive providers.</P> Sat, 13 Jan 2024 03:50:34 GMT jebus1967 2024-01-13T03:50:34Z https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3009387#M22744 <P>Hi I am having frequent router reset issues due to a Kernel panic in my router's firmware.</P><P>&nbsp;</P><P>The message reads as follows:<BR /><BR />1981-01-01 00:00:10 [Error][Alarm-Log] AlarmID:104001,AlarmLevel:Error,Device reset. Cause: System reset due to kernel panic, Terminal:OTHER<BR /><BR /></P><P>The outcome is that all of my Smarthome devices frequently lose their connection, including (most annoyingly my Sonos surround sound system, my HomeAassistant SmartHome hub and My Harmony IR remote control hub. It seems to be a constant battle to keep all my things connected.</P><P>&nbsp;</P><P>I have attached my full system log below. But please can you resolve this issue, either remotely or directly? I reported this problem once before and you sent me another ADSL router. However it was exactly the same make and model (and firmware version) as my existing router and made no difference whatsoever! I am on your full fibre package, but am seriously considering migrating to another company unless these issues can be fixed!<BR /><BR />Please resolve!</P> Tue, 19 Dec 2023 13:50:33 GMT https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3009387#M22744 jebus1967 2023-12-19T13:50:33Z https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3009402#M22745 <P>Hi jebus1967</P> <P>&nbsp;</P> <P>I'm really sorry to hear this.</P> <P>&nbsp;</P> <P>I've made a change to your router firmware, please can you monitor the connection over the next few days and let us know how it compares.</P> <P>&nbsp;</P> <P>Thanks</P> <P>&nbsp;</P> <P>Debbie</P> Tue, 19 Dec 2023 14:14:35 GMT https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3009402#M22745 Debbie-TalkTalk 2023-12-19T14:14:35Z https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3009506#M22752 <P>Thanks Debbi. I will do. But when you say you made changes, can you tell me exactly what you did? You mean you upgraded the firmware? How can I check the firmware version? Thanks.</P> Wed, 20 Dec 2023 04:49:11 GMT https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3009506#M22752 jebus1967 2023-12-20T04:49:11Z https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3009518#M22753 <P>Good morning,</P> <P>&nbsp;</P> <P>Yes, we changed this to a different version of firmware which will resolve this specific issue. We will check back in with you on Friday to see how you're getting on.</P> <P>&nbsp;</P> <P>Thanks</P> <P>&nbsp;</P> <P>Michelle</P> <P>&nbsp;</P> Wed, 20 Dec 2023 06:38:00 GMT https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3009518#M22753 Anonymous 2023-12-20T06:38:00Z https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3009884#M22795 <P>Yes, there are no more Kernel panics from what I can see. But now many of my smarthome devices (I have over 40) are having a lot of trouble both connecting to and staying connected to my WiFi?</P> Thu, 21 Dec 2023 12:04:01 GMT https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3009884#M22795 jebus1967 2023-12-21T12:04:01Z https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3009885#M22796 <P>Hi</P> <P>&nbsp;</P> <P>The firmware will not make any changes to wifi but is solely to stop the kernal panic issue.</P> <P>&nbsp;</P> <P>Try a pin reset of the router, then see if the wifi still drops.</P> <P>&nbsp;</P> <P>Karl.</P> Thu, 21 Dec 2023 12:12:52 GMT https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3009885#M22796 Karl-TalkTalk 2023-12-21T12:12:52Z https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3009889#M22797 <P>Hi. I just looked. The kernel panics are back also.</P> Thu, 21 Dec 2023 12:23:50 GMT https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3009889#M22797 jebus1967 2023-12-21T12:23:50Z https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3009892#M22798 <P>Hi</P> <P>&nbsp;</P> <P>Would you like to swap out the router ?</P> <P>&nbsp;</P> <P>Karl</P> Thu, 21 Dec 2023 12:31:55 GMT https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3009892#M22798 Karl-TalkTalk 2023-12-21T12:31:55Z https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3009893#M22799 <P>I did this once before and you sent me exactly the same router. You can try sending me one I guess, but only if you are certain it's a different and more up-to-date router.</P> Thu, 21 Dec 2023 12:36:51 GMT https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3009893#M22799 jebus1967 2023-12-21T12:36:51Z https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3009896#M22800 <P>Hi</P> <P>&nbsp;</P> <P>I've ordered the router via our manual process and specifically requested the sagemcom model.</P> <P>&nbsp;</P> <P><SPAN style="color:#000000;">Thanks &nbsp;</SPAN></P> <P><SPAN style="color:#000000;">Karl.&nbsp;</SPAN></P> Thu, 21 Dec 2023 12:52:08 GMT https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3009896#M22800 Karl-TalkTalk 2023-12-21T12:52:08Z https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3009961#M22811 <P>Can I ask you to delay delivery until the 2nd of January, or use Royal Mail, so I can go to my local sorting office to collect it? I will be away from home for the holidays until then.</P> Thu, 21 Dec 2023 20:10:14 GMT https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3009961#M22811 jebus1967 2023-12-21T20:10:14Z https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3010006#M22828 <P>Hi jebus1967,</P> <P>&nbsp;</P> <P>I'm sorry, we can't delay delivery but our routers are designed to fit through most letterboxes. If it won't fit through your letterbox then the delivery driver will leave a card with information about arranging a redelivery</P> <P><BR />Chris</P> Fri, 22 Dec 2023 09:54:39 GMT https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3010006#M22828 Chris-TalkTalk 2023-12-22T09:54:39Z https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3010729#M22890 <P>Hi jebus1967</P> <P>&nbsp;</P> <P>Did you receive the router ok?</P> Thu, 28 Dec 2023 10:00:02 GMT https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3010729#M22890 Debbie-TalkTalk 2023-12-28T10:00:02Z https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3010773#M22896 <P>No. As I stated, I am away from home visiting relatives for the holiday. It made no sense for you to send the router before I returned home on January the 2nd. I clearly stated I would not be at home to accept the delivery before then. Although I assume this is what you have done regardless?</P> Thu, 28 Dec 2023 11:32:04 GMT https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3010773#M22896 jebus1967 2023-12-28T11:32:04Z https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3010795#M22898 <P>Staff indicated that they didn't have any way to stop the progress of the router once it was ordered, <a href="https://community.talktalk.co.uk/t5/user/viewprofilepage/user-id/339962">@jebus1967</a>.</P> <P>&nbsp;</P> <P>It was ordered around lunchtime on 21st, but the instruction to delay delivery not picked up before the following day. There was no way to stop it.</P> <P>&nbsp;</P> <P>The instructions about picking it up will be on a card through the door etc.</P> <P>&nbsp;</P> <P>You would need to have mentioned that you were away for the holidays BEFORE staff ordered it, but you seemed to give the go ahead.</P> <P>&nbsp;</P> <P>They were simply being efficient!</P> Thu, 28 Dec 2023 13:18:33 GMT https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3010795#M22898 Gliwmaeden2 2023-12-28T13:18:33Z https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3010803#M22899 <P>First your view was neither asked for, nor is it welcomed. So stick that in your pipe and smoke it! Second, the question was asked, did I get the router? I simply confirmed I did not and stated the reason for this. Simple as. You might imagine it would make sense not to mail things during the holidays, however. (As did I.) If there's a card, I will use it when I return on the 2nd. If not, and it has been left outside my flat door, there's a fair chance it will be taken by a random passing thief. Not that it will be much use to them, but there you go.</P> Thu, 28 Dec 2023 14:10:43 GMT https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3010803#M22899 jebus1967 2023-12-28T14:10:43Z https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3010913#M22908 <P>Hi jebus1967</P> <P>&nbsp;</P> <P>Apologies, the router was ordered before we knew you would be away.</P> <P>&nbsp;</P> <P>Please post back here once you are home and I will re order another router.</P> <P>&nbsp;</P> <P>Thanks</P> Fri, 29 Dec 2023 07:40:53 GMT https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3010913#M22908 Debbie-TalkTalk 2023-12-29T07:40:53Z https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3011132#M22918 <P>Thanks, Debbie. I'll let you know. There's a small chance it might still be there when I return home.</P> Sat, 30 Dec 2023 09:35:52 GMT https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3011132#M22918 jebus1967 2023-12-30T09:35:52Z https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3011590#M22980 <P>Hi jebus1967</P> <P>&nbsp;</P> <P>Ok, thank you.</P> <P>&nbsp;</P> <P>Debbie</P> Tue, 02 Jan 2024 06:58:57 GMT https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3011590#M22980 Debbie-TalkTalk 2024-01-02T06:58:57Z https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3012652#M23139 <P>Hi jebus1967</P> <P>&nbsp;</P> <P>Did you receive the router?</P> Fri, 05 Jan 2024 09:04:42 GMT https://community.talktalk.co.uk/t5/Full-Fibre/Kernel-Panic-leads-to-frequent-router-resets/m-p/3012652#M23139 Debbie-TalkTalk 2024-01-05T09:04:42Z