I was using a RaZ and then i did not have this issue, then the RaZ broke and i bought a UZB instead and now I have the issue.
Of course it could be a coincidence but I am using the same devices, just excluded and included to the UZB
Current status is not correct
Re: Current status is not correct
So what should I do?
If I buy a RaZberry2 EU gen5 and it solves the issue, will i get a full refund for my UZB+License?
If I buy a RaZberry2 EU gen5 and it solves the issue, will i get a full refund for my UZB+License?
Re: Current status is not correct
Those devices have 99% same firmwares. The difference is only in EEPROM and USB/UART. So I doubt it will help. Sure UZB is on the latest f/w version (5.06)?
Re: Current status is not correct
Firmware
Library Type: Static Controller
SDK Version: 6.51.06
Serial API Version: 05.06
But maybe it could be some fault on my UZB?
Library Type: Static Controller
SDK Version: 6.51.06
Serial API Version: 05.06
But maybe it could be some fault on my UZB?
Re: Current status is not correct
I doubt... Please make sure devices have in Report group (LifeLine) the controller (1, 1:0 or 1:x)
Re: Current status is not correct
Where do I find that information Report group?
But it always works when i manually update the status from expert UI, and in the queue we could see both SET anf GET is sent.
But it always works when i manually update the status from expert UI, and in the queue we could see both SET anf GET is sent.
Re: Current status is not correct
Let me analyse your log again. Can you make more of these "simultaneous"? I've never seen such conjestions...
Re: Current status is not correct
Sure, no problem.
Do you just want me to turn on and off or do you want me to update also from Expert UI?
Do you just want me to turn on and off or do you want me to update also from Expert UI?
Re: Current status is not correct
I have now made some more tests and I have included the log.
One thing i noticed is that it happens much more regular on Fibaro Wall Plug. I already had one device "out off sync" with its current status so I do not know when that happened so i do not have a good log file for that, but i tried 4 devices 10 times without issue, then I added two Fibaro Wall Plugs to the test and every time at least one of them failed to update status correct.
It is device 3 and 19 in the log.
Here is some information about the log files, between what times I did different things, hope that helps to read the log file.
[2017-01-29 19:12:38.993] - [2017-01-29 19:14:23.014] device 3 failed
[2017-01-29 19:14:23.014] - [2017-01-29 19:15:05.068] manual update device 3
[2017-01-29 19:15:05.068] - [2017-01-29 19:16:48.282] device 19 and 3 failed
[2017-01-29 19:16:48.282] - [2017-01-29 19:18:08.890] manual update device 19 & 3
[2017-01-29 19:18:08.890] - [2017-01-29 19:19:25.298] device 3 failed
[2017-01-29 19:19:25.298] - [2017-01-29 19:20:13.317] manual update device 3
One thing i noticed is that it happens much more regular on Fibaro Wall Plug. I already had one device "out off sync" with its current status so I do not know when that happened so i do not have a good log file for that, but i tried 4 devices 10 times without issue, then I added two Fibaro Wall Plugs to the test and every time at least one of them failed to update status correct.
It is device 3 and 19 in the log.
Here is some information about the log files, between what times I did different things, hope that helps to read the log file.
[2017-01-29 19:12:38.993] - [2017-01-29 19:14:23.014] device 3 failed
[2017-01-29 19:14:23.014] - [2017-01-29 19:15:05.068] manual update device 3
[2017-01-29 19:15:05.068] - [2017-01-29 19:16:48.282] device 19 and 3 failed
[2017-01-29 19:16:48.282] - [2017-01-29 19:18:08.890] manual update device 19 & 3
[2017-01-29 19:18:08.890] - [2017-01-29 19:19:25.298] device 3 failed
[2017-01-29 19:19:25.298] - [2017-01-29 19:20:13.317] manual update device 3
- Attachments
-
- z-way-server.zip
- (12.46 KiB) Downloaded 239 times
Re: Current status is not correct
Did you find anything in the log?