@ljbotero, I’m getting the same error as @pomonabill220. I’m seeing it every one hour in my log fwiw, although I’m not seeing any problems manifest so far.
Error Monitor Harrogate II - Flair Vents - org.codehaus.groovy.runtime.metaclass.missingmethodexceptionnostack: no signature of method: java.lang.string.call() is applicable for argument types: (hubitat.scheduling.asyncresponse null) values: [hubitat.scheduling.asyncresponse@8d0565 null]
possible solutions: wait() chars() any() trim() grep() find() (handleauthresponse)
I just looked through my log after seeing your note about seeing it every one hour...
and i see it EVERY hour accurate to the SECOND in my log!
Interesting!
Thanks guys, I'm investigating this, I'm also seeing this in my logs, but it's quite tricky, I'll get back to you once I identify the root cause and will push an update once I figure this out.
Curious if either of you guys are seeing actual problems associated with this error? Versus are we possibly chasing an error strictly in theory not practice?
If I am having behavior problems, I’m not seeing it/them.
Just updated to 0.233.
A question just popped into my brain!
Since I use the thermostat controller HE app and not my physical stat for mode and setpoint status to your flair app, AND I use fractional setpoints (IE 75.5 deg F), does your flair app use the decimal values or round the numbers?
Also my temperature sensors that I use in my rooms report fractional values as well.
Would this cause problems?
@ljbotero, I had to disable your app because I was getting flooded with these errors (log below). I’m suspecting this may be unique to me as I have 3 instances running in parallel (one each for upstairs, ground level, and basement) since each is its own HVAC zone. This is happening only for the one zone where I have relatively many vents (21). But I never had this problem with prior versions, so maybe there is a fix I can try?
FWIW when I check “app stats” and “device stats” in the HE log, your integration doesn’t show up anywhere close to the top of the list in resource consumption, so I’m confused why it’s happening.
Temperature change 0.0°C is below hysteresis threshold 0.6°C - ignoring
is showing up so much? I know that the room temps are changing more than 0.6C.. more like 1-2 F.
Does this indicate that the temperature sensors are not being used?
I'm curious on how I can tweak this to work a bit better for me. I know that the code is written with the intention of minimizing vent movements and trying to find an overall balance. I'm kind of shooting for the opposite, I don't mind at all if there are frequent vent movements in order to achieve better balance in the house. The east side of the house is hot in the morning prompting the vents to open more, and then in the afternoon when the west side of the house is hot, I just don't feel like this is responsive enough. So the east side of the house overcools and the west side is left hot. Eventually it recovers but it just seems like it's a constant circle of trying to play catch up. I would much rather it monitor the temps and make vent adjustments in more real time.
Is there anything I can tweak in the parameters to make it run the calculations and make vent adjustments more often to promote better real time balancing?
