No Support for NEEWER MS60B

[danir-de]

The MS60B is not supported. I can connect, but the status message is stuck to "Waiting to send...". The Light Preferences are already set to This light can only use CCT mode.

I can try to modify settings in the GUI once it reached "Waiting to send..." state, but it won't do anything on the lamp itself, even if the status value changes accoridng to what I change in the GUI.

The log shows me waiting for the state to change to "Waiting to send..." and then toggling some values.

---------------------------------------------------------
             NeewerLite-Python ver. 0.12d
                 by Zach Glenwright
  > https://github.com/taburineagle/NeewerLite-Python <
---------------------------------------------------------
[17:23:23] - Loading global preferences from file...
[17:23:23] - Starting program with command-line arguments
[17:23:23] -  > Launch GUI: True
[17:23:23] -  > Show Debug Strings on Console: True
[17:23:23] -  > Mode: CCT
[17:23:23] -  > Color Temperature: 5600K
[17:23:23] -  > Brightness: 100
[17:23:23] - Searching for new lights
[17:23:29] - Matching whitelisted address found - MAC Address: C0:26:BC:3D:80:E0, adding to the list
/home/danir/Software/Neewer/./NeewerLite-Python.py:2165: FutureWarning: BLEDevice.rssi is deprecated and will be removed in a future version of Bleak, use AdvertisementData.rssi instead
  printDebugString("Found new light! [" + currentScan[a].name + "] " + returnMACname() + " " + currentScan[a].address + " RSSI: " + str(currentScan[a].rssi) + " dBm")
[17:23:29] - Found new light! [NEEWER-MS60B] MAC Address: C0:26:BC:3D:80:E0 RSSI: -66 dBm
[17:23:29] - A custom preferences file was found for C0:26:BC:3D:80:E0!
Neewer/./NeewerLite-Python.py:1343: FutureWarning: BLEDevice.rssi is deprecated and will be removed in a future version of Bleak, use AdvertisementData.rssi instead
  self.setTheTable([availableLights[a][2] + " (" + availableLights[a][0].name + ")" + "\n  [ʀssɪ: " + str(availableLights[a][0].rssi) + " dBm]", availableLights[a][0].address, "Waiting", "Waiting to connect..."])
[17:23:29] - Attempting to link to light [NEEWER-MS60B] MAC Address: C0:26:BC:3D:80:E0 (Attempt 1 of 6)
[17:23:41] - Error linking to light [NEEWER-MS60B] MAC Address: C0:26:BC:3D:80:E0
[17:23:45] - Attempting to link to light [NEEWER-MS60B] MAC Address: C0:26:BC:3D:80:E0 (Attempt 2 of 6)
[17:23:57] - Error linking to light [NEEWER-MS60B] MAC Address: C0:26:BC:3D:80:E0
[17:24:01] - Attempting to link to light [NEEWER-MS60B] MAC Address: C0:26:BC:3D:80:E0 (Attempt 3 of 6)
[17:24:02] - Successful link on light [NEEWER-MS60B] MAC Address: C0:26:BC:3D:80:E0
[17:24:12] - Background Thread Running
[17:24:16] - Background Thread Running
[17:24:17] - Going into send mode
[17:24:18] - Leaving send mode and going back to background thread
[17:24:20] - Background Thread Running
[17:24:24] - Going into send mode
[17:24:24] - Leaving send mode and going back to background thread
[17:24:25] - Background Thread Running
[17:24:27] - Successful link on light [NEEWER-MS60B] MAC Address: C0:26:BC:3D:80:E0
[17:24:28] - Background Thread Running
[17:24:32] - Going into send mode
[17:24:32] - Leaving send mode and going back to background thread
[17:24:33] - Background Thread Running
[17:24:33] - Going into send mode
[17:24:34] - Leaving send mode and going back to background thread
[17:24:34] - Going into send mode
[17:24:35] - Leaving send mode and going back to background thread

[taburineagle]

Hi @danir-de - this looks to be a similar issue to #74 - some Neewer lights use something called "Infinity mode" which I think is slightly different than the normal control set. I need to get ahold of an Infinity controlled light and scan to see what the app is doing to control it to add support for those lights. One question for you though, do the "Turn Light On" and "Turn Light Off" buttons at the top work? If so, then it's definitely the same kind of control issue as #74.

[danir-de]

Both of my Lamps (CB60 RGB & MS60B) use the new Infinity mode system in Bluetooth mode. My CB60 sporadically works with your app but sometimes only on and off work. So that one is likely to be related with #74 .

Both lights also are named NW... by default (unless I rename them), as seen above in my first message.

The MS60B doesn't work at all, even just turning on or off doesn't do anything, so this issue might be related to something else? It's an even newer model though 🤔

[taburineagle]

Got you, got you - yeah, I need to get ahold of an Infinity light and see how the app sends the command strings to the lights. They may have changed a few things since 2021 in their control scheme that the value sent to the light differs in just a slight way.

[taburineagle]

I ordered an SL90, which is also an Infinity light - I want to see how that one communicates with the Neewer app, and hopefully that will let me understand the MS60B as well... we will see!

[taburineagle]

OK @danir-de - I have added Infinity support in a branch from the main branch. I haven't added the MS60B in to the mix yet, but I will ASAP!

[taburineagle]

OK @danir-de - long time no write... I'm working on releasing the next version of NeewerLite-Python, and I've added Infinity support to the program, so the new version should work with the MS60B. I don't have one to test yet personally, but I have tested the Infinity command set with the SL90 and it works fine with that... so I'll let you know when it's released!

[taburineagle]

@danir-de - I'm planning on releasing the new version of NeewerLite-Python this week (ha, I hope so, I've been working on it since this issue first appeared), but as I've not heard anything from you in a while, I'll close this issue as well. Feel free to make another one if you notice anything else!