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
I would like to suggest a minor enhancement, so the issue I will mention was totally my mistake and is not an issue of the adapter.
After updating I received issues like this:
Without the information which device and service is affected it is kind of difficult to figure out what created the issue. Therefore, I checked the code and added a try/catch block. The code section I adjusted was:
this.adapter.log.debug(`script: converting value to homekit: ${value} to ${newValue}`);
returnnewValue;
}
toIOBroker(value){
letnewValue=this.toIOFunction(value);
this.adapter.log.debug(`script: converting value to ioBroker: ${value} to ${newValue}`);
returnnewValue;
}
I did the following:
toHomeKit(value){try{letnewValue=this.toHKFunction(value);this.adapter.log.debug(`script: converting value to homekit: ${value} to ${newValue}`);returnnewValue;}catch(error){this.adapter.log.error(`Could not convert values to HomeKit for : ${JSON.stringify(this.parameters)}`);throwerror;}}
It would be great if there were more information except the function themselves. But I am not sure if this is possible. At least it helped me to figure out which services are creating the issue.
The text was updated successfully, but these errors were encountered:
Hi,
First of all thx for the awesome work!
I would like to suggest a minor enhancement, so the issue I will mention was totally my mistake and is not an issue of the adapter.
After updating I received issues like this:
Without the information which device and service is affected it is kind of difficult to figure out what created the issue. Therefore, I checked the code and added a try/catch block. The code section I adjusted was:
ioBroker.yahka/main.js
Lines 1588 to 1597 in f380bb7
I did the following:
It would be great if there were more information except the function themselves. But I am not sure if this is possible. At least it helped me to figure out which services are creating the issue.
The text was updated successfully, but these errors were encountered: