-
Notifications
You must be signed in to change notification settings - Fork 36
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
Google Device node Sensor #215
Comments
I'll check this issue as soon as possible |
I have been able to experiment a little more and came across the following: If I select as trait "Recommended" or "All", I'm able to configure the sensor (and possible also other devices). If I return later and if I select "Selected" I see my configuration and I can modify this, if I wanted. However I suggest, that the option "Selected" should be omitted, until one has configured the trait. Or at least a clear explanation in its README file. Regards |
For every device type there are some traits mandatory, you cannot unselected then. Selecting select the first time, the mandatory traits should be shown. |
Agree, But if a less experieced user want to use this node it is maybe confusing and therefore I suggested to remove that option, if there are no mandatory traits. Thanks for publicing the new version 0.2.0. |
I tested the sensor node and I noted that it works correctly and gives the Temperature in degrees Celsius as, e.g. TC: 9.8°C I think we can close this issue. |
Hello all,
I continued to configure the Sensor node and I noticed a number of issues.
As an example I selected two sensors, Particulate Matter, PM10 and also PM25.
See the following test flow:
However, if I wanted to configure the Google Device node, I noted the following:
So, if you choose " Show trait" and select "Selected", you will see that there is nothing to select.
In the previous, I think, version it was possible:
A second thing I noted that also here 'If msg arrives on input, pass through to output:" does not give an output.
This has been reported before and I believe it has been picked up.
Regards
The text was updated successfully, but these errors were encountered: