just got latest echo speaks main and diffed it with my loaded version .. only difference is the comments i added..
my device source is difference was getting errors on 404 error when playing an audible book on an echo.. it was trying to find the book image.. i added that check as a noop
not sure maybe i should just disable the check in the main, as i was getting tons of errors because of the 404 trying to lookup an image.
ie
Did you recently change the HE version of this hub? ie an HE change?
he updated a couple of days ago when latest main release came out..
i can try a reboot and see if that fixes it.. do you see something why ver could be null?
i am wondering if it was because the hub rebooted when my es server on my qnap was down and got an error.. i then started up the server and everything checked out ok .. but i will reboot the hub now with the es server up and running and see if that fixes it.. thanks
REBOOT of hub with es server up did not fix issue still getting thos log messages.
Make a backup of what you changed, then load the official code and see what happens. Seems to me it is complaining about something within the changed code.
its just those 2 lines ill try that..
1 Like
here is the error i was talking about when i reverted my code change actually worse in a way.. maybe you could put that fix in?
1 Like
I know whats going on thanks for your help.. with debugging i get this
Its looking up the first echo device in your device list to get the version of the driver.
Well that is coming back null in this case because:
We have multiple locations/houses so i can get msgs/warnings wherever we are... and the first device is at our camp/cottage.
The other owner is at the cottage for 2 weeks so i disabled that device so he doesnt get annoyed for instance when it tells me a wine fridge or freezer is too warm, a door left open, mail arrived etc.
Well with it disabled the ver variable is coming back null and causing the issue.
So it had nothing to do with my code change which i still recommend be rolled in..
Thanks for your help..
The real solution would be to go through the list and get the first device that is NOT disabled and get the version there. However, too much work for me now so i will just put a check in that ver is not null. Maybe someone else can fix it is the more correct way.
Here is the workaround for now:
4 Likes
