ChipChop Support Forum
Log in
Log out
Join the forum
My Details
REPLIES: 6
VIEWS: 395
BACK
REPLY TO THIS POST
Gizmo
13 Mar 2025
Misconfigured Device (somewhere near Prague, CZ)
Hi everyone,

This is a quick message for ChipChop users based in Czech Republic and connecting to the API1 node.

There is another misconfigured device this week trying to connect for the last few days (currently at around 30,000 requests) but the connection credentials are rubbish and the server can not directly inform whoever this little device belongs to so eventually it will ban the entire IP 🙀

I don't want all your devices to suddenly lose connection with ChipChop because your IP is banned and then you would have to wait until I can manually remove your IP from the blacklist ☠️

Connection requests are coming from IP: 90.xxx.xxx.122

and it's broadcasting the following:

    uuid: "jedinecna_identifikace_zarizeni"
    device_id: "pridelene_device_ID"

Can you please check if this is one of yours and pull the plug to put it out of its misery or re-program the poor thing 😂


G



Gizmo
18 Mar 2025

And now there is another one!

broadcasting:

uuid: sw7gjr-s6587d.tmep.cz
device_id: pridelene_device_ID

Seriously guys, I understand you don't want to pay few cents for the tmep.cz service to read your temp & humidity sensors (don't know if that's expensive or not good enough...not my problem) but why do you think that ChipChop would care about your account id from there (sw7gjr-s6587d.tmep.cz)???

For fuck sake, it's really not difficult, my grandma could setup a device with ChipChop beyond her grave (god bless her soul...hi Gran 👋😇)

I really don't want to ban anyone's sorry ass, it's lazy and I like when things work properly....so, If you follow one of the first basic tutorials and can't get it working (observe the serial monitor for messages) contact me via email and I'll get you up and running in minutes.

Note: ChipChop is not some shitty mqtt broker and it's not running something like Mosquito. Mqtt is only used (at the moment) as a transport as it's bit easier to fit on various micro-controllers and the ChipChop IoT engine handles it directly on the tcp data packet level (there is no pub/sub and crap like that)... so If you are not using the ChipChop library and trying to connect from something that is not a ESP/Arduino type of micro-controller it's most likely not going to work (it can be done, maybe, but I'll have to guide you how to set it up)

And, if this is your device...please, switch the fucking thing off until it's working properly, you are wasting your own bandwidth and worse you are potentially trusting an unstable device (don't blame me if your fridge has defrosted, plants died or house burned down)

So, get in touch and let's fix your little sensor :-)


G


Tomin
24 Nov 2025

Hi mr.

My appologize. It was from one of my customer, I think.
He mixed up values in a setting form where are Chipchop and TMEP values in one page :-(
Gizmo
24 Nov 2025

Hey Tom,

Thank you for letting me know, it was driving me crazy :-)

Anyway, good job with tmep.cz, it looks great. If you ever need anything from ChipChop (extra infrastructure, features etc) just let me know and will be more than happy to help.

All the best

Gizmo
Tomin
24 Nov 2025

Thanks a lot for your offer.
I will gladly accept your offer in a near future. Too many things to do ... :-(
Tomin
24 Nov 2025

In add., just to keep out of this trouble, I will remove proper URL from default value in a device.
Gizmo
24 Nov 2025

Thank you!

I am preparing to launch a completely new ChipChop super fast binary IoT communication protocol so this will not be an issue anymore and mqtt will only be available for private and commercial systems.

Drop me a message when you have some spare time, I have some things in the development pipeline that could be interesting to have a chat together.

G