From Newsgroup: uk.telecom.mobile

My Fitbit Charge 6 seems not to charge from an integrated USB-C socket
(MK) but charges okay from a phone charger (Apple). Is this correct
and will there be any reason?
--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: uk.telecom.mobile

Scott wrote:

My Fitbit Charge 6 seems not to charge from an integrated USB-C socket
(MK) but charges okay from a phone charger (Apple). Is this correct
and will there be any reason?

Does the Fitbit require "PD charging", likely your socket only provides
"dumb" charging signalled by resistors?
--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: uk.telecom.mobile

Scott <newsgroups@gefion.myzen.co.uk> wrote:

My Fitbit Charge 6 seems not to charge from an integrated USB-C socket
(MK) but charges okay from a phone charger (Apple). Is this correct
and will there be any reason?

USB-C devices are supposed to negotiate with USB-C chargers, in crude terms please turn the power on followed by a conversation about the charge
voltage. Unfortunately not all devices conduct this conversation. Cheap
devices have a rCLdumbrCY USB-C connector but are delivered with a USB-C to USB-A cable. USB-A power supplies are rCLalways onrCY.

There more to USB-C than just the shape of the connector, and
implementation is very variable.

--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: uk.telecom.mobile

On Wed, 11 Feb 2026 19:28:03 -0000 (UTC), Tweed
<usenet.tweed@gmail.com> wrote:

Scott <newsgroups@gefion.myzen.co.uk> wrote:

My Fitbit Charge 6 seems not to charge from an integrated USB-C socket
(MK) but charges okay from a phone charger (Apple). Is this correct
and will there be any reason?

USB-C devices are supposed to negotiate with USB-C chargers, in crude terms >please turn the power on followed by a conversation about the charge
voltage. Unfortunately not all devices conduct this conversation. Cheap >devices have a odumbo USB-C connector but are delivered with a USB-C to
USB-A cable. USB-A power supplies are oalways ono.

There more to USB-C than just the shape of the connector, and
implementation is very variable.

Sorry,but I have made a mistake. It's USB-A not USB-C. The MK socket
has USB-A and USB-C ports. Fitbit does not seem to work with the USB-A
port but works okay with an older (USB-A) Apple charger. Does this
make a difference? Are you thinking the cheap device is the Fitbit or
the socket, made by MK?
--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: uk.telecom.mobile

Scott <newsgroups@gefion.myzen.co.uk> wrote:

On Wed, 11 Feb 2026 19:28:03 -0000 (UTC), Tweed
<usenet.tweed@gmail.com> wrote:

Scott <newsgroups@gefion.myzen.co.uk> wrote:

My Fitbit Charge 6 seems not to charge from an integrated USB-C socket
(MK) but charges okay from a phone charger (Apple). Is this correct
and will there be any reason?

USB-C devices are supposed to negotiate with USB-C chargers, in crude terms >> please turn the power on followed by a conversation about the charge
voltage. Unfortunately not all devices conduct this conversation. Cheap
devices have a -odumb-o USB-C connector but are delivered with a USB-C to
USB-A cable. USB-A power supplies are -oalways on-o.

There more to USB-C than just the shape of the connector, and
implementation is very variable.

Sorry,but I have made a mistake. It's USB-A not USB-C. The MK socket
has USB-A and USB-C ports. Fitbit does not seem to work with the USB-A
port but works okay with an older (USB-A) Apple charger. Does this
make a difference? Are you thinking the cheap device is the Fitbit or
the socket, made by MK?

Does the MK USB-A port work with anything else? Broken?

--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: uk.telecom.mobile

On Wed, 11 Feb 2026 20:49:06 -0000 (UTC), Tweed
<usenet.tweed@gmail.com> wrote:

Scott <newsgroups@gefion.myzen.co.uk> wrote:

On Wed, 11 Feb 2026 19:28:03 -0000 (UTC), Tweed
<usenet.tweed@gmail.com> wrote:

Scott <newsgroups@gefion.myzen.co.uk> wrote:

My Fitbit Charge 6 seems not to charge from an integrated USB-C socket >>>> (MK) but charges okay from a phone charger (Apple). Is this correct
and will there be any reason?

USB-C devices are supposed to negotiate with USB-C chargers, in crude terms >>> please turn the power on followed by a conversation about the charge
voltage. Unfortunately not all devices conduct this conversation. Cheap
devices have a ?dumb? USB-C connector but are delivered with a USB-C to
USB-A cable. USB-A power supplies are ?always on?.

There more to USB-C than just the shape of the connector, and
implementation is very variable.

Sorry,but I have made a mistake. It's USB-A not USB-C. The MK socket
has USB-A and USB-C ports. Fitbit does not seem to work with the USB-A
port but works okay with an older (USB-A) Apple charger. Does this
make a difference? Are you thinking the cheap device is the Fitbit or
the socket, made by MK?

Does the MK USB-A port work with anything else? Broken?

It works fine with other devices. I wonder if its output could be
rated too high or too low for Fitbit?
--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: uk.telecom.mobile

Scott <newsgroups@gefion.myzen.co.uk> wrote:

