Hi all,
Here's one for a network professional / perhaps an Epson printer expert.
I have an Epson WF-2530 printer / scanner all in one that was working OK over WiFi until recently. Something changed, at the moment I assume that it was the v0.26.03.01286-BT smart hub firmware update that arrived on 19th April 2021, to make things go bad.
The state of things at the moment is that if I reboot the smart hub, the printer manages to WiFi connect to the hub for a short period of time and it works as expected. After a short while the printer then disconnects, it is no longer pingable and it appears that it is no longer on the network.
Things that I've tried:
This problem almost feels like there's been an incompatibility introduced in the last smart hub firmware update coupled to the ancient crustiness of the printer firmware. This is nothing more than a guess to be honest.
The one thing that I've not tried yet is a smart hub reset to factory defaults.
Any ideas anyone / does this sound familiar at all ?
Thanks, Joe
Solved! Go to Solution.
Possibly caused by the firmware issue that people are reporting in https://community.bt.com/t5/BT-Devices/2-4GHZ-and-5GHZ-Bands-BT-Smart-Hub-2/td-p/1907547
To add to the above reply, there was also a fairly large update of Windows 10 together with some ad hoc bits and pieces in April.
We have an Epson WF-2540 connected by wifi to our Smart Hub 2 and although it has not given any problems lately, in the past, we simply powered off the printer, waited a few seconds and powered up again.
Just a point, having started again after a meltdown of my previous computer, I note, because I haven't reinstalled the Epson software, that the driver is now actually a bog-standard Windows job but it does everything we need.
A confirmed firmware bug is / was the cause of this issue.
After posting in https://community.bt.com/t5/BT-Devices/2-4GHZ-and-5GHZ-Bands-BT-Smart-Hub-2/m-p/2159603/highlight/tr... and then subsequently reporting the issue directly to the forum mods via a direct message as requested, details of the problem were forwarded to the hub support team who later rolled out hub 2 firmware v0.26.04.04227-BT to my hub.
Following the firmware update the problem vanished. Fixed!