Unfortunately I’m not a groovy programmer so creating that driver is beyond my skill set. I’m offering what I can. Access to my hub and my time
It would not be wise to grant community members access to your hub, as the software in question is closed source code. Most of us do not have a license to see that source code. If this were open source code, you'd have a much easier time with gaining assistance from the community.
IMHO, this issue will need to be worked out between @yracine66 and @mike.maxwell, as the rest of us have no access to any of this source code in question.
Personally, I would remove as many of those custom attributes as possible, keeping only those that have an actual use for your specific requirements, to see if that resolves the issue. Almost all of those attributes are custom, as opposed to standard Hubitat attributes found in the standard capabilities. Thus, I question their usefulness as most apps (aside from a few that can handle custom attributes, like Rule Machine) cannot even use those.
1 Like
The offer to access my was specifically for @mike.maxwell . It wasn’t for general community members. Thanks
Not to answer for Mike, but there is nothing that we can do to debug this. Your recourse is to @yracine66. We don't have the driver source code either, and it's not really within the scope of what we do to dig into custom driver issues.
For the Maker API error, turn on Debug Logging in Maker API. Then post a screenshot of the logs from Maker API when you cause this error That will give you some clue to what's going on.
2 Likes
@jbasen Please download the latest version of the drivers using the same selffy download link.
As I don't have any control on how the MakerAPI app is doing its json serialisation, after many trials and errors, I found out that if I change the pressure's datatype in MyFlairVent driver from number to string in the header, then it works fine. The datatype change is the only thing that I can control from my side of things. You can even try it on your side with the original driver, and it should work without issue.
So, I've revised all the other Flair drivers and made some changes to some attributes to make the json serialisation work.
Here is the MakerAPI's previous log
app:9422023-04-19 03:31:40.606debugfindDevice called
app:9422023-04-19 03:31:40.603debugsendDeviceCommand called
app:9422023-04-19 03:30:37.590debugdeviceItem called
app:9422023-04-19 03:30:37.587debugExecuting command: refresh on device: My Flair Vent Office-186c
app:9422023-04-19 03:30:35.683debugfindDevice called
app:9422023-04-19 03:30:35.680debugsendDeviceCommand called
app:9422023-04-19 03:30:20.815errorjava.lang.NumberFormatException: null on line 742 (method sendDeviceCommand)
app:9422023-04-19 03:30:20.807debugdeviceItem called
app:9422023-04-19 03:30:20.804debugExecuting command: refresh on device: My Flair Vent Office-186c
app:9422023-04-19 03:57:41.544debugfindDevice called
app:9422023-04-19 03:57:41.541debugsendDeviceCommand called
app:9422023-04-19 03:57:18.999[error](http://192.168.XX.XXX/logs#)java.lang.NumberFormatException: null on line 742 (method sendDeviceCommand)
app:9422023-04-19 03:57:18.985debugdeviceItem called
Regards.
2 Likes
The Flair users who know the Flair App (like @jbasen) and want to do some special automation need some of those custom attributes to control their Flair system.
My specialised zoning smartapps (ecobeeSetZoneWithSchedule, ScheduleRoomTempControl, ScheduleTstatZones) also need some of those attributes to control the Flair zones...
Regards.
2 Likes
I wanted to thank everyone publicly for working so hard to resolve this. I've been testing this morning and this issue appears to be fully resolved.
Thanks again
2 Likes
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
