You obviously picked an experimental 3rd party integration, and you blame home assistant.
Read this release note
Are you by any chance running version 3 of the firmware on your weather station are you?
If you aren’t, you should revert to the previous version of the integration. 1.3.7 I think. Or there is a 1.5.0 version now. (5 hours ago)
But above all, post to schizza’s GitHub. It’s the place to get help. And I see you are getting help there. So stop moaning.
No, I have the basic version 1.0 firmware. There probably isn’t another version, I wrote about Sencor or Fast and no answer. I’ve tried 1.3.5, 1.3.7 and 1.4.0 and none of them work now. Version 1.3.5 worked with core HA 2025.2.3. But no version works on them anymore.
That is not true. Read your own issue on their GitHub
I won’t argue whether the firmware is v3.0 or not. I wrote an email to Sencor and Fast and I didn’t get any response. I didn’t upgrade the weather station, so the basic firmware is v1.0. If the firmware was v3.0, why doesn’t the weather station upgrade itself or don’t I get a message to upgrade it?
Probably because you bought a device that works that way… 
What I meant was that 1.4.0 of the integration does work with ha 2025.2.4.
Please use the author’s GitHub.
I reinstalled “Orcale VM VirtualBox” from scratch, created a virtual PC according to the instructions: “Windows - Home Assistant”, started Home Assistant. I installed Tuya Integration and the like, then also through HACS the “Dahua” integration, which works without problems, then I installed the “Sencor SWS 12500 Weather station v 1.5.1” integration, which does not work again. Super congratulations to the developer!
So I’ve now found out that version 1.3.5 is functional, but how long will it be? Will it survive the next HA update?
What part of deal with the developer on GitHub do you not understand.
You need to change your attitude.
I think that the HA team should change its stance so that the integration and the own integration are compatible with HA, otherwise it will cause constant problems. As for the developers of their own integrations, they should listen to HA so that they can adapt their errors according to the properties of the core HA and not so that users who buy that integration will have to worry. As I already wrote, I am not a developer or a programmer. It is true that I am interested in this issue, but if there are too many problems, I do not enjoy using this HA. Now I am still hesitating whether to buy the “Home Assistant Connect ZBT-1” and Zigbee appliances and sensors. It is a pity that the weather station also does not allow communication via Zigbee, maybe it would be easier.
By the way, why don’t the developer updates work?
Whenever possible the HA core developers provide deprecation warnings to all (both core and custom) integration developers so they can prepare for upcoming changes to HA interfaces they might rely on. They maintain an extensive Home Assistant Developer Docs website, which includes a blog where they discuss changes developers might need to be aware of in detail.
Your expectations, with regard to this device, are unreasonable. Zigbee, Z-Wave, and Matter, for instance, are all standards that users of any platform(not just Home Assistant) should be able to rely on to work smoothly. The device you purchased uses its own proprietary protocol, makes no claim to work with Home Assistant, and was not intended by the manufacturer to be integrated with Home Assistant, as far as I know. That protocol just happened to be reverse engineered by someone in their spare time, who was nice enough to provide users with the open source code and directions to set it up themselves in Home Assistant.
By the way, why don’t the developer updates work?
You’d have to ask the custom component developer, on his Github page. As has been explained over, and over, this isn’t a Home Assistant issue. It can’t be fixed or even properly troubleshooted here. You need someone who has familiarity with the integration specific code, and maybe access to the device (or a similar device at least). I’ve been following your posts on the developer’s github, and I think it’s possible there are language barriers between you and them. If I were you, I would go back and re-read everything that’s been shared with you there again, and follow up there with requests for more info if you don’t understand what’s been said or don’t think that it has helped. Be prepared to provide logs and configuration details.
You are really barking at the wrong tree!
You haven’t bought anything. Home Asistant is free. The custom integration is free.
Deal with the developer of the custom integration on his github.
This topic has been closed as you are not listening and this circular discussion serves no purpose.
You have been repeatedly told this is not an issue with Home Assistant. It is the third party integration developer’s responsibility to to keep up with changes to Home Assistant. Deal with them not “Home Assistant IT support”.
