-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid PIN - PINs matching #480
Comments
On the amazon Alexa side she caches a copy of your configuration so she knows what devices you have and how to reach them. If you change your configuration ask her to discover devices again, and she will refresh the cache. |
Hi, thanks for the reply. I’d already tried deleting and rediscovering my devices. They worked initially but then the PIN error returned. |
I think it’s something to do with Alexa discovery?
|
I set the refresh interval in the Alexa plugin down to 300 and the issue started happening after 5 minutes instead of 15. I raised the refresh interval to 86400 to get around it combined with a cron job to restart Homebridge daily and it’s fine now. |
Hi, thanks very much for making this plugin.
I’m using it to control some Somfy blinds in conjunction with the homebridge-rpi-RTS plugin.
Something strange is happening when I issue a command from Alexa, it will sometimes work fine, and I see a corresponding log message in homebridge.log
I can try it again shortly afterwards and get an invalid PIN message
Initially I had the default PIN for the Alexa plugin and the main Homebridge process (031-45-154).
I tried changing both to 155 as shown above in the log file, it worked for a few commands then the PIN errors returned.
Something I did notice was that I also tried changing the Homebridge username to CC:22:3D:E3:CE:30 in my config.json (through the config-ui plugin). After restarting homebridge the username was still showing as DD:22:3D:E3:CE:30 as if it was cached somewhere?
I’m running a standard homebridge installation in all of the default locations (/var/lib/homebridge) on a Raspberry Pi 2 running Bullseye.
Here’s my /var/lib/homebridge/config.json
{
"bridge": {
"name": "Homebridge",
"username": "DD:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-155"
},
"description": "blah blah.",
"platforms": [
{
"platform": "LightWaveRF",
"name": "LightWaveRF",
"ip_address": "192.168.1.5",
"manager_host": "web.trustsmartcloud.com",
"email": "home@***com",
"pin": "****",
"devices": [
{
"roomId": 1,
"roomName": "Garage",
"deviceId": 1,
"deviceName": "Door",
"deviceType": "S"
},
{
"roomId": 3,
"roomName": "Back Garden",
"deviceId": 1,
"deviceName": "Lights",
"deviceType": "S"
},
{
"roomId": 3,
"roomName": "Back Garden",
"deviceId": 2,
"deviceName": "Sprinkler Upper",
"deviceType": "S"
},
{
"roomId": 3,
"roomName": "Back Garden",
"deviceId": 3,
"deviceName": "Sprinkler Centre",
"deviceType": "S"
},
{
"roomId": 3,
"roomName": "Back Garden",
"deviceId": 4,
"deviceName": "Sprinkler Patio",
"deviceType": "S"
},
{
"roomId": 3,
"roomName": "Back Garden",
"deviceId": 5,
"deviceName": "Pergola Lights",
"deviceType": "S"
},
{
"roomId": 4,
"roomName": "Front Garden",
"deviceId": 1,
"deviceName": "Lights",
"deviceType": "S"
}
]
},
{
"name": "Config",
"port": 8581,
"platform": "config"
},
{
"name": "Alexa",
"username": "colin@.co.uk",
"password": "Dgffggghh”,
"routines": false,
"blind": true,
"door": false,
"debug": false,
"deviceListHandling": "allow",
"pin": "031-45-155",
"platform": "Alexa"
}
],
"accessories": [
{
"name": "Lounge Left",
"id": 1000001,
"prog": false,
"accessory": "Somfy RTS Remote"
},
{
"name": "Lounge Right",
"id": 1018617,
"prog": false,
"accessory": "Somfy RTS Remote"
},
{
"name": "Lounge Both",
"id": 1857477,
"prog": true,
"accessory": "Somfy RTS Remote"
}
]
}
Very much appreciate any help you can give,
Col
The text was updated successfully, but these errors were encountered: