You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe Your Problem:
Intermittently, when making changes to the mode or target temperature, the child bridge running this plugin crashes with an "UnhandledPromiseRejection" error, and the Home app shows 'No Response' for the Air Conditioner. After about 10 seconds the child bridge is restarted and it's available to change again, but all changes in the Home app appear to be reverted immediately after changing, and the logs say "Target temperature is already 25.5° for system; ignoring request." Changes don't then usually cause it to crash again, unless I do enough of them in a row, but I also can't get changes to stick.
Changing the values on the iZone control tablet or in their app still works, and it seems once those are changed somehow then I can make changes in the home app again.
Obviously still a bit of troubleshooting left for me to do, to figure out which precise combination of circumstances cause it, but thought I'd raise this and ask in case you've seen it before and might save me some time (but no issues if you haven't).
Logs:
[2/15/2024, 8:31:21 AM] [Air Conditioner] System is already set to cool; ignoring request.
[2/15/2024, 8:31:21 AM] [Air Conditioner] System is already on; ignoring request.
[2/15/2024, 8:31:24 AM] [Air Conditioner] Sending command: {"UnitSetpoint":"25.5"}
[2/15/2024, 8:31:25 AM] [Air Conditioner] Target temperature set to 25.5 for system.
[2/15/2024, 8:31:31 AM] [Air Conditioner] System is already on; ignoring request.
[2/15/2024, 8:31:31 AM] [Air Conditioner] System is already set to cool; ignoring request.
[2/15/2024, 8:31:44 AM] [Air Conditioner] Sending command: {"UnitSetpoint":"26.5"}
[2/15/2024, 8:31:44 AM] [Air Conditioner] Target temperature is already 25.5° for system; ignoring request.
[2/15/2024, 8:31:44 AM] [Air Conditioner] Target temperature set to 26.5 for system.
[2/15/2024, 8:31:45 AM] [Air Conditioner] Sending command: {"UnitSetpoint":"25"}
[2/15/2024, 8:31:45 AM] [Air Conditioner] Target temperature is already 26.5° for system; ignoring request.
[2/15/2024, 8:31:45 AM] [Air Conditioner] Target temperature set to 25 for system.
[2/15/2024, 8:31:52 AM] [Air Conditioner] Sending command: {"UnitSetpoint":"26"}
[2/15/2024, 8:31:52 AM] [Air Conditioner] Sending command: {"UnitSetpoint":"25.5"}
[2/15/2024, 8:31:52 AM] [Air Conditioner] Target temperature set to 25.5 for system.
UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "UNKNOWN".
[2/15/2024, 8:31:52 AM] [Air Conditioner] Child bridge process ended
[2/15/2024, 8:31:52 AM] [Air Conditioner] Process Ended. Code: 1, Signal: null
Describe Your Problem:
Intermittently, when making changes to the mode or target temperature, the child bridge running this plugin crashes with an "UnhandledPromiseRejection" error, and the Home app shows 'No Response' for the Air Conditioner. After about 10 seconds the child bridge is restarted and it's available to change again, but all changes in the Home app appear to be reverted immediately after changing, and the logs say "Target temperature is already 25.5° for system; ignoring request." Changes don't then usually cause it to crash again, unless I do enough of them in a row, but I also can't get changes to stick.
Changing the values on the iZone control tablet or in their app still works, and it seems once those are changed somehow then I can make changes in the home app again.
Obviously still a bit of troubleshooting left for me to do, to figure out which precise combination of circumstances cause it, but thought I'd raise this and ask in case you've seen it before and might save me some time (but no issues if you haven't).
Logs:
Plugin Config:
Environment:
The text was updated successfully, but these errors were encountered: