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