pywmspro seems sometimes to be stuck…

[zomtec]

Hi Marc,

I have a unfortunately not precisely reproducible behavior:
Sometimes, when I want to manually control my blinds (I have a Zigbee Dimmer light Switch remote which triggers in HA the blind-controls like tilt open/close or move up/down), they react one or two times and then they don’t react anymore for several minutes. During this time, I cannot control ANY blind via Homeassistant. But: when using the Waremas own WebControl App, it works flawlessly.

This behavior seems like the pywmspro lib is stuck anywhere and doesn’t send any new requests to the WebControl? I’m currently using pywmspro v0.4.0.

Is something like this possible? I also had this behavior with earlier versions of the lib.

Have you ever experienced something like that?
I already increased the polling frequency to 300s. As normally I’m controlling the blinds only via HA, polling the state back is not so relevant for me.

[mback2k]

Hi Olli,

I haven't observed this behavior yet. If the library itself would be stuck within some call from within Home Assistant, then HA would log a warning message about that. Did you observe that?

I just pushed a couple of commits which include retrying and throttling logic to improve the stability. Please give it a try, it will be tagged as version 0.4.1.

[zomtec]

I tried to test 0.4.1:

Unable to install package pywmspro==0.4.1: × No solution found when resolving dependencies: ╰─▶ Because pywmspro==0.4.1 depends on aiohttp>=3.14.1 and aiohttp==3.13.5, we can conclude that pywmspro==0.4.1 cannot be used. And because you require pywmspro==0.4.1, we can conclude that your requirements are unsatisfiable.

Hmm.

[mback2k]

Try to upgrade your Python version to at least 3.10: b756e00

[zomtec]

I'm running Homeassistant OS. It has python 3.14.5 installed.

[zomtec]

Ah, it's the current aiohttp version Homeassistant OS itself has installed. It seems to not like having you a newer version required?

[mback2k]

Hm, I am pointing to the same version as the dev branch of HA. Maybe try the beta release?

[zomtec]

Ah, that should explain it. I'll wait for the release, I don't like updating my productive environment to the dev branch. ;)

[zomtec]

I tried to follow your code implementation. This may be a situation causing my observed behavior?

pywmspro/wmspro/webcontrol.py

Line 51 in c159640

async with self._common_lock:

You send the http post request and lock it until the request is finished.
As far as I see, there is no explicit timeout for the request defined? Perhaps it may make sense to define i.E. a 10s timeout in case anything goes wrong with the request?

[mback2k]

Good point, I will add a timeout.

[mback2k]

@zomtec please test the new version 0.4.2 which should now be compatible with Home Assistant 2026.7.

[zomtec]

Works so far for me. Thanks.

But one thing what happened today: after restart of HA (after updating the manifest.json): the raw rotation input_number of one of my blinds switched to +128 (the current_tilt_position was equivalently at -34%). But it was only one single blind and after moving it, it was correct again. 🤷‍♂️

I don't know what to do with this, except adding an additional check in my evening automation to check for a valid current state. (When closing the blind in the evening but keeping the slats a bit open, I want to prevent opening them again, when they have been previously closed manually: I check the current state. The -34% broke that and the blind didn't move at all. So now I have an additional check for an invalid current state.)

[mback2k]

@zomtec I can only imagine an issue in the WMS WebControl pro or it's API. +128 is outside of the standard supported range of -127/127. Was there maybe an update to your WMS WebControl pro?

Regarding the new version of pywmspro, I will now create a PR to Home Assistant to get it merged then.