Tried this, did not help as far as i can see. Also, debug creates a wall of text, impossible to follow, or look at afterwards, unless one knows what to look for.
It is node 6, is it some keywords i could look for to get going, inside the logfile?
I first did an exclusion of the device, and then i did a hard reset of the zstick (aotec).
Did a new inclusion, and i put the remote very close to the stick. For the first time the remote gave an ack by blinking green. I can now press a button and there is some reaction. Looks like the system is queueing up some requests, and as far as i can interpret it is talking to the device.
I just kept pressing the button when the log indicated device was sleeping. Then, after a while, there was possible to set an wakeup time/interval in habmin. It was “0”, i set 10 seconds, hoping this would mean it would stay awake long enough to exchange some information.
Kept pressing a button from time to time, and suddenly something “came loose” and the system looked like it was creating the device, i think it had enough info to detect it, and create it.
The main thing i did was reset the zstick, so it forgot what it had seen of the remote, and also forgot the fibaro dimmer2. Then i did a new scan, initiating the inclusion mode on the remote a couple of times, close to the stick, until it acked with a green blink.
I dont know what and if something was wrong, log was too fast for me to recognize something obvius.
This is a very short wakeup interval. It likely will drain your battery rapidly. Generally, a “good” wakeup interval is 3600 to 14400 seconds, depending on how much you want to conserve battery life.
if you post your openhab.log, we can take a look at what actually happened. The log likely is too big to post on the forum, so you would need to post to a sharing service like Dropbox, Google Drive, etc.
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!