If you use two nodes in two flows things get crazy.
GAZ082 opened this issue · comments
If you use a node in one flow and then a new one but with same configuration in the second, when you refresh the GUI the sonoff nodes disconnect or move around.
I'm seeing a similar issue, appears to be anything linking to the input of the node is never saved to the flow file. Things work fine when you link and deploy from the app, but restarting or doing a refresh on the webpage disconnects all inputs from this node.
Rather annoying as I really love what this module does for simplicity.
The other alternative is to create my own subflow to produce the same results.
Further investigation, it appears the "id" value being requested in the form is clobbering the node-red "ID" field internally which is why we are seeing some rather strange results for everything we do with it.
| Field | Value |
|---|---|
| Name | My light |
| Type | Sonoff device |
| ID | "frontdoor" |
| mode | "0" |
| broker | localhost:1883 |
| id | "frontdoor" |
| onValue | "ON" |
| offValue | "OFF" |
| cmdPrefix | "cmnd" |
| statPrefix | "stat" |
| telePrefix | "tele" |
I've modified my local copy to correct this and it's now happy.
I've added a PR to address this problem, hopefully it's just a merge and version bump on this end but being that I'm not a JS/node developer in the slightest.. meh.
Refernce: #11
Thanks @steffenmllr, I just wiped mine out, removed the nodes in my code and cleared everything before pulling it back through the pallete.
I know it's not a real world test but it works perfect on this end. 😃