Whats is wrong with my connection from the 13 march

[krzysztofnowak1972]

Hallo

I have had an UPLINK connection for several months - everything was working properly until probably the update - on the 13 march starts problems . After the updates, I have no continuous data. Charts are broken. There is this error in the Log.

Rejestrator: custom_components.myuplink
Source: helpers/update_coordinator.py:350
integration : myUplink (dokumentacja, Problemy)
First Event: 14 marca 2024 19:38:54 (20 zdarzenia)
Last Log: 08:01:15
Error fetching myUplink data: Error communicating with API: Cannot connect to host api.myuplink.com:443 ssl:default [Try again]

and this

Platform myuplink does not generate unique IDs. ID myuplink_emmy-r-104535-20240104-06722520059720-04-91-62-e0-a6-f4_40940 already exists - ignoring sensor.smo_40_nibef_smo_40_degree_minutes
Platform myuplink does not generate unique IDs. ID myuplink_emmy-r-104535-20240104-06722520059720-04-91-62-e0-a6-f4_44069 already exists - ignoring sensor.smo_40_slave_1_eb101_no_of_starts_eb101_ep14
Platform myuplink does not generate unique IDs. ID myuplink_emmy-r-104535-20240104-06722520059720-04-91-62-e0-a6-f4_44071 already exists - ignoring sensor.smo_40_slave_1_eb101_oper_time_eb101_ep14
Platform myuplink does not generate unique IDs. ID myuplink_emmy-r-104535-20240104-06722520059720-04-91-62-e0-a6-f4_44073 already exists - ignoring sensor.smo_40_slave_1_eb101_oper_time_hot_water_eb101_ep14
Platform myuplink does not generate unique IDs. ID myuplink_emmy-r-104535-20240104-06722520059720-04-91-62-e0-a6-f4_44266 already exists - ignoring sensor.smo_40_cooling_4_pipe_cooling_degree_minutes