Soma Connect - sudden behavior changes

Third party integrations
1

I upgraded to 2025.3.3 today, and I don’t know if that had anything to do with it, but my Soma Tilt devices have gone nuts.

I have 3 units. They have always been tilt devices (i.e. set_cover_tilt_position) and device class of blind. Today, one of the 3 switched to a device class of shade and needed to be controlled by position (set_cover_position). This of course broke my automations.

After some troubleshooting (restart HA, reinstall integration, etc), finally restarting the actual Soma Connect and reloading the integration got “lefty” back to a blind/tilt. However, all is not well, because more often than not, one of the 3 will fail to open/close and I get the following error:

Error while setting the cover position (None): READ ONDISCONNECT

Usually…it’s one of the two that kept their blind state in the earlier ordeal. Sending the command again usually causes it to work that second time.

Any ideas what might be going on here?

2

In case it helps anyone else…I tried to move the Soma Connect thinking maybe it was a interference issue. After moving it, the Soma would not come online…I could ping it, but I kept getting “connection refused”.

I finally flashed the Soma software to a new flash drive, and installed that into the Connect, and now it’s working fine again. I guess something was corrupted on the flash drive.