-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Device properties via variable #91
Comments
With the latest master you can add an "AccessoryInformation" service to specify those values via datapoints/functions etc. |
As soon as I add the service, there is always an error message: TypeError: Cannot read property 'toString' of undefined |
Where do you get this error? |
If I don't specify a service typ (AccessoryInformation Service), there's a mistake: Error: Cannot add a Characteristic with the same UUID as another Characteristic in this Service: |
can you please enable the debug log for the Yahka Adapter? |
|
You are not using the latest version of Yahka (which is necessary for this feature) Please check again if it works with 0.9.0 |
How exactly do I do that using the GitHub button? |
Go to the "Adapters" Page |
I found it... thank you. |
The error is also present with the current version. Could you please write a working example where the AccessoryInformation Service function is used and also works |
Can you please post the log again? |
yahka.0 2019-01-24 12:54:59.193 error at initAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4990:18) |
Did you fill in the "Subtype" Fields? |
If I leave the service subtype empty, the error occurs: yahka.0 2019-01-24 13:16:23.398 error Error: Cannot add a Characteristic with the same UUID as another Characteristic in this Service: xxxxxx-xxxxxx-xxxxxx-xxxxxx-xxxxxxxxxxxx |
Can you post more of the log? |
Any news on this? |
sorry... I have tested it with a heating thermostat, it works, with the lamp comes the said error |
Can you make a screenshot of your configuration of the said lamp? |
Read out device properties optionally via ioBrocker.State or similar.
With this you can automatically read and enter the firmware, serial number, manufacturer etc..
The text was updated successfully, but these errors were encountered: