That is valid if you are running the new app. If you are not you may want to update to the Wiz v2 app to get the rssi.
I have a linksys velop ax mesh system. Rock solid about 100-115 devices. None of my other wifi bulbs do this. Just started happening recently.
Roughly -52 through -65 rssi on all my bulbs.
Same here. half mine won't show connected. It's a wifi issue, but it shouldn't be, they have plenty of signal strength. possibly might be too much, some interference maybe.
I have several of these bulbs currently working (locally) with a HomeBridge plugin.
Since they run local, I also have a firewall rule that blocks them from the internet.
I installed the app, ran discover, and no devices were discovered.
I verified I can ping the bulbs from network settings on hubitat.
I don't think it should be an issue that the bulbs are registered with Homebridge since it seems the Wiz App can control them locally just fine as well as HomeBridge.
(The main reason I want to add them to Habitat is for scenes - the Homebridge plugin I am using does not support them.)
Any advice?
Has anyone else encountered this?
Ping uses icmp on TCP were as the integration uses UDP.
Try removing the firewall rule and see if that works. You can also try the community driver as it uses TCP for communication and see if that works.
Pausing the firewall rule has no effect.
Homebridge, which is on the same subnet with the Hubitat and the lights has no problem discovering them. Similarly, the Wiz app also has no problem finding them.
I guess I could Wireshark the hubitat during discovery to see what's going on, but all that should be happening is a UDP broadcast on port 38899 with the content:
{"method":"registration","params":{"phoneMac":"<hub_mac_address>","register":false,"phoneIp":"<hub_ip_address>"}}
Then every bulb should respond on port 38900 with:
{"method":"registration","env":"pro","result":{"mac":"<light_address>","success":true}}
At least that's what Homebridge does...
To add - I fired up Wireshark and I don't see the Hubitat sending any UDP broadcasts at all.
I see a lot of MDNS multicasts and for some strange reason it looks like the Hubitat is scanning the local subnet with sequential ARP requests every few seconds. (I will have to look into this later...) But zero UDP frames and no other broadcasts.
Here is the entire sequence I captured filtering on the hub MAC while the hub was running discovery:
No. Time Source Destination Protocol Length Info
1 0.000000 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.191? Tell 10.0.1.2
2 0.614800 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.190? Tell 10.0.1.2
3 0.923789 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.191? Tell 10.0.1.2
4 1.535986 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.190? Tell 10.0.1.2
5 1.849836 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.191? Tell 10.0.1.2
6 2.769064 10-0-1-2.local 224.0.0.251 MDNS 261 Standard query response 0x0000 SRV, cache flush 1 1 60000 10-0-1-2.local TXT, cache flush PTR Hubitat Coolbreeze Castle._hap._tcp.local A, cache flush 10.0.1.2
7 3.379179 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.191? Tell 10.0.1.2
8 3.993989 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.192? Tell 10.0.1.2
9 4.915549 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.192? Tell 10.0.1.2
10 5.529859 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.191? Tell 10.0.1.2
11 5.837639 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.192? Tell 10.0.1.2
12 7.373130 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.192? Tell 10.0.1.2
13 7.679923 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.193? Tell 10.0.1.2
14 8.294631 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.192? Tell 10.0.1.2
15 8.908718 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.193? Tell 10.0.1.2
16 9.529920 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.192? Tell 10.0.1.2
17 9.830651 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.193? Tell 10.0.1.2
18 10.449322 10-0-1-2.local 224.0.0.251 MDNS 261 Standard query response 0x0000 SRV, cache flush 1 1 60000 10-0-1-2.local TXT, cache flush PTR Hubitat Coolbreeze Castle._hap._tcp.local A, cache flush 10.0.1.2
19 12.288403 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.193? Tell 10.0.1.2
20 12.595549 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.194? Tell 10.0.1.2
21 13.210612 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.193? Tell 10.0.1.2
22 14.135869 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
23 14.136963 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
24 15.360294 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.194? Tell 10.0.1.2
25 15.360601 10-0-1-2.local 224.0.0.251 MDNS 247 Standard query response 0x0000 SRV, cache flush 1 1 60000 10-0-1-2.local TXT, cache flush A, cache flush 10.0.1.2
26 15.360606 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
27 15.360929 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
28 15.667419 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.195? Tell 10.0.1.2
29 17.203498 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.194? Tell 10.0.1.2
30 17.510665 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.195? Tell 10.0.1.2
31 18.127990 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
32 18.127996 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
33 18.128167 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
34 18.432268 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
35 19.046405 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.195? Tell 10.0.1.2
36 19.660389 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.196? Tell 10.0.1.2
37 20.275644 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.195? Tell 10.0.1.2
38 20.584063 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.196? Tell 10.0.1.2
39 21.198250 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.195? Tell 10.0.1.2
40 21.504663 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.196? Tell 10.0.1.2
41 22.430729 10-0-1-2.local 224.0.0.251 MDNS 247 Standard query response 0x0000 SRV, cache flush 1 1 60000 10-0-1-2.local TXT, cache flush A, cache flush 10.0.1.2
42 23.347702 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.197? Tell 10.0.1.2
43 23.964343 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.196? Tell 10.0.1.2
44 25.189952 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.196? Tell 10.0.1.2
45 25.498035 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.197? Tell 10.0.1.2
46 27.344419 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
47 27.344778 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
48 27.346845 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.198? Tell 10.0.1.2
49 28.262586 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.198? Tell 10.0.1.2
50 28.876327 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.197? Tell 10.0.1.2
51 29.187108 10-0-1-2.local 224.0.0.251 MDNS 261 Standard query response 0x0000 SRV, cache flush 1 1 60000 10-0-1-2.local TXT, cache flush PTR Hubitat Coolbreeze Castle._hap._tcp.local A, cache flush 10.0.1.2
52 29.492102 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.198? Tell 10.0.1.2
53 30.719960 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.198? Tell 10.0.1.2
54 31.334450 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.199? Tell 10.0.1.2
55 32.260284 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.199? Tell 10.0.1.2
56 32.871355 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.198? Tell 10.0.1.2
57 33.178263 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.199? Tell 10.0.1.2
58 34.098720 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
59 34.713102 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.199? Tell 10.0.1.2
60 35.020347 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.200? Tell 10.0.1.2
61 35.634806 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.199? Tell 10.0.1.2
62 36.249730 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.200? Tell 10.0.1.2
63 36.249779 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
64 36.250009 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
65 37.170726 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.200? Tell 10.0.1.2
66 37.478776 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
67 37.478783 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
68 37.478961 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
69 38.399952 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
70 40.549879 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
71 40.551227 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
72 40.551533 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
73 40.551537 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
74 41.778783 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
75 41.778791 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
76 41.778878 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
77 41.779136 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
78 43.007675 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.202? Tell 10.0.1.2
79 43.622062 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.201? Tell 10.0.1.2
80 43.929199 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.202? Tell 10.0.1.2
81 44.543399 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.201? Tell 10.0.1.2
82 46.387036 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.202? Tell 10.0.1.2
83 47.000831 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.203? Tell 10.0.1.2
84 47.615259 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.202? Tell 10.0.1.2
85 48.537200 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.202? Tell 10.0.1.2
86 48.844455 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.203? Tell 10.0.1.2
87 49.151367 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
88 50.696549 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.204? Tell 10.0.1.2
89 51.302924 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.203? Tell 10.0.1.2
90 51.612505 10-0-1-2.local 224.0.0.251 MDNS 261 Standard query response 0x0000 SRV, cache flush 1 1 60000 10-0-1-2.local TXT, cache flush PTR Hubitat Coolbreeze Castle._hap._tcp.local A, cache flush 10.0.1.2
91 51.920098 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.204? Tell 10.0.1.2
92 52.530661 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.203? Tell 10.0.1.2
93 54.374167 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
94 54.374743 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
95 54.374884 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.204? Tell 10.0.1.2
96 54.682609 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.205? Tell 10.0.1.2
97 55.295131 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
98 55.295567 10-0-1-2.local 224.0.0.251 MDNS 84 Standard query response 0x0000 A, cache flush 10.0.1.2
99 55.295570 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.204? Tell 10.0.1.2
100 55.602560 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.205? Tell 10.0.1.2
101 56.217113 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.204? Tell 10.0.1.2
102 56.830918 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.205? Tell 10.0.1.2
103 58.674294 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.206? Tell 10.0.1.2
104 59.595758 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.206? Tell 10.0.1.2
105 60.212021 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.205? Tell 10.0.1.2
106 60.824919 10-0-1-2.local 224.0.0.251 MDNS 261 Standard query response 0x0000 SRV, cache flush 1 1 60000 10-0-1-2.local TXT, cache flush PTR Hubitat Coolbreeze Castle._hap._tcp.local A, cache flush 10.0.1.2
107 62.053949 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.206? Tell 10.0.1.2
108 62.668039 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.207? Tell 10.0.1.2
109 64.204030 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.206? Tell 10.0.1.2
110 64.512452 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.207? Tell 10.0.1.2
111 66.047649 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.207? Tell 10.0.1.2
112 66.354288 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.208? Tell 10.0.1.2
113 67.582828 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.208? Tell 10.0.1.2
114 68.197582 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.207? Tell 10.0.1.2
115 68.504591 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.208? Tell 10.0.1.2
116 70.347681 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.209? Tell 10.0.1.2
117 70.962488 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.208? Tell 10.0.1.2
118 72.498625 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.209? Tell 10.0.1.2
119 74.034340 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.209? Tell 10.0.1.2
120 74.341280 10-0-1-2.local Broadcast ARP 60 Who has 10.0.1.210? Tell 10.0.1.2
Here's what it looks like when Homebridge does it (Homebridge is running on the same box as pihole - so Wireshark show that name):
No. Time Source Destination Protocol Length Info
1 0.000000 pi.hole wiz_3b4344.localdomain UDP 143 38900 → 38899 Len=101
2 0.000003 pi.hole wiz_3c6dfe.localdomain UDP 143 38900 → 38899 Len=101
3 0.000022 pi.hole wiz_3e9b49.localdomain UDP 143 38900 → 38899 Len=101
4 0.000031 pi.hole wiz_855143.localdomain UDP 143 38900 → 38899 Len=101
5 0.000047 pi.hole wiz_3f2331.localdomain UDP 143 38900 → 38899 Len=101
6 0.000051 pi.hole 255.255.255.255 UDP 143 38900 → 38899 Len=101
7 0.000109 pi.hole wiz_3da9a2.localdomain UDP 143 38900 → 38899 Len=101
8 0.000123 pi.hole wiz_3ef9fd.localdomain UDP 143 38900 → 38899 Len=101
9 0.000138 pi.hole wiz_3bf3fc.localdomain UDP 143 38900 → 38899 Len=101
10 0.000154 pi.hole wiz_3a5739.localdomain UDP 143 38900 → 38899 Len=101
11 0.000246 pi.hole wiz_3f79ac.localdomain UDP 143 38900 → 38899 Len=101
12 0.008072 wiz_3c6dfe.localdomain pi.hole UDP 126 38899 → 38900 Len=84
13 0.012968 wiz_3f2331.localdomain pi.hole UDP 126 38899 → 38900 Len=84
14 0.013127 wiz_855143.localdomain pi.hole UDP 126 38899 → 38900 Len=84
15 0.013289 wiz_3c6dfe.localdomain pi.hole UDP 126 38899 → 38900 Len=84
16 0.013447 wiz_3b4344.localdomain pi.hole UDP 126 38899 → 38900 Len=84
17 0.014430 pi.hole wiz_3c6dfe.localdomain UDP 82 38900 → 38899 Len=40
18 0.015180 pi.hole wiz_3c6dfe.localdomain UDP 82 38900 → 38899 Len=40
19 0.015189 pi.hole wiz_3f2331.localdomain UDP 82 38900 → 38899 Len=40
20 0.015201 pi.hole wiz_855143.localdomain UDP 82 38900 → 38899 Len=40
21 0.015210 pi.hole wiz_3b4344.localdomain UDP 82 38900 → 38899 Len=40
22 0.016430 wiz_3e9b49.localdomain pi.hole UDP 126 38899 → 38900 Len=84
23 0.017145 wiz_855143.localdomain pi.hole UDP 126 38899 → 38900 Len=84
24 0.017311 wiz_3da9a2.localdomain pi.hole UDP 126 38899 → 38900 Len=84
25 0.017560 wiz_3ef9fd.localdomain pi.hole UDP 126 38899 → 38900 Len=84
26 0.017936 pi.hole wiz_3e9b49.localdomain UDP 82 38900 → 38899 Len=40
27 0.017940 pi.hole wiz_855143.localdomain UDP 82 38900 → 38899 Len=40
28 0.017951 pi.hole wiz_3da9a2.localdomain UDP 82 38900 → 38899 Len=40
29 0.017964 pi.hole wiz_3ef9fd.localdomain UDP 82 38900 → 38899 Len=40
30 0.019954 wiz_3ef9fd.localdomain pi.hole UDP 126 38899 → 38900 Len=84
31 0.020157 wiz_3a5739.localdomain pi.hole UDP 126 38899 → 38900 Len=84
32 0.020313 wiz_3a5739.localdomain pi.hole UDP 126 38899 → 38900 Len=84
33 0.020544 pi.hole wiz_3ef9fd.localdomain UDP 82 38900 → 38899 Len=40
34 0.020552 wiz_3da9a2.localdomain pi.hole UDP 126 38899 → 38900 Len=84
35 0.020703 wiz_3e9b49.localdomain pi.hole UDP 126 38899 → 38900 Len=84
36 0.020913 wiz_3f79ac.localdomain pi.hole UDP 126 38899 → 38900 Len=84
37 0.021133 wiz_3f79ac.localdomain pi.hole UDP 126 38899 → 38900 Len=84
38 0.021163 pi.hole wiz_3a5739.localdomain UDP 82 38900 → 38899 Len=40
39 0.021173 pi.hole wiz_3a5739.localdomain UDP 82 38900 → 38899 Len=40
40 0.021182 pi.hole wiz_3da9a2.localdomain UDP 82 38900 → 38899 Len=40
41 0.021191 pi.hole wiz_3e9b49.localdomain UDP 82 38900 → 38899 Len=40
42 0.021400 wiz_3bf3fc.localdomain pi.hole UDP 126 38899 → 38900 Len=84
43 0.021495 pi.hole wiz_3f79ac.localdomain UDP 82 38900 → 38899 Len=40
44 0.021535 wiz_3bf3fc.localdomain pi.hole UDP 126 38899 → 38900 Len=84
45 0.021745 wiz_3b4344.localdomain pi.hole UDP 126 38899 → 38900 Len=84
46 0.022603 pi.hole wiz_3bf3fc.localdomain UDP 82 38900 → 38899 Len=40
47 0.022607 pi.hole wiz_3f79ac.localdomain UDP 82 38900 → 38899 Len=40
48 0.022613 pi.hole wiz_3bf3fc.localdomain UDP 82 38900 → 38899 Len=40
49 0.022617 pi.hole wiz_3b4344.localdomain UDP 82 38900 → 38899 Len=40
50 0.024640 wiz_3f2331.localdomain pi.hole UDP 126 38899 → 38900 Len=84
51 0.025152 pi.hole wiz_3f2331.localdomain UDP 82 38900 → 38899 Len=40
52 0.031329 wiz_3e9b49.localdomain pi.hole UDP 250 38899 → 38900 Len=208
53 0.033931 wiz_3ef9fd.localdomain pi.hole UDP 250 38899 → 38900 Len=208
54 0.034112 wiz_3c6dfe.localdomain pi.hole UDP 250 38899 → 38900 Len=208
55 0.034305 wiz_3b4344.localdomain pi.hole UDP 250 38899 → 38900 Len=208
56 0.034533 wiz_855143.localdomain pi.hole UDP 250 38899 → 38900 Len=208
57 0.034770 wiz_3a5739.localdomain pi.hole UDP 250 38899 → 38900 Len=208
58 0.035342 wiz_3f79ac.localdomain pi.hole UDP 250 38899 → 38900 Len=208
59 0.036532 wiz_3f2331.localdomain pi.hole UDP 250 38899 → 38900 Len=208
60 0.037803 wiz_3da9a2.localdomain pi.hole UDP 250 38899 → 38900 Len=208
61 0.038066 wiz_3b4344.localdomain pi.hole UDP 250 38899 → 38900 Len=208
62 0.038249 wiz_3e9b49.localdomain pi.hole UDP 250 38899 → 38900 Len=208
63 0.039514 wiz_3c6dfe.localdomain pi.hole UDP 250 38899 → 38900 Len=208
64 0.039989 wiz_3ef9fd.localdomain pi.hole UDP 250 38899 → 38900 Len=208
65 0.041296 wiz_3a5739.localdomain pi.hole UDP 250 38899 → 38900 Len=208
66 0.041821 wiz_3f79ac.localdomain pi.hole UDP 250 38899 → 38900 Len=208
67 0.042105 wiz_3bf3fc.localdomain pi.hole UDP 250 38899 → 38900 Len=208
68 0.042927 wiz_855143.localdomain pi.hole UDP 250 38899 → 38900 Len=208
69 0.044738 wiz_3f2331.localdomain pi.hole UDP 250 38899 → 38900 Len=208
70 0.045985 wiz_3da9a2.localdomain pi.hole UDP 250 38899 → 38900 Len=208
71 0.049983 wiz_3bf3fc.localdomain pi.hole UDP 250 38899 → 38900 Len=208
72 10.757818 pi.hole wiz_3e9b49.localdomain UDP 75 38900 → 38899 Len=33
73 10.757843 pi.hole wiz_3f79ac.localdomain UDP 75 38900 → 38899 Len=33
74 10.759234 pi.hole wiz_3a5739.localdomain UDP 75 38900 → 38899 Len=33
75 10.760482 pi.hole wiz_3ef9fd.localdomain UDP 75 38900 → 38899 Len=33
76 10.762900 pi.hole wiz_3bf3fc.localdomain UDP 75 38900 → 38899 Len=33
77 10.764086 pi.hole wiz_855143.localdomain UDP 75 38900 → 38899 Len=33
78 10.765238 wiz_3f79ac.localdomain pi.hole UDP 179 38899 → 38900 Len=137
79 10.765380 pi.hole wiz_3c6dfe.localdomain UDP 75 38900 → 38899 Len=33
80 10.767587 pi.hole wiz_3da9a2.localdomain UDP 75 38900 → 38899 Len=33
81 10.767598 pi.hole wiz_3b4344.localdomain UDP 75 38900 → 38899 Len=33
82 10.767617 pi.hole wiz_3f2331.localdomain UDP 75 38900 → 38899 Len=33
83 10.767914 wiz_3e9b49.localdomain pi.hole UDP 178 38899 → 38900 Len=136
84 10.768829 wiz_3a5739.localdomain pi.hole UDP 179 38899 → 38900 Len=137
85 10.769003 wiz_3ef9fd.localdomain pi.hole UDP 178 38899 → 38900 Len=136
86 10.772575 wiz_3bf3fc.localdomain pi.hole UDP 179 38899 → 38900 Len=137
87 10.772772 wiz_855143.localdomain pi.hole UDP 178 38899 → 38900 Len=136
88 10.777228 wiz_3da9a2.localdomain pi.hole UDP 178 38899 → 38900 Len=136
89 10.778153 wiz_3f2331.localdomain pi.hole UDP 179 38899 → 38900 Len=137
90 10.778312 wiz_3c6dfe.localdomain pi.hole UDP 178 38899 → 38900 Len=136
91 10.779697 wiz_3b4344.localdomain pi.hole UDP 178 38899 → 38900 Len=136
Renaming Wiz bulbs in Hubitat doesn’t work for me. The bulbs get a generic name Wiz RGBW Light + IP address name which is not the same as the name I’ve given them via the Wiz v2 iOS app. I’m able to change the name under the Device information page in Hubitat and after saving the name appears atop the device info page (see screenshot) but when I return to the Device List page, the original name is back. I’ve restarted the hub but it did not help.
Running Platform Version 2.3.4.117 on hw Rev C-7.
Does setting the "Device label" stay? I've been using that field instead of "Device name".
1 Like
Use Device Label. That is the "friendly" name instead of the long name or integration name. The Device Label will show up on dashboards and in other apps if you fill it out.
1 Like
I was away from home for over a month and had everything powered down, and I had neglected to assign static (or DHCP reserved) IP addresses for my Wiz strips. Now they have been all been assigned new IP addresses, and I'm trying to update all these devices in my Hubitat, using the IP addresses as reported by the Wiz app. I've tried using the "Set IP address" field on the device page and then saving the device, but this doesn't seem to work. Any other way I can update the IP addresses? Thanks.
The integration should be able to pick IP changes automatically as long as multicasts work. This sounds like connectivity between hub and Wiz devices is off for some reason. Are they on the same LAN/router, like hub is 192.168.1.4 and Wiz device is 192.168.1.6?
Everything's on the same Class C with nothing fancy. And in fact, today it did pick up the new IP addresses and everything is now working. I wonder why today, 16 days after I returned home and turned everything on. Perhaps because I rebooted the Hubitat last night (though it hadn't yet when I tested it right after rebooting)? In any case, I've now reserved the addresses on the DHCP server so this doesn't hapen again.
Any Ideas on how to slow down my wiz bulbs? i'm getting excessive events pretty regularly. Looks like they are rapidly attempting to switch between ct and scenes.
Mine are going crazy too. I think it's been triggered by something in the 2.3.4.134 update. I believe that @gopher.ny is the integration developer/maintainer.
Here's a page of events:
Try changing the CT to something diffrent. I use 2700 as well and see it to. but i think if you use something like 2800 it won't happen the same way.
I think I see what triggers the issue. Using built-in Wiz scenes that are CT based causes the continuous events. Wiz scenes that are RGB based do not cause the event issue. Setting a manual CT value via Hubitat also does not cause the issue.
So is this a Wiz issue or a Hubitat issue? I don't know.
In my case I inadvertently identified the issue when the power to the lights was turned off and then on with the Wiz on recovery set to a CT scene. It just so happened to happen at about the same time I applied the latest Hubitat release.
Noted and reproduced, there will be a change to address excessive events in the next build.
2 Likes
I decided to give Wiz a whirl again. The built in integration still can't find the bulb on my eero network. Was this fixed @gopher.ny? I gave up on Wiz in the fall, but bought an A21 bulb again. Community driver works, but not the built-in integration. Never finds the bulb. Of note, the Hubitat hub is on 192.168.4.126 and the bulb is on 192.168.5.14. But the Hubitat network test page can ping the bulb just fine.
