Node 3 is showing tons of these retires/timeouts, which appears to what’s interfering with the initialization process.
By waking the device many times, it looks like initialization completed. But, the above-mentioned errors made initialization take much longer than normal.
BTW, @kimhaak can’t post anything for a while due to some new user post throttling.
It looks like the binding is still sending requests when the device is asleep and they are failing - I don’t know why this is, and really can’t look for this in the old binding.
My suggestion is to change to using the development branch - then if there is any such error we can actually look for it.
The development branch can be found here -:
Alternatively, this will be merged in a week or so if you prefer to wait.
I am on the latest snapshot build, and the jar installer you provided in your link, looks to be the same as i am running, and which the logs come from.
No - it’s not the same version - at least the logs that are provided above are definitely not from the new version of the binding. If these are not the logs, then maybe I’m looking at the wrong ones?
If you can see it in PaperUI, then you do not have the development binding installed. If you’d like to give it a try, this script should do it all for you…
Ok, now we are getting there! Used 5iver’s script, wich worked just fine. Deleted my things, and rediscovered them. Now i dont get the 500 internal server error while editing the remote I can even control my first lamp
Ok, so then i guess i will have to go on to the next step, integrate more stuff, and figure out the logics
Thank you all!