I have a 2017 Wrangler Unlimited and I am trying to add SmartStart functionality to it. I installed the CHTHD2 T-Harness, DBALL2, and VSM350, however I am not seeing the green "Data Connection" LED illuminate at all on the VSM350.
I purchased the VSM350 from a seller who should have flashed it for the correct vehicle (most likely 2016 rather than 2017 because I don't think firmware is available yet for 2017 Wranglers, although AFAIK nothing has changed since 2016). I asked that the 3x remote start NOT be enabled, because I have factory remote start, so I don't want to change the functionality of my factory keyfob. As far as I can tell from the LED indicator on the DBALL2, I successfully programmed it with my vehicle. I'm not sure how to test that with the 3x start disabled, other than by utilizing the VSM350. I would assume that the green LED on the VSM350 would illuminate even if the DBALL2 was not programmed to my vehicle correctly.
Through the SmartStart installer portal I can successfully retrieve the VSM350 signal strength and GPS location, but none of the commands work. This is what I would expect with no green LED indicator. The indicator does not come on at all when power is supplied to the DBALL2, it doesn't flash - nothing. The amber LED flashes and becomes steady as expected.
I have a second VSM350 module which I tried installing and displayed the same behavior, so I am fairly confident the issue is on the DBALL2 side. Is it possible that the D2D connection between the modules isn't working due to the programming of the DBALL2, or would this be indicative of a hardware issue? I'm wondering if I should invest in the XKLOADER2 to try to fix the issue, or if I should just be purchasing a new DBALL2. Or, is it more simple than that and I have the wiring screwed up? I've included some pictures of the wiring. With the CHTHD2 T-Harness wiring is so simple I find it hard to believe that I could have messed it up, but who knows...
Any help is greatly appreciated!

UPDATE: I purchased an XKLOADER2. It seems to be recognized by XpressVIP, but the DBALL2 is not found. I'm guessing this means that the DBALL2 D2D port is bad?
UPDATE 2: got a replacement DBALL2 and everything worked properly, so the issue was definitely a bad DBALL2 module. Hope this helps someone else in the future.