Replies: 2 comments
-
Hi |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hello, I just saw that another discussion post (#409) describes the same problem. It is also strange how the display of the KNX device node behaves
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Salutation (i'll not respond to users that doesn’t wrote at least "Hello")
Describe the bug
Hello,
I have a question about the specification in a KNX device node.
In the section: “Read status on start” you can specify “Restart last value saved to file prior to disconnection. If the file is missed read from KNX Bus ....”. I assume that the file that is described is an internal file and does not need to be specified by the user. I have observed that when the node is restarted, an attempt is made to read from the KNX bus and the file is not evaluated. Are there problems in this area?
Greetings
Joachim
To Reproduce
Write here the steps to reproduce the behavior, for example:
Expected behavior
Write here a clear and concise description of what you expected to happen.
After a restart of the KNX device node, the last value for KNX should be provided. A KNX read telegram should only be sent if the file is not available.
Screenshots
Here, if applicable, add screenshots to help explain your problem.
Knx-Ultimate Version
3.3.8
Are you running node-red behind homematic, docker or anything similar?
Node-Red running alone in RaspberryPi
Additional context
Beta Was this translation helpful? Give feedback.
All reactions