On Wed, 11 Feb 2026 20:49:06 -0000 (UTC), Tweed
<usenet.tweed@gmail.com> wrote:

Scott <newsgroups@gefion.myzen.co.uk> wrote:

On Wed, 11 Feb 2026 19:28:03 -0000 (UTC), Tweed
<usenet.tweed@gmail.com> wrote:

Scott <newsgroups@gefion.myzen.co.uk> wrote:

My Fitbit Charge 6 seems not to charge from an integrated USB-C socket >>>>> (MK) but charges okay from a phone charger (Apple). Is this correct
and will there be any reason?

USB-C devices are supposed to negotiate with USB-C chargers, in crude terms
please turn the power on followed by a conversation about the charge
voltage. Unfortunately not all devices conduct this conversation. Cheap >>>> devices have a ?dumb? USB-C connector but are delivered with a USB-C to >>>> USB-A cable. USB-A power supplies are ?always on?.

There more to USB-C than just the shape of the connector, and
implementation is very variable.

Sorry,but I have made a mistake. It's USB-A not USB-C. The MK socket
has USB-A and USB-C ports. Fitbit does not seem to work with the USB-A
port but works okay with an older (USB-A) Apple charger. Does this
make a difference? Are you thinking the cheap device is the Fitbit or
the socket, made by MK?

Does the MK USB-A port work with anything else? Broken?

It works fine with other devices. I wonder if its output could be
rated too high or too low for Fitbit?

Have you tried another cable? Could be pins not making proper contact.


--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: uk.telecom.mobile

On Wed, 11 Feb 2026 21:23:30 -0000 (UTC), Tweed
<usenet.tweed@gmail.com> wrote:

Scott <newsgroups@gefion.myzen.co.uk> wrote:

On Wed, 11 Feb 2026 20:49:06 -0000 (UTC), Tweed
<usenet.tweed@gmail.com> wrote:

Scott <newsgroups@gefion.myzen.co.uk> wrote:

On Wed, 11 Feb 2026 19:28:03 -0000 (UTC), Tweed
<usenet.tweed@gmail.com> wrote:

Scott <newsgroups@gefion.myzen.co.uk> wrote:

My Fitbit Charge 6 seems not to charge from an integrated USB-C socket >>>>>> (MK) but charges okay from a phone charger (Apple). Is this correct >>>>>> and will there be any reason?

USB-C devices are supposed to negotiate with USB-C chargers, in crude terms
please turn the power on followed by a conversation about the charge >>>>> voltage. Unfortunately not all devices conduct this conversation. Cheap >>>>> devices have a ?dumb? USB-C connector but are delivered with a USB-C to >>>>> USB-A cable. USB-A power supplies are ?always on?.

There more to USB-C than just the shape of the connector, and
implementation is very variable.

Sorry,but I have made a mistake. It's USB-A not USB-C. The MK socket
has USB-A and USB-C ports. Fitbit does not seem to work with the USB-A >>>> port but works okay with an older (USB-A) Apple charger. Does this
make a difference? Are you thinking the cheap device is the Fitbit or
the socket, made by MK?

Does the MK USB-A port work with anything else? Broken?

It works fine with other devices. I wonder if its output could be
rated too high or too low for Fitbit?

Have you tried another cable? Could be pins not making proper contact.

No, because Fitbit comes with its own cable with a magnetic connector
at the other end.
--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: uk.telecom.mobile

Scott <newsgroups@gefion.myzen.co.uk> wrote:

On Wed, 11 Feb 2026 21:23:30 -0000 (UTC), Tweed
<usenet.tweed@gmail.com> wrote:

Scott <newsgroups@gefion.myzen.co.uk> wrote:

On Wed, 11 Feb 2026 20:49:06 -0000 (UTC), Tweed
<usenet.tweed@gmail.com> wrote:

Scott <newsgroups@gefion.myzen.co.uk> wrote:

On Wed, 11 Feb 2026 19:28:03 -0000 (UTC), Tweed
<usenet.tweed@gmail.com> wrote:

Scott <newsgroups@gefion.myzen.co.uk> wrote:

My Fitbit Charge 6 seems not to charge from an integrated USB-C socket >>>>>>> (MK) but charges okay from a phone charger (Apple). Is this correct >>>>>>> and will there be any reason?

USB-C devices are supposed to negotiate with USB-C chargers, in crude terms
please turn the power on followed by a conversation about the charge >>>>>> voltage. Unfortunately not all devices conduct this conversation. Cheap >>>>>> devices have a ?dumb? USB-C connector but are delivered with a USB-C to >>>>>> USB-A cable. USB-A power supplies are ?always on?.

There more to USB-C than just the shape of the connector, and
implementation is very variable.

Sorry,but I have made a mistake. It's USB-A not USB-C. The MK socket >>>>> has USB-A and USB-C ports. Fitbit does not seem to work with the USB-A >>>>> port but works okay with an older (USB-A) Apple charger. Does this
make a difference? Are you thinking the cheap device is the Fitbit or >>>>> the socket, made by MK?

Does the MK USB-A port work with anything else? Broken?

It works fine with other devices. I wonder if its output could be
rated too high or too low for Fitbit?

