You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before reporting an issue, there are a number of reasons why this Homebridge plugin may not be working. Here's some steps to follow to work towards a fix:
Make sure you're Homebridge config.json file is properly formatted (see the default sample file here) and the settings for this plugin are correct for your Alarm.com account.
Refresh the accessories cache by starting Homebridge with the -R flag: homebridge -R
If your homebridge is set to start on boot, you may need to disable that first and start it manually on the command line to refresh the cache and see if the problems continue while in this setup before restoring the start on boot setup.
Try deleting the cachedAccessories file:
a. FIRST, stop Homebridge (this is important);
b. locate and delete the ~/.homebridge/accessories/cachedAccessories file;
c. start up Homebridge again and test for success.
Make sure that all parts of the plugin have been updated to their latest or expected versions, use the following command: sudo npm list node-alarm-dot-com
Once you have submitted the ticket, you can also visit the Slack channelDiscord channel (moved from Slack to Discord) to see if others are working on the issue already.
As a last resort (not recommended due to the destructive nature), the following steps can help reset your entire Homekit/Homebridge integration:
NOTE: this will remove all Homebridge based accessories, their locations in the rooms of Home.app, their automations, scenes, configurations and any related data stored in Homekit. BE VERY CAREFUL!
Remove Homebridge from HomeKit in the Home.app on your "iDevice".
Stop Homebridge.
Delete the accessories and persist folders in the ~/.homebridge/ folder.
Edit config.json settings:
a. changing the homebridge user name (just change one character or number in that hex style sequence, without removing any of the colons);
b.remove any unwanted plugins from the accessories and platforms sections.
mkormendy
changed the title
BEFORE ALL ELSE... (Guidelines for Troubleshooting)
BEFORE ALL ELSE...<br>(Guidelines for Troubleshooting)
Jan 21, 2020
mkormendy
changed the title
BEFORE ALL ELSE...<br>(Guidelines for Troubleshooting)
BEFORE ALL ELSE... (Guidelines for Troubleshooting)
Jan 21, 2020
mkormendy
changed the title
BEFORE ALL ELSE... (Guidelines for Troubleshooting)
BEFORE ALL ELSE...
Jan 21, 2020
mkormendy
changed the title
BEFORE ALL ELSE...
BEFORE ALL ELSE...
(Guidelines for Troubleshooting)
Jan 21, 2020
mkormendy
changed the title
BEFORE ALL ELSE...
(Guidelines for Troubleshooting)
BEFORE ALL ELSE...\s\s(Guidelines for Troubleshooting)
Jan 21, 2020
mkormendy
changed the title
BEFORE ALL ELSE...\s\s(Guidelines for Troubleshooting)
BEFORE ALL ELSE...(Guidelines for :Troubleshooting)
Jan 21, 2020
mkormendy
changed the title
BEFORE ALL ELSE...(Guidelines for :Troubleshooting)
BEFORE ALL ELSE...(Guidelines for Troubleshooting)
Jan 21, 2020
mkormendy
changed the title
BEFORE ALL ELSE...(Guidelines for Troubleshooting)
BEFORE ALL ELSE... (Guidelines_for_Troubleshooting)
Jan 21, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Before reporting an issue, there are a number of reasons why this Homebridge plugin may not be working. Here's some steps to follow to work towards a fix:
config.json
file is properly formatted (see the default sample file here) and the settings for this plugin are correct for your Alarm.com account.-R
flag:homebridge -R
If your homebridge is set to start on boot, you may need to disable that first and start it manually on the command line to refresh the cache and see if the problems continue while in this setup before restoring the start on boot setup.
cachedAccessories
file:a. FIRST, stop Homebridge (this is important);
b. locate and delete the
~/.homebridge/accessories/cachedAccessories
file;c. start up Homebridge again and test for success.
sudo npm list node-alarm-dot-com
If at this point things are not working, please submit a ticket using the Bug Report template.
Once you have submitted the ticket, you can also visit the
Slack channelDiscord channel (moved from Slack to Discord) to see if others are working on the issue already.As a last resort (not recommended due to the destructive nature), the following steps can help reset your entire Homekit/Homebridge integration:
NOTE: this will remove all Homebridge based accessories, their locations in the rooms of Home.app, their automations, scenes, configurations and any related data stored in Homekit. BE VERY CAREFUL!
~/.homebridge/
folder.config.json
settings:a. changing the homebridge user name (just change one character or number in that hex style sequence, without removing any of the colons);
b.remove any unwanted plugins from the accessories and platforms sections.
If the issue persists, please submit a ticket using the Bug Report template.
The text was updated successfully, but these errors were encountered: