I just noticed that this started happening recently. I have both Bond integrations installed in Hubitat - user and system. Have tested this on both. Hubitat is getting the commands and turning the fan on but the tile is not updating. I have probably screwed something up but don’t know what it is! Thanks.
Hubitat version 2.3.9.176. Bond V4.7.1.2.
It sounds like SharpTools fundamentally isn’t getting the status updates for the speed attribute for the device. It looks like your screenshots are from 2024-08-31, but the last state for speed in your first screenshot was on 2024-08-29.
Have you checked your Hubitat logs and do you see it trying to send the updated speed statuses for that device to SharpTools? Note that you may need to update the Enable Logging setting within the SharpTools Hubitat App if it’s currently disabled.
And has anything changed with that particular device or the associated driver + app recently?
ok, I turned debug on and I don’t see any information about speed being sent. I assume that this would show as a separate log line?
I do see errors about cloud message limits?
While playing around I removed the fan from the Sharptools app and then re-added it. This does cause the tile to update once but doesn’t update after that.
I am running two Bond integrations on Hubitat - community and system. I do this because neither has a complete set of features implemented. But I use the community app exclusively for fans. I have tried adding both devices (community and system) to Sharptools and they both behave the same way.
For what it is worth I tried to add it to the Hubitat → Home Assistant connection but it only shows up as an on/off switch over there. Apparently Home Assistant has deprecated speed and speed_list in favor of percentage_step and percentage? So I couldn’t really test to see what is coming out of maker that way. Also, the on/off status didn’t update but that might be due to the app implementation.
So not sure what to do next?
Yes, you would expect to see a log line similar to the other events like:
Sending event for DEVICE: {{deviceId}} {{attribute}} -> {{value}}
I wouldn’t worry about those for this particular issue as they are unrelated and self-resolving. Based on your logs, those errors are occurring during device synchronization attempts. SharpTools is reaching out to Hubitat asking for the devices (in batches) and it looks like the payload is too big for Hubitat to respond.
Reading the logs from bottom to top, you may notice that it tries a batch of 20 devices starting at index 341 and after that fails it automatically retries with a smaller batch of 10 devices starting at the same index of 341. We can see that it succeeds and then moves onto the next batch of 20 starting at index 351 as expected.
That makes sense as it will perform a full device synchronization and thus get an up-to-date snapshot of the current device states (attribute values).
Have you also checked the Events tab for the device in Hubitat and do you see the speed attribute reporting events there? Since you have multiple similar devices, also double check that you’re comparing the exact same device by verifying the reported Device ID in SharpTools and in Hubitat to make sure they’re the same.
If you want to send a note to support@sharptools.io with the Device ID in question that isn’t updating as expected, I can take a closer look and see if there are any clues.
ok, I sent a support email. Thanks.
In following up with Simon via email, it looks like the devices that aren’t updating status as expected also aren’t emitting events in Hubitat which explains the issue.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
