Sentinel82 Posted November 6, 2022 Share Posted November 6, 2022 Hi team, I Upgraded to the dumaOS mobile app and have noticed an error popping up “device not found” see screen shot below. To remove this error I had to downgrade to previous version V1.0.0.58 and upgraded back to the latest V1.0.0.64 - look like error not there now thank god. I don’t think I’m gonna use the dumaOS mobile app anytime soon coz I tried twice and error keeps popping up unfortunately! thanks Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted November 6, 2022 Administrators Share Posted November 6, 2022 Glad to hear you fixed the issue, you're seeing this error on the web interface though, not using the app so I'm a little lost on how the app has caused this? Link to comment Share on other sites More sharing options...
Sentinel82 Posted November 6, 2022 Author Share Posted November 6, 2022 Hi Fraser, Sorry, yes the error is seen via the web interface, i thought i try the new dumaOS mobile app, so I did, a day after the error issue appeared when login to web interface for some odd reason. I didn’t have this issue when using the alpha app. So, now everything is ok, I’m confused why? regards Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted November 6, 2022 Administrators Share Posted November 6, 2022 Usually this error happens when a device is deleted from the Device Manager that was added to Traffic Prioritization or the Geo-Filter, does that sound like what may have happened? Link to comment Share on other sites More sharing options...
Sentinel82 Posted November 6, 2022 Author Share Posted November 6, 2022 Hi Fraser, thank you for responding swiftly. It make sense but in this case I didn’t delete anything from the Device Manager that was added to Traffic Prioritization or theGeo-Filter, Regards Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted November 6, 2022 Administrators Share Posted November 6, 2022 Hmm interesting, any settings changes or anything to do with the devices before the error happened? Link to comment Share on other sites More sharing options...
Sentinel82 Posted November 7, 2022 Author Share Posted November 7, 2022 the error happened when I used DumaOS mobile app, as for the settings nothing has changed - no devices issues either. I’ll try download dumaOS mobile once more an get back to you later tonight. thanks Link to comment Share on other sites More sharing options...
Sentinel82 Posted November 7, 2022 Author Share Posted November 7, 2022 I started over again from scratch upgraded to latest version 1.0.0.64 and added console under traffic prioritisation, so far everything is normal no pop up error. Downloaded dumaOS mobile and closed app, open the web interface and same problem error appeared again. So, i deleted the console under prioritised traffic via the dumaOS app on phone and closed app. Login to the web interface and its normal now I’m totally confused. 🫤 Link to comment Share on other sites More sharing options...
Netduma Liam Posted November 7, 2022 Share Posted November 7, 2022 6 hours ago, Sentinel82 said: I started over again from scratch upgraded to latest version 1.0.0.64 and added console under traffic prioritisation, so far everything is normal no pop up error. Downloaded dumaOS mobile and closed app, open the web interface and same problem error appeared again. So, i deleted the console under prioritised traffic via the dumaOS app on phone and closed app. Login to the web interface and its normal now I’m totally confused. That's bizarre, OK let me see if we can reproduce this issue internally and figure out what's causing it. Sentinel82 1 Link to comment Share on other sites More sharing options...
Sentinel82 Posted November 7, 2022 Author Share Posted November 7, 2022 Thank you Liam, regards Link to comment Share on other sites More sharing options...
Baturi Posted November 8, 2022 Share Posted November 8, 2022 18 hours ago, Netduma Liam said: That's bizarre, OK let me see if we can reproduce this issue internally and figure out what's causing it. it has happened to me as well on XR1000 i believe theirs a ways to fix it and 1 way on whats causing it firstly whats causing is it seems that when you do enable priority feature and login into web Interface it causes conflictions for whatever reason secondly how to fix it is by having it still enabled via the app but then manually importing a rule after that head over to interface and error should be gone thirdly what kinda sucks (for now) is if we disable the default Priority Rule and we add a manual rule Traffic priority will not actually work without having default rule enabled 1st and then have your manual rule added Sentinel82 1 Link to comment Share on other sites More sharing options...
Sentinel82 Posted November 8, 2022 Author Share Posted November 8, 2022 @Baturi thank you for adding to this issue, I thought it was just me alone 👍 Link to comment Share on other sites More sharing options...
Kevin.pal Posted December 2, 2022 Share Posted December 2, 2022 When is this getting fixed? Been a month? Link to comment Share on other sites More sharing options...
Netduma Liam Posted December 2, 2022 Share Posted December 2, 2022 8 hours ago, Swgohlegend said: When is this getting fixed? Been a month? Are you having the same problem with your R1? Or are you also using an XR router now? Link to comment Share on other sites More sharing options...
Kevin.pal Posted December 3, 2022 Share Posted December 3, 2022 15 hours ago, Netduma Liam said: Are you having the same problem with your R1? Or are you also using an XR router now? R1 Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted December 3, 2022 Administrators Share Posted December 3, 2022 10 hours ago, Swgohlegend said: R1 It usually happens when a device is deleted from the Device Manager that was currently added to Traffic Prioritization or the Geo-Filter for example. Current Solutions: Factory reset Re-add/connect the device back to the router and give it the same name & device type in the Device Manager To prevent it happening again delete the device from where it has been added before then deleting it from the Device Manager. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now