It’s purely because I tend to shy away from anything in test mode. But if that’s the best way to get things working in the short term, I’ll give it a go! Is this the best (and easiest) way to accomplish this?
EDIT: To clear up any confusion, I was concerned that the current built-in Overkiz integration had problems with later HA releases - entities being renamed, disappearing etc. However, I just updated to the latest HA release and all seems fine with my Somfy blinds, with no changes required. Maybe the built-in integration got fixed somewhere along the line? I’m happy to wait for the integration that includes local control to become “official”.
When I was using the cloud api version, I had created an automation check in Node-RED to check if one of my covers are unavailable. When that was the case I get a push notification.
I get those messages on regular base.
Since 3 days I’m now using the test local api version in my production environment. The unavailable check is still running. And what I noticed is that the covers are still sometimes unavailable.
So does anybody else have unavailable entities of the Tahoma Switch with the local api at some times?
In my case (since 25-07) the covers are 7x unavailable. My Hue lights don’t show unavailable state and there are connected on the same network switch. Also my Tahoma switch is connected by ethernet.
If your use the PR integration, go to the integration panel, click on the 3 dots on the device, and reload, see screenshot, this should repull the pull request to latest version. then just restart HA.
[UPDATE] The official Somfy app kept notifying me the Tahoma Switch got disconnected. This got me thinking: Maybe my connection isn’t stable enough for the Tahoma Switch. I placed it for 12 hours on a different spot and no more disconnections! This might help others as well regarding the ‘unavailable’ states. These are gone now.
BUT: My Garage door isn’t getting the proper states still when my wife uses our oldskool ‘IO key’. Sometimes HA senses the door is being opened, but after closing within a minute the close states isn’t in my logs. I’m going to setup a quick REST dev setup soon for myself to test if the states are correct without this plugin to test. . After running the API via CURL everything is fine, but there is a bug regarding garage Doors and refreshing the closed state…
====
Ok, installed via PR custom component. Installation went flawless (although had to double read my PIN was necessary in the gateway URL.
After a couple of hours I’ve seen a lot of ‘Garage became unavailable’ and ‘Garage Identify became unavailable’. This is the same behaviour for my sun cover. Any idea what’s happening?
Not sure actually where this is coming from. I have seen this in the past, but I thought it was resolved in the last versions. Unfortunately the local API on my TaHoma Switch isn’t functional anymore, so I will have to wait for support…
Will keep an eye out for this issue, and see if I otherwise can add additional logging for this.
That is not possible. I wasn’t able to factory reset my TaHoma Switch, but I have had more issues with developer mode on my box in the past. My parents TaHoma v2 works like a charm for dev mode.
