2023.3.2b1

[Djelibeybi]

What's Changed

• chore: add debug logging to help troubleshoot SOMA Connect by @Djelibeybi in chore: add debug logging to help troubleshoot SOMA Connect #21

Full Changelog: 2023.3.1...2023.3.2b1

---

This discussion was created from the release 2023.3.2b1.

[ziptbm]

@Djelibeybi I've configured this beta build, logger, and restarted as prescribed in this thread, but I do need a pointer on how to pull the logs for this. I've enabled debugging on the integration, reproduced the situation, but I'm not seeing anything in the logs via the HA UI. How should I get you this information from my install?

[ziptbm]

Also make sure that the SOMA Connect block on your Devices screen has the "Provided by custom integration" icon and that the documentation links point here. I notice you can enable/disable debug logging via that screen too. The frontend developers keep adding buttons I never notice. :)

Yes, that’s where I also enabled debug logging. It links here.

[Djelibeybi]

Maybe try completely rebooting your Home Assistant device? Can't think of anything else.

[ziptbm]

Should the config yaml contain custom_components.soma_connect?

I think it currently has only custom_components.soma since that what the text I copied from the HA forums thread.

[Djelibeybi]

Whoops, you're right. The logger configuration should use custom_components.soma_connect. Sorry abou that!

[ziptbm]

Thanks. Changed it, rebooted, but still nothing. Trying a complete system reboot.

Or maybe the debug option in Ui is messing it up? Will try that next if this doesn’t work.

[Djelibeybi]

I've updated the forum thread too, just in case anyone else tries it.

[ziptbm]

ok! What Soma Connect do you use?

I've submitted a support ticket to Soma to see if there's anything else I can do to improve the reporting information from Soma Connect since the Smart Shades app is showing the correct value. I really don't know what else to do here...

[Djelibeybi]

I use a Raspberry Pi 4 running SOMA Connect 2.3.1. There is a new USB SOMA Connect device that may be better, but I've not tried it myself yet.

[ziptbm]

Interesting. I’m on the original pi-based model purchased from SOMA. We will see what they say to my support request then.

In the meantime, should I revert off your beta build?

Or is there anything else I can do or test on this one?

[Djelibeybi]

This beta should be more reliable overall than the built-in integration as it has actual retries and reconnect logic that the built-in version does not. I would also suggest increasing the speed of your blinds if they keep stopping, as usually its caused by the speed being too low for the motor to actually move the blind.

[ziptbm]

Ok, I’ll keep the beta for now.

thanks, I keep them all at 100% and just double checked to make sure.

If I don’t get anywhere with SOMA support, I may just have to try reinstalling. However, this only appears to happen in colder months….

[ziptbm]

I just noticed when a shade does not complete the open request, if I tap/click on the stop button in HA for that shade, the location updates correctly.

maybe it thinks it’s still opening and therefore not updating? I’m mentioning in case there is something there can force the location update. Or this might be my automation workaround. The problem is there are no signals to HA that it didn’t complete the request….at least in the UI.

Soma support has been unhelpful so far.

[Djelibeybi]

The integration has no knowledge of how open or closed a shade is unti it asks the SOMA Connect. When you tell it to open/close or use the slider, it just sends a single command to SOMA Connect that says, "Adjust the shade to this"

My advice would be to time how long a successful opening and closing takes, then use that as a delay in your automation to then "stop" the shade.

[ziptbm]

FYI - I've adjusted my install, which appears to have helped a little - now the devices will just stop, but issuing another open command seems to successfully open them, so I don't have to close them a few percentage first.

Aside from that, SOMA support released a new firmware 2.3.3 in response to my case. Per support, this update should do the following: "The position should update 30 seconds after the motor realizes that it's not moving. After 30 seconds of staying still the motor will stop trying to move and update the position."

I'll be testing this over the next few days. Sharing the latest from SOMA in case this has any implications for the beta build I'm still running.

[Djelibeybi]

The Beta should notice the motor has stopped at most about 30 seconds after SOMA Connect does. Hopefully.

[ziptbm]

Two quick observations from the beta build following Soma's release of firmware 2.3.3. It could be coincidental and of no consequence, but I'm sharing in case it's helpful. The firmware update has significantly improved the position reporting back to HA in combination with this build.

1. One of my devices does not know the model for some reason in HA and shows it as "unknown unknown." Operation wise, I've seen no other issues.

2. Each device in HA shows firmware 2.3.1, even though Smart Shades shows 2.3.3.

[Djelibeybi]

Soma don't appear to have released the firmware publicly yet, and I can't reproduce or test things until they do.

I've seen the unknown model problem with the current version too, it's just what SOMA Connect reports. The version may be similar. Probably why they haven't released it publicly yet. :)

[ziptbm]

Well, I’m not sure what’s going on here but I discovered one of my shades now reporting as open, but it’s physically closed and has been for over 12 hours. The smart shades app shows as closed, but HA is showing closed. Even after reloading the app or asking it to close, it still shows as open. I can grab logs tomorrow, but here’s a screenshot of what it shows from the history on this shade.

I’ll submit to soma too since this may be related to the new firmware.

[ziptbm]

Could the beta build be pinging the devices so much that it impacts the battery?

I've noticed three of the shades are losing battery significantly overnight as well, despite no movement or activity. Soma has indicated that earlier 2S devices had a hardware defect, so they may be sending me replacements....not sure if related, but I'm starting to think there's a bigger issue here as each step to workaround is spurring a new "issue."

[Djelibeybi]

The beta doesn't ping the devices at all, it only talks to SOMA Connect. I have 5 motors in my house and the battery lasts weeks for each of them.

[ziptbm]

Thanks for confirming. I think there’s an issue with my units then, so I’ll push for replacement to see if that helps.