I have 11 locos which have HM7000 sound decoders. When my layout is operating all are normally powered, but the ones not running are in sidings (separate power district). I have other non-HM7000 locos. Four of the HM7000 locos are now giving me grief, in that that the bluetooth part is not working. When I start up the HM-DCC app, 7 locos are found, with the first marked as 'host' with a little blue 'H' next to its blue Bluetooth symbol. The four troublesome locos have red Bluetooth symbols, and don't respond to any commands (motion, lights or sound) from the app. The HM-DCC is running on an Apple iPad mini 6, iPadOS 17.2 (ie latest). The decoders are all up to date with the latest bluetooth firmware. If I put any of the four locos on my programming track, and write 0 into CV12 (ie control handed to DCC not bluetooth), when back on the main track they operate normally from my Elite DCC controller, including lights and sound. The 11 HM7000 locos are listed in the app in the order that they were installed. The first loco listed is a 'good' one, the second and third are troublesome ones. If I start up the layout (or just restart the HM-DCC app) with the first, 'good', loco off the track (ie unpowered), the app 'finds' the second ('troublesome') loco, and it gets a blue 'H' and a blue Bluetooth symbol. But none of the other locos are 'found' by the app and stay with red bluetooth symbols. So the 'troublesome' locos are not forming a mesh with anything else. And, the loco will not respond to commands from the app, ie no movement, lights or sound. But the app is resetting CV12 to 2, so the loco needs another trip to the programming track before it will run from the Elite controller again. What are peoples' thoughts? Send the decoders back as faulty? (one is in a sound-fitted 9F).