Home Assistant + Homekit + Mysa = Failure

I've used Home Assistant in the past, but a year ago, I moved into a new house, and decided to give pure Homekit a try. After a year, I realize that I want to move back to HA.

The one major hurdle is I have two Mysa thermostats. As I have electric baseboard heating, that's really my only option unless I want to go toward another thermostat and using relays. So, I'm working on getting the Mysa into HA using the Homekit Controller, but am having no luck. Most of what I've read either suggests adding it using the Mysa app, then you'll see it appear in Integrations, or some say to use the Mysa app, but not complete the process, just go far enough to get it to show up in HA, the add it to HA. The problem I have is, I can never successfully add it to HA. Either HA will say that the device can no longer be found, or that it's already paired with something else. I've deleted the thermostats out of Home and the Mysa app over and over, and have reset the devices to repair at least a dozen times so far.

Anyone out there successfully pairing Mysa thermostats with HA, and what exactly is the secret dances to it all to work. I have 2 thermostats so far, and if I can get this to work, will probably be adding at least 3 more.

Posted Oct 26, 2020, 2:32 PM UTC

18
mnoah66•

Just went through this yesterday. I reset the MYSA then added it with the MYSA app (it prompted me to connect to HomeKit which I complied with). After trying to pair it to HA, HA said it was already paired with another device so I opened up HomeKit on my iPhone and removed the MYSA accessory. I then restarted the HA server and was able to pair it into HA.

HOWEVER, after a few hours, HA has stopped receiving data from the MYSA and vice versa. It seems that once the MYSA goes to idle it just stops altogether. Checking my core logs, I get the following error: AccessoryDisconnectedError( aiohomekit.exceptions.AccessoryDisconnectedError: Timeout while waiting for connection to device)

Not sure how or where to start troubleshooting.

​

Edit: Found this on MYSAs support page that to do a FULL reset you have to flip the breaker after the smiley face step. I didn't do that...will try later and hope that solves it.

https://help.getmysa.com/hc/en-us/articles/360030621572-Mysa-was-connected-but-now-it-s-not-How-do-I-reconnect-Mysa-#:~:text=The%20following%20are%20some%20steps,used%20to%20connect%20with%20Mysa.

1
daveonkels•

I'm using MYSA successfully with HA but the trick was to 1) reset, 2) pair with the Android app to get the device online since it uses Bluetooth to load the wifi network rather than Homekit, 3) input the Homekit code into HA. I happened to have an Android phone in a drawer that I could use.

1
mnoah66•

Interesting. I have an android laying around too so I’ll give that a go. Does your MYSA integration stop communicating after some time? Or has it been steady?

1
daveonkels•

Steady as best I can tell. I don’t make a ton of changes since it’s floor heat and setup on a schedule but seems to be reliable.

2
mnoah66•

Looks like your android trick is working. Hasn’t dropped off communicating with HA like it did previously.

2
daveonkels•

Glad to hear!

1
Bismarck_86•

I have two of three of them and I didn’t have a problem moving them. But I did it like two months ago, probably it’s the HA version that is bugging them while you add them new. And I like them a lot also in HA, they report flawless all the information

1
RouterMonkeyOP•

Follow up:

Nothing I tried would work. No matter what steps I tried, in whatever order, the Mysa was also said to have already paired with something or unable to be found. I tried the reset then flipping the breaker trick a few times, no luck.

Today, being the weekend, I decided to fight with it till I won. A bit more Googling lead me to some threads about disabling HomeKit autostart, to allow the z-wave network to come up first. This resolved some issues with some HomeKit devices not being seen by HA correctly. WTH, it's worth a try. Well, I made the config changes, rebooted HA, and both Mysas were waiting to pair as soon as it came back up, and I was able to pair both without any issues.

So, here's the code I added, YMMV.

discovery:
homekit:
auto_start: false
automation:
- alias: 'Start HomeKit'
trigger:
- platform: event
event_type: zwave.network_ready
- platform: event
event_type: zwave.network_complete
- platform: event
event_type: zwave.network_complete_some_dead
action:
- service: homekit.start

1