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

Can not read disabled dummy device value #940

Closed
wolverinevn opened this issue Feb 25, 2018 · 4 comments
Closed

Can not read disabled dummy device value #940

wolverinevn opened this issue Feb 25, 2018 · 4 comments

Comments

@wolverinevn
Copy link

wolverinevn commented Feb 25, 2018

Steps to reproduce

  • OTA update to mega-20180224 from 2.0.0-dev12
  • In rules: use if statement compare disabled dummy device value to any value. Ex:
    if [Dummy#value1] > 1000
    command
    endif
  • Taskvalueset works well.
    Does the problem presist after powering off and on? (just resetting isnt enough sometimes)
  • Yes

Expected behavior

  • Read disabled dummy device value as normal sensor value

Actual behavior

  • Can not read value of disabled dummy device

System configuration

Hardware: Nodemcu-12E

Software or git version: mega-20180224
Previous good version: 2.0.0-dev12

@wolverinevn wolverinevn changed the title Can not read disable dummy device value Can not read disabled dummy device value Feb 25, 2018
@uzi18
Copy link
Contributor

uzi18 commented Feb 25, 2018

It is not a bug.
Why do You want to read from disabled device?

@TD-er
Copy link
Member

TD-er commented Feb 25, 2018

It is indeed by design to ignore disabled devices/controllers etc.
This will save resources on the ESP and allow for better responsiveness and more stable operations.

@wolverinevn
Copy link
Author

I use dummy devices as variables so no need to keep it updating regularly (in log: EVENT: ...). I want to control them manually by reading and writing as needed. I do not know well how ESPeasy works but I guest keeping device disabled helps saving resource.

@TD-er
Copy link
Member

TD-er commented Feb 25, 2018

I guess enabling the dummy device will not use many resources, so please try with the dummy device enabled.

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

No branches or pull requests

3 participants