Have you tried another cable? Could be pins not making proper contact.

No, because Fitbit comes with its own cable with a magnetic connector
at the other end.

Something else that occurred to me. Maybe the Fitbit is being economical
with the truth. If the MK outlet can only deliver the basic 500mA (either
by design or because the Fitbit and the outlet donrCOt use the same methods
for signalling a higher current) then the Fitbit might be charging very
slowly but claiming not to be charging. If you plug my iPad into a low
current charger it will claim not to be charging, but actually does very slowly. Try leaving the Fitbit plugged in overnight and see what happens.

--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: uk.telecom.mobile

On Thu, 12 Feb 2026 16:40:08 -0000 (UTC), Tweed
<usenet.tweed@gmail.com> wrote:

Scott <newsgroups@gefion.myzen.co.uk> wrote:

On Wed, 11 Feb 2026 21:23:30 -0000 (UTC), Tweed
<usenet.tweed@gmail.com> wrote:

Scott <newsgroups@gefion.myzen.co.uk> wrote:

On Wed, 11 Feb 2026 20:49:06 -0000 (UTC), Tweed
<usenet.tweed@gmail.com> wrote:

Scott <newsgroups@gefion.myzen.co.uk> wrote:

On Wed, 11 Feb 2026 19:28:03 -0000 (UTC), Tweed
<usenet.tweed@gmail.com> wrote:

Scott <newsgroups@gefion.myzen.co.uk> wrote:

My Fitbit Charge 6 seems not to charge from an integrated USB-C socket >>>>>>>> (MK) but charges okay from a phone charger (Apple). Is this correct >>>>>>>> and will there be any reason?

USB-C devices are supposed to negotiate with USB-C chargers, in crude terms
please turn the power on followed by a conversation about the charge >>>>>>> voltage. Unfortunately not all devices conduct this conversation. Cheap >>>>>>> devices have a ?dumb? USB-C connector but are delivered with a USB-C to >>>>>>> USB-A cable. USB-A power supplies are ?always on?.

There more to USB-C than just the shape of the connector, and
implementation is very variable.

Sorry,but I have made a mistake. It's USB-A not USB-C. The MK socket >>>>>> has USB-A and USB-C ports. Fitbit does not seem to work with the USB-A >>>>>> port but works okay with an older (USB-A) Apple charger. Does this >>>>>> make a difference? Are you thinking the cheap device is the Fitbit or >>>>>> the socket, made by MK?

Does the MK USB-A port work with anything else? Broken?

It works fine with other devices. I wonder if its output could be
rated too high or too low for Fitbit?

Have you tried another cable? Could be pins not making proper contact.

No, because Fitbit comes with its own cable with a magnetic connector
at the other end.

Something else that occurred to me. Maybe the Fitbit is being economical
with the truth. If the MK outlet can only deliver the basic 500mA (either
by design or because the Fitbit and the outlet donAt use the same methods
for signalling a higher current) then the Fitbit might be charging very >slowly but claiming not to be charging. If you plug my iPad into a low >current charger it will claim not to be charging, but actually does very >slowly. Try leaving the Fitbit plugged in overnight and see what happens.

I shall certainly try that - what my physics teacher used to refer to
as an ex-purr-iment.
--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: uk.telecom.mobile

Tweed <usenet.tweed@gmail.com> wrote:

Something else that occurred to me. Maybe the Fitbit is being economical
with the truth. If the MK outlet can only deliver the basic 500mA (either
by design or because the Fitbit and the outlet donrCOt use the same methods for signalling a higher current) then the Fitbit might be charging very slowly but claiming not to be charging. If you plug my iPad into a low current charger it will claim not to be charging, but actually does very slowly. Try leaving the Fitbit plugged in overnight and see what happens.

I would have thought 500mA would be ample. These things must only have a
tiny battery - perhaps 200-300mAh - so I doubt it would need any fast
charging modes. Maybe the MK outlet doesn't do the right kind of thing with the USB data pins that the Fitbit is expecting? I assume the wall socket
does the USB battery charging spec:

https://en.wikipedia.org/wiki/USB_hardware#USB_battery_charging

but here it says: https://buildings.honeywell.com/content/dam/hbtbt/en/documents/document-lists/mk-electric/gb_brochures/MK-USB-Charging-Solutions-brochure_UKMK446-0321-EN.pdf

"Dynamic Device Recognition
By detecting the nuances between the
differing charging configurations tablet
manufacturers use, the product can react
accordingly for optimal charging efficiency"

"What is Dynamic Device Recognition?
Manufacturers have each adopted differing configurations for charging their devices. MKrCOs USB Integrated sockets have been designed such that it understands
and recognises this nuance and is designed to react accordingly, rather than
be aligned to one specific charging configuration. This ensures we provide the optimum charging compatibility across a broad range of devices."

which sounds like it's trying to do something clever. Perhaps it's too
clever?

(in particular, cleverness can never account for things that might happen
after the product is manufactured - unless it can accept a firmware upgrade. Which is another can of worms)

Theo
--- Synchronet 3.21b-Linux NewsLink 1.2