No, nothing wrong, but Indigo's log file is always front and center, so it's easy to see.petergebruers wrote: ↑16 Nov 2017 17:18You would probably not have noticed it, if you did not have a look at that logfile... Or was something else wrong so you thought: "let us have a look at the log"?
Multiple Reports
Re: Multiple Reports
-
- Posts: 255
- Joined: 26 Jul 2015 17:29
Re: Multiple Reports
Thanks! So that is the exact opposite of Fibaro... Their detailed logfile is not visible to end users.
Anyway... I am curious so I'll try to setup a test this weekend. But first I have to solder a few connectors to my Z-Uno. For an LED project.
Anyway... I am curious so I'll try to setup a test this weekend. But first I have to solder a few connectors to my Z-Uno. For an LED project.
Meet me here: https://forum.fibaro.com/index.php?/pro ... rgebruers/ or here: memberlist.php?mode=viewprofile&u=564463
-
- Posts: 255
- Joined: 26 Jul 2015 17:29
Re: Multiple Reports
Here are the results of my test.
I load this FLIRS LED lamp code:
https://github.com/petergebruers/Z-Uno-BH1750
Then I click the service butten, this toggles the LED.
As expected, the Z-Uno sends 2 notifications: one for instance 0 and one for instance 1.
So do not see duplicated messages, like you see on your Indigo controller. This is Zway 2.3.6. This is the log:
I load this FLIRS LED lamp code:
https://github.com/petergebruers/Z-Uno-BH1750
Then I click the service butten, this toggles the LED.
As expected, the Z-Uno sends 2 notifications: one for instance 0 and one for instance 1.
So do not see duplicated messages, like you see on your Indigo controller. This is Zway 2.3.6. This is the log:
Code: Select all
[2017-11-19 09:52:44.704] [D] [zway] RECEIVED: ( 01 0F 00 04 00 43 07 60 0D 01 00 25 03 00 C4 00 3E )
[2017-11-19 09:52:44.705] [D] [zway] SENT ACK
[2017-11-19 09:52:44.705] [D] [zway] SETDATA devices.67.data.lastReceived = 0 (0x00000000)
[2017-11-19 09:52:44.705] [D] [zway] SETDATA devices.67.instances.1.commandClasses.37.data.level = False
[2017-11-19 09:52:44.725] [D] [zway] RECEIVED: ( 01 0B 00 04 00 43 03 25 03 00 C3 00 55 )
[2017-11-19 09:52:44.726] [D] [zway] SENT ACK
[2017-11-19 09:52:44.726] [D] [zway] SETDATA devices.67.data.lastReceived = 0 (0x00000000)
[2017-11-19 09:52:44.726] [D] [zway] SETDATA devices.67.instances.0.commandClasses.37.data.level = False
[2017-11-19 09:52:44.738] [I] [core] Notification: device-info (device-OnOff): {"dev":"Z-Wave.Me Switch (67.1)","l":"off","location":""}
[2017-11-19 09:52:44.809] [I] [core] Notification: device-info (device-OnOff): {"dev":"Z-Wave.Me Switch (67.0)","l":"off","location":""}
Meet me here: https://forum.fibaro.com/index.php?/pro ... rgebruers/ or here: memberlist.php?mode=viewprofile&u=564463
Re: Multiple Reports
Thanks for the test. I wonder what my Z-Stick is doing then?
The one thing I find that is interesting/different is that my controller reports "extra" information for the Z-Uno:
Even though I have the Z-Uno set up as mains powered, I get a battery report and two extra pieces of information, Current Load and Total Usage. I wonder if it's manufacturing reports for these other non-existent sensors?
The one thing I find that is interesting/different is that my controller reports "extra" information for the Z-Uno:
Even though I have the Z-Uno set up as mains powered, I get a battery report and two extra pieces of information, Current Load and Total Usage. I wonder if it's manufacturing reports for these other non-existent sensors?
Re: Multiple Reports
What controller is this? May be your controller uses some template for Z-Uno made by someone who used it for a battery device
Re: Multiple Reports
It's the latest version of Indigo talking to a Z-Stick Gen 5.
So I poked around a bit, and Indigo thinks that a Manufacturer ID of 0115 and Model ID of 01100001 is the ZME_ITEMP made by Duwi. Apparently that device doesn't send unsolicited reports and must be polled, so that is what Indigo is doing.
I found a setting in Indigo to disable polling, but I'm still getting these duplicates. I'm guessing it's got to still be something with the way that Indigo is interpreting the device. Not a big deal.
So I poked around a bit, and Indigo thinks that a Manufacturer ID of 0115 and Model ID of 01100001 is the ZME_ITEMP made by Duwi. Apparently that device doesn't send unsolicited reports and must be polled, so that is what Indigo is doing.
I found a setting in Indigo to disable polling, but I'm still getting these duplicates. I'm guessing it's got to still be something with the way that Indigo is interpreting the device. Not a big deal.