Noticed it this morning when I pulled down the latest HomeBridge release. You've been busy.
Nice I saw the update but had not checked out the change log yet.
So you pulled in the patch I made for Heroku in this thread: Echo Speaks - Heroku new deployment workarounds
If so I can update my instructions to get rid of the part about using my custom code.
Nevermind, I found it in the changelog.
[FIX] Added server host override Thanks @jtp10181.
Also I am not the one who added the info for the newer devices, there was a bunch of different people posting that and I do not think I contributed at all.
update to the hubitat or also the external (for me on qnap/container station) servers?
thanks
also you didnt wrap in my 2 changes.. ie error for disabled device and playing audiobook 404 error looking for image file.
Update was to the Hubitat app code.
Do you have a link to your changes?
I post d the lines above. if u want me to checkout and make a version with the changes I will.
I updated the files with your suggestions... I even fixed the code version when devices might be disabled
ok will do a repair thanks again.
No, thank you for your efforts on figuring these things out... I haven't worked on the app much because it always just works for me...
It's crazy to think i created ES back in 2018 and it still works so well 7 years later
I am seeing this in my logs after updating to the latest version:
Hub is connected to the Internet as are all of my Echo devices. No issues on that end.
Have you opened the app since it was updated? With the two apps from this dev I have found it good to open the app after updating, click done. Then open again and click done. This seems to get everything to sync up.
Opening it will force all the child apps and devices to run initialize() and report there version back to the main app. It will eventually run it on it's own with the healthcheck
I know this wasn't in response to me, but yes I have.
My other warnings seem to have cleared, but I still see this one @tonesto7
Make sure the device driver code actually updated
I didn't make any changes to those areas of the code... I feel like that warning has existed for years. I will investigate it when i get some time. I really need to look at the latest apis available and update the app and devices
I appreciate the response @tonesto7 .
I've been running Echo Speaks for ages and am very aware of logs, etc. I have never seen these 408 errors at any time previously. Internet connectivity across the board is 100% OK in my environment.
I was wrong, other warnings seem to be coming back:
