New light tested - works as well

[fribse]

Just got my very small Neewer RGB176, and that works fine as well:

[fribse]

Today it showed the channel: But newerlite still crashed 😢

[fribse]

Latest logfiles with the new commit:

16:20:41] - A custom preferences file was found for C0:50:A7:8C:95:BA!
[16:20:41] - Attempting to link to light 1 [NEEWER-SNL660] MAC Address: CE:D9:49:A3:1F:F7 (Attempt 1 of 6)
[16:20:45] - Successfully linked to light 1 [NEEWER-SNL660] MAC Address: CE:D9:49:A3:1F:F7
[16:20:46] - Attempting to link to light 2 [NEEWER-SNL660] MAC Address: DF:88:56:D0:72:A8 (Attempt 1 of 6)
[16:20:49] - Successfully linked to light 2 [NEEWER-SNL660] MAC Address: DF:88:56:D0:72:A8
[16:20:50] - Attempting to link to light 3 [NEEWER-RGB176] MAC Address: C0:50:A7:8C:95:BA (Attempt 1 of 6)
[16:20:51] - Successfully linked to light 3 [NEEWER-RGB176] MAC Address: C0:50:A7:8C:95:BA
[16:20:55] - Background Thread Running
[16:20:57] - Going into send mode
[16:20:58] - Leaving send mode and going back to background thread
[16:21:01] - Background Thread Running
[16:21:03] - Going into send mode
[16:21:03] - Leaving send mode and going back to background thread
[16:21:06] - Background Thread Running
[16:21:07] - We don't have enough information from light [NEEWER-RGB176] to get the status.
bytearray(b'6')
[16:21:10] - Background Thread Running
[16:21:11] - Going into send mode
[16:21:12] - Leaving send mode and going back to background thread
[16:21:14] - Going into send mode
[16:21:15] - Leaving send mode and going back to background thread
[16:21:15] - Background Thread Running
[16:21:17] - We don't have enough information from light [NEEWER-RGB176] to get the status.
bytearray(b'6')
[16:21:17] - Going into send mode
[16:21:20] - Leaving send mode and going back to background thread
[16:21:23] - Background Thread Running
[16:21:28] - Background Thread Running
[16:21:33] - Going into send mode
[16:21:34] - Leaving send mode and going back to background thread
[16:21:34] - Background Thread Running
[16:21:35] - Going into send mode
[16:21:35] - Leaving send mode and going back to background thread
[16:21:38] - Background Thread Running
[16:21:44] - Background Thread Running
[16:21:48] - Waiting for the background thread to terminate...
[16:21:48] - Stopping the background thread
[16:21:50] - You asked NeewerLite-Python to save the last used light parameters on exit, so we will do that now...
[16:21:50] - Saving last used parameters for light #1 (1 of 3)
[16:21:50] - Exported preferences for [NEEWER-SNL660] to D:\neewer\light_prefs\CED949A31FF7
[16:21:50] - Saving last used parameters for light #2 (2 of 3)
[16:21:50] - Exported preferences for [NEEWER-SNL660] to D:\neewer\light_prefs\DF8856D072A8
[16:21:50] - Saving last used parameters for light #3 (3 of 3)
[16:21:50] - Exported preferences for [NEEWER-RGB176] to D:\neewer\light_prefs\C050A78C95BA
[16:21:50] - We will now attempt to unlink from the lights...
[16:21:50] - Attempting to unlink from light #1 (1 of 3 lights to unlink)
[16:21:53] - Successfully unlinked from light 1 [NEEWER-SNL660] MAC Address: CE:D9:49:A3:1F:F7
[16:21:53] - Attempting to unlink from light #2 (2 of 3 lights to unlink)
[16:21:56] - Successfully unlinked from light 2 [NEEWER-SNL660] MAC Address: DF:88:56:D0:72:A8
[16:21:56] - Attempting to unlink from light #3 (3 of 3 lights to unlink)
[16:21:59] - Successfully unlinked from light 3 [NEEWER-RGB176] MAC Address: C0:50:A7:8C:95:BA
[16:21:59] - Closing the program NOW

So it didn't crash, and kept talking to it... That's the only type of error I see from the log...

[taburineagle]

Ah, yes, that's very helpful! So it is the RGB176 that's having the issue.

[16:21:17] - We don't have enough information from light [NEEWER-RGB176] to get the status.
bytearray(b'6')

I'm not really sure what (b'6') is, but that's a one element array and not several (normal statuses are 5 elements, including a main part, category, length, payload and checksum) as I'm used to seeing, so it's definitely coming up short on one of the status requests. I'm curious which status request it's having issues with though. I'm assuming the GUI shows a status similar to:

  LINKED
ON / CH. ---

When that error is being displayed, correct? That means the RGB176 is sending the power state, but not the channel state (which makes sense, because I don't think it uses channels.) I'm still a bit confused why it was originally sending "Channel 0" as its channel, but that may have just been a false result.

[taburineagle]

Also, if you turn the RGB176 off (well, use the program to put it into energy saving mode), does the status then update to this?:

   LINKED
STBY / CH. ---

[fribse]

I just tested it again.

I still see the message:

[16:50:30] - We don't have enough information from light [NEEWER-RGB176] to get the status.
bytearray(b'6')

At first discovery it shows:

When turned off it shows:

When turned on it shows:

So no on / off settings shown.

[taburineagle]

Got you, OK - well, according to that, the light doesn't actually send any tangible data to the characteristic that feeds that information back (or it doesn't even have that characteristic in it to begin with), so it might be better for me to disable checking that state for that specific kind of light. Interesting...

[taburineagle]

Ahhhhhhhhhh - just checked the description of that light out on Amazon, and it's written right there:

So that explains the channel situation at least 😊

[taburineagle]

I'm closing this one as the main issues are handled in other issue requests 😊