Closed realjax closed 5 years ago
I will take a look at this problem
This is a completely new version, I started this version before you have added smoke detector, so I just copy it to the new version, cause it is not backward compatible in the code. Your commits are present in version 1 - branch v1 in the repo.
I removed the config from the gateway node. If you want to add the new device just add the corresponded node and write the device SID to the node.
Could you try v2.0.3 with the fix of the problem you have had. If it is not fixed, could you export your flow, I will test on it, cause I cannot reproduce it on my flows.
Thanks I'll try. Exporting the flow is however not an option because I can no longer get to the admin part of node red because of the load. I suspect it is caused by the gateway utils node.
Igor notifications@github.com schreef op 12 mei 2019 10:24:26 CEST:
Could you try v2.0.3 with the fix of the problem you have had. If it is not fixed, could you export your flow, I will test on it, cause I cannot reproduce it on my flows.
-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/igdr/node-red-contrib-xiaomi-smart-devices/issues/14#issuecomment-491575672
gateway utils node is a just debug node and prints to the console all devices in the network.
Ah then that is my problem. It is flooding the console with messages. Hundreds of em and doesn't stop. Seems like it is looping
Igor notifications@github.com schreef op 12 mei 2019 11:31:10 CEST:
gateway utils node is a just debug node and prints to the console all devices in the network.
-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/igdr/node-red-contrib-xiaomi-smart-devices/issues/14#issuecomment-491579865
I'd added in the new version one thing - ask for the element state every 60 sec, it can also flood to the console
Well, it seems unrepairable so far :( I have downgraded to version 1.0.15 and then Node-red starts to work normally again ( as soon as I upgrade again, flooding starts). But with 1.0.15 my flows no longer work correctly and I seem to have lost all configurations for the devices, it can no longer resolve the correct SID. When I open the configuration node for the gateway it no longer shows the devices either ( see pic) I do have a backup of my flows but those also no longer work when downgrading... very unhappy now.. Not sure what happened here, but looks like I can start all over
I upgraded my "home automation" based on Node-Red successfully from the previous version to the new one, one thing I had to do just set device names, cause they were empty.
I have now downgraded to 1.0.14 which brought back the devices configuration option again.
Using this I can get it back to work :)
Something is very weird about my setup. I wil try again with the 2.0 version later when I have some more time :) For now I just wanted things to work again :)
Did you have a chance to try the new version again?
No activity, so I close this issue
I have three questions:
1) The last version kills my node-red. The logs are FLOODED with messages like for instance Sending message '{"cmd":"write","sid":"158d00024e4933","data":"{\"cmd\":\"write\",\"sid\":\"158d0002c91e47\",\"data\":{\"cmd\":\"write\",\"sid\":\"158d0002c91e47\",\"data\":{\"cmd\":\"read\",\"sid\":\"158d0002579485\",\"data\":{\"key\":\"2f11870149aa8f47ccc7761430773f66\"},\"key\":\"2f11870149aa8f47ccc7761430773f66\"},\"key\":\"2f11870149aa8f47ccc7761430773f66\"},\"key\":\"2f11870149aa8f47ccc7761430773f66\"}"}'
Hundreds of them until I kill the non-responding server!! Edit: Seems to be gone now Edit 2: Nope, got it back and it kills my node-red server
2) is there something going on with a history rewrite of the repo? I have added the smoke detector which you merged on 31st of March but which now reads as being added by you 7 hours ago??
3) where are all my devices in the config, I cant find them anymore. How do I add a device?