socalgene Posted August 30, 2022 Posted August 30, 2022 Bond was working fine for 2 months. I tried to load another fan and the node server will not work no matter how many things that I try. Enclosed is a file with the correct error codes, I think. Thank you. Error Codes.rtfFetching info...
Phil G Posted September 4, 2022 Posted September 4, 2022 Did you update the Bond bridge s/w? Some people are reporting (me included) that the current NS doesn't work with the latest version and they fixed the problem by reinstalling v2.22.6.
hart2hart Posted September 4, 2022 Posted September 4, 2022 On 9/4/2022 at 7:38 PM, Hoosier Daddy said: Did you update the Bond bridge s/w? Some people are reporting (me included) that the current NS doesn't work with the latest version and they fixed the problem by reinstalling v2.22.6.I just saw the Bond FW update and came here to see if any issues before updating the FW. Appears there may be. Did you mean reinstall as delete and delete it back or restart it? If delete and add back in same slot did it retain device links for you?
Phil G Posted September 4, 2022 Posted September 4, 2022 On 9/4/2022 at 8:32 PM, hart2hart said: I just saw the Bond FW update and came here to see if any issues before updating the FW. Appears there may be. Expand Yes, there are issues. Don’t update your Bond beyond 2.22.6. If you have, then you can always reset the Bond to its original firmware, but you don’t want the hassle. I lost all Bond devices in the Bond app when I wiped the firmware back to factory. I never had the NS working with it prior to that start over point because I had immediately updated the Bond as soon as I unboxed it, then added devices, then installed the NS and found it didn’t work.
hart2hart Posted September 4, 2022 Posted September 4, 2022 On 9/4/2022 at 9:36 PM, Hoosier Daddy said: Yes, there are issues. Don’t update your Bond beyond 2.22.6. If you have, then you can always reset the Bond to its original firmware, but you don’t want the hassle. I lost all Bond devices in the Bond app when I wiped the firmware back to factory. I never had the NS working with it prior to that start over point because I had immediately updated the Bond as soon as I unboxed it, then added devices, then installed the NS and found it didn’t work.I’ll definitely hold off on Bond FW update until I see a NS update has been released.
socalgene Posted September 14, 2022 Author Posted September 14, 2022 (edited) Has there been any forward movement to solving this problem? I tried all of the solutions listed but none seem to work. The Bond NS was one of my most used but now unusable NS. Hopefully, someone is working towards a solution for this. I appreciate any help that is offered. Edited September 14, 2022 by socalgene
Phil G Posted September 16, 2022 Posted September 16, 2022 On 9/14/2022 at 6:44 AM, socalgene said: Has there been any forward movement to solving this problem? I tried all of the solutions listed but none seem to work. Expand You couldn't get the bridge firmware back to 2.22.6? Or, once you did that you still have problems? The developer is having issues getting his dev environment back up after moving.
Goose66 Posted September 17, 2022 Posted September 17, 2022 Development environment back as of Friday. Will be done this weekend. 1
Goose66 Posted September 19, 2022 Posted September 19, 2022 A new v3.0.10 version is available in the Node Server Store that fixes this problem and a couple of others raised by changes to the Bond API and PG3. 1
socalgene Posted September 20, 2022 Author Posted September 20, 2022 It works! I have 6 ceiling fans, all of which are controlled by my ecobee thermostat and am a happy camper now. Thank you for all of your hard work.
Recommended Posts