NorthernMan54
commented
4 years ago Chris,
With the V1 approach, Amazon has been slowly dropping support for it for a few years now with each new device. My guess is that it has now hit the tipping point for yourself and is no longer supported by your devices.
My recommendation would be to get yourself to a recent version of homebridge and your plugins, then layer in the V2 plugin.
And as getting everything running again is a bit of effort, setup it up beside your existing setup, then cut over once it’s stable.
On Sep 26, 2019, at 12:33 PM, chrisp79 notifications@github.com wrote:
Hi, hope you’re well. Back in 2017 ago you helped me get Alexa-Homebridge (V1) up and running in my home. I’m so grateful – it’s been absolutely brilliant ever since then.
I seem to have developed a bit of a problem in the last fortnight though. It started with Alexa not being able to contact any devices one evening (Homekit still worked fine). The next morning everything seemed fine much to my relief. However, later that day Alexa stopped being able contact any devices again (again Homekit was fine), and it’s never worked again since.
I went onto your Github page to see if I could see any comments from other users, and noticed that you’d released V2. I backed up my existing setup and then tried installing your V2 but I couldn’t get that to work no matter what I tried. I saw there was a new version of Raspbian (Buster) so downloaded a fresh image and tried installing scratch. I tried absolutely everything, but whatever I did I couldn’t get homebridge-rcswitch-gpiomem to install – I keep getting NPM errors. I noticed there were various versions of gpiomen, npm and node and tried quite a few different combinations to no avail. I repeated this on fresh installs of Stretch and Jessie but still no luck. Having spent goodness knows how many days on trying to get new versions to work, I decided to restore my backup and focus on trying to debug that.
I’ve tried all sorts to get the V1 setup working, but am having no luck with that either. Whatever I do, Alexa doesn’t see my Homebridge. I even restored an image I took back in 2017 when I initially got everything up and running fine – in case the RPI had somehow taken an update recently that had caused the problem – but again no luck, Alexa still doesn’t see it. I found some debug steps you sent me back in 2017 and have re-run those – the output seems to match what it was back then, so I’m stumped as to what’s happening.
I’m guessing the fact that Alexa can’t see my Homebridge is therefore something to do with SSDP. I assume my router has an important part to play with this, so was wondering whether my cable provider had pushed an update to it that might’ve caused a problem. But then I realised my that I’d made a copy of my SD and RPI for my Dad back in 2017 to set his home up, and he has the same router and cable provider as me and his install is fine.
So I’m completely flummoxed. If you have any idea what might be going on here I’d be extremely grateful for your help.
Many thanks, Chris
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
chrisp79
Hi, hope you’re well. Back in 2017 ago you helped me get Alexa-Homebridge (V1) up and running in my home. I’m so grateful – it’s been absolutely brilliant ever since then.
I seem to have developed a bit of a problem in the last fortnight though. It started with Alexa not being able to contact any devices one evening (Homekit still worked fine). The next morning everything seemed fine much to my relief. However, later that day Alexa stopped being able contact any devices again (again Homekit was fine), and it’s never worked again since.
I went onto your Github page to see if I could see any comments from other users, and noticed that you’d released V2. I backed up my existing setup and then tried installing your V2 but I couldn’t get that to work no matter what I tried. I saw there was a new version of Raspbian (Buster) so downloaded a fresh image and tried installing scratch. I tried absolutely everything, but whatever I did I couldn’t get homebridge-rcswitch-gpiomem to install – I keep getting NPM errors. I noticed there were various versions of gpiomen, npm and node and tried quite a few different combinations to no avail. I repeated this on fresh installs of Stretch and Jessie but still no luck. Having spent goodness knows how many days on trying to get new versions to work, I decided to restore my backup and focus on trying to debug that.
I’ve tried all sorts to get the V1 setup working, but am having no luck with that either. Whatever I do, Alexa doesn’t see my Homebridge. I even restored an image I took back in 2017 when I initially got everything up and running fine – in case the RPI had somehow taken an update recently that had caused the problem – but again no luck, Alexa still doesn’t see it. I found some debug steps you sent me back in 2017 and have re-run those – the output seems to match what it was back then, so I’m stumped as to what’s happening.
I’m guessing the fact that Alexa can’t see my Homebridge is therefore something to do with SSDP. I assume my router has an important part to play with this, so was wondering whether my cable provider had pushed an update to it that might’ve caused a problem. But then I realised my that I’d made a copy of my SD and RPI for my Dad back in 2017 to set his home up, and he has the same router and cable provider as me and his install is fine.
So I’m completely flummoxed. If you have any idea what might be going on here I’d be extremely grateful for your help.
Many thanks, Chris