Skip to content
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

Time pin visible on DHT11 #1984

Open
Cesar-S opened this issue May 11, 2020 · 5 comments
Open

Time pin visible on DHT11 #1984

Cesar-S opened this issue May 11, 2020 · 5 comments

Comments

@Cesar-S
Copy link
Contributor

Cesar-S commented May 11, 2020

With the DHT11 node and LCD I see that there are still problems. A though an throttle node was included, the time is set to 0.2 and the xoders add a clock with 2 or 3 seconds. Something redundant ...

The time pin should be accessible and be modifiable.

@Cesar-S Cesar-S changed the title As a novice xoder I want foo so that I qux Time pin visible on DHT11 May 11, 2020
@nkrkv
Copy link
Member

nkrkv commented May 12, 2020

Hello! Are you talking that the boolean ACT on text-lcd-16x2-i2c is not sufficient and the LCD is missing some updates so that the pulse UPD should be brought back?

@Cesar-S
Copy link
Contributor Author

Cesar-S commented May 12, 2020

Hello, Sorry for not including the links...

Here are two examples, it seems that some have a problem.

https://forum.xod.io/t/not-reading-temp-from-dht11/3920/3

https://forum.xod.io/t/text-lcd-i2c-16x2-with-dht11-hygrometer-nodes-lcd-err/3721/19

@Cesar-S
Copy link
Contributor Author

Cesar-S commented May 12, 2020

Now I realize that they are using an old LCD node 🤦‍♂️

ps: but in the second topic, I see that there are only some watch

@nkrkv
Copy link
Member

nkrkv commented May 12, 2020

Looks like there are plenty of different models of DHT11 in the world. The current version of dht11-hygrometer throttles updates with 0.2 seconds intervals which is not sufficient for all models, possibly.

What’s the best option for the dht11-hygrometer, what do you think?

  • Raise throttling from 0.2 to 1.0, keep interface the same, hope the things will work for everyone
  • Expose the throttling limit as an input pin with 0.2 as default. That is, make the interface more complex
  • Expose the throttling limit as an input pin with 1.0 as default.
  • Expose the throttling limit as an input pin and replace pulse UPD with boolean ACT.

@Cesar-S
Copy link
Contributor Author

Cesar-S commented May 12, 2020

Expose the throttling limit as an input pin with 0.2 as default. That is, make the interface more complex

In my library I used the throttle node but left the time pin visible. I think it could be a simple change without affecting the rest.

https://xod.io/libs/cesars/rich-uno-r3/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants