Hi. I’ve had a Smart By Bond ceiling fan on my back deck for a few years now. I recently setup Home Assistant and a scene controller to control the fan, before that I mostly just turned it on and off with the wall switch (which cut power to it). Now I am trying to keep it always on. All that is to say I’m paying a lot more attention to it now, so I am not sure if my issues or new or not.
Here’s the version:
HTTP/1.1 200 OK
BOND-Flags: 4
Content-Length: 300
Content-Type: application/json; charset=utf-8
{"target":"breck-volunteer-6rf","fw_ver":"v3.5","fw_date":"Wed Oct 19 21:46:16 UTC 2022","uptime_s":50488,"boot_patch":"not first boot","make":"Progress Lighting","model":"BF841","branding_profile":"PROGRESS_BF841","bondid":"KVPRBEL77550","upgrade_http":true,"api":2,"_":"7427cc77","__":"7427cc77"}
My wifi signal is weak, the API tends to report it in the 30s. Not sure why, it’s actually only 20 feet from the router.
I turned off the watchdog using the api, but it still seems to disappear. I thought it was just the wifi being flakey, and I think that is also the case, but I noticed it rebooting even with the watchdog turned off, and rebooting into v2.15.8.2, so it must be in a recovery mode or something. And then later I check back and it’s back to v3.5. Very confusing.
It’s also in the 30sF outside, so I wonder if it doesn’t like the cold.
Is there any way to get it to tell me what is happening? Like an api that says it’s in safe mode, or why it’s in safe mode?
Smart by Bond devices usually boot in the factory partition first and then reboot in the OTA partition.
However, it shouldn’t be rebooting that much. We are looking at this issue!
Hey! We did actually discover the issue here and fix in v4.4.4 firmware, but this is either not released yet or available only in the beta channel, depending on your fan model. Can you try the beta and let us know?
I switched to beta and it doesn’t show any available updates. However, both fans have been stable and holding the v3.5 firmware for the past 4 or 5 days now.
Thanks for checking in, Tim. I don’t think we will need logs on this particular issue because we understand the root cause. (When rebooting intentionally we were setting some volatile flags to instruct the bootloader which firmware image to boot. However, we had overlooked that crashes were not setting this flag, so it would boot back into the wrong image… the “rescue” image rather than the latest one delivered by OTA update.)
Well, after having the beta update for a while I can say that I am largely unable to control the group on/off settings. Sometimes the group control will turn both lights on but I usually have to select each fan individually to turn lights on and off. Scheduling works good though as a group. The firmware seems stable though…the fans haven’t reverted back to previous versions.
Thanks for followup. Perhaps the fan firmware is still crashing on the Group commands and just not reverting to the old fw anymore (since we fixed the reversion but not the crash that was causing it). We will have to check on this on our end.
Group settings are set to turn fan lights on at sunset and off at sunrise.
Lights come on quite reliably at sunset, however they do not turn off at sunrise (or at any other time during the day) without being turned off individually on each fan. (ie: the app can communicate with both fans in Group. It just won’t - like a petulant 2 year old) App says there is a problem communcating with the device- but will turn off both lights individually from the Devices page. I have tried changing settings to different times and got the same results. (The other day the app said there may be a problem with the bridge but I didn’t take a good enough note to remember exactly what it said)
This sounds like you are still getting a crash. I was able to pull up your account. We will see if we can figure out what’s going on here, but it could take a few weeks to get back just based on current load. (@igoraltvidal let’s take to a gh issue).
Strangely, since I wrote last, it has worked great for 3 out of the last 4 days. “scratching head” (ie worked 1 day then not for one day, then good for 2 days)
One last update for my fan issues. Updated to the beta firmware and continued to have the group issues. Recently I deleted the group with both fans and programmed schedules for each one individually. Both fans have been working flawlessly ever since.