Upgraded to 90.1 and Join no longer works. Before this it worked just fine and has for the past 2 years.
from the log
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/joaoapps_join/__init__.py", line 83, in setup
for device in config[DOMAIN]:
KeyError: 'joaoapps_join'
2019-05-06 21:09:03 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform joaoapps_join: Unable to set up component.
I donât use node-red though⌠Join (joaoapps) has worked just fine and even up to a few days ago. I went to migrate over to FCM from GCM and that crapped out with errors so I needed a backupâŚ
Iâm not sure the issue, as it just wonât installâŚ
have you tried moving to the newest version of home assistant? 0.90 is in the middle of the great migration and things may have been screwed up for that platform.
I have also had issues with Join lately. I know it broke on one of the more recent updates but I had already set up Ariel (for actionable notifications) by the time it broke so I never dug deeper into the issue.
In my logging I was getting errors during startup. Re added the config real quick to get the following error:
Tue May 07 2019 08:42:40 GMT-0400 (Eastern Daylight Time)
Error during setup of component joaoapps_join
Traceback (most recent call last):
File â/usr/local/lib/python3.7/site-packages/homeassistant/setup.pyâ, line 156, in _async_setup_component
component.setup, hass, processed_config) # type: ignore
File â/usr/local/lib/python3.7/concurrent/futures/thread.pyâ, line 57, in run
result = self.fn(*self.args, **self.kwargs)
File â/usr/local/lib/python3.7/site-packages/homeassistant/components/joaoapps_join/init.pyâ, line 83, in setup
for device in config[DOMAIN]:
KeyError: âjoaoapps_joinâ
I didnât see anything with breaking changes around this although there was a couple of non join related notify changes in the release notes.
I know you mentioned you do not use node-red but that is definitely a viable workaround if you want to delve into the node-red world. I avoided it for quite a while as I thought Yaml was the way to go and I didnât want to âcomplicateâ things by introducing another point of failure.
I was wrong. Node-Red has taken my Home Automation setup to the next level. Iâm now using the manual alarm component and configured every bit of the arming, notifications (with the ability to control alarm state directly from the notification) and alarm triggers directly from Node-Red.
As I typed my last update, just saw this come through. I was wondering if something had changed on the config side as the config definitely did NOT match what I had configured before. Will give that a shot.
I have not because it didnât make sense. The way the documentation is written it shows one entry for the components and another for the group? I wasnât using group notification so I didnât put that in. Iâll try again when I get home
So turns out, if you have another notify platform configured and you add the join portion, make sure its BEFORE the join platform. I kept getting missing data errors until I moved my fcm-android platform to the top of the notify portion.
This config seems to work:
notify:
- name: android
platform: fcm-android
- platform: joaoapps_join
api_key: API
device_id: ID
device_names: Pixel 3 XL
name: Name
joaoapps_join:
- api_key: API
device_id: ID