I have an older (r1.1) sensor, that I never ran live as I was renovating the house. Now I have the perfect place for it, but need to set it up.

So I install chrome, the SC chrome setup extension which seems to open up pages in my default browsers. So I paste URIs back to a chrome tab) and struck what may be a firmware issue:

Entered the node details for the website, sensor’s mac address, eg (xx:xx:xx:xx:xx:xx, where xx is hex values) and followed the link to setup the sensor. This ‘terminal page’ shows the correct serial port (via local USB). The page prompts to:

OK, so the device is up to date, but chrome is still saying the site is ‘Waiting for your kit’s data’. The sensor has a local IP. Perhaps I just have to get the outbound data through the firewall- but there is no blocking on TCP:80 and 443.

After waiting a few hours, the Profile is yet to see any data.

The only packets the firewall is stopping are broadcasts to 255.255.255.255 on UDP:55555 and the request to rn.microchip.com (198.175.253.161) on TCP:21

Why? Who are Microchip Technology Inc. (MICROC)? Why is the sensor sending data there?
I opened TCP:21 (but why should is it needed?).

Will leave it a long time again, see if it heals itself…

Allowing TCP:21 made no difference

Now opening access to any host, on any port, for the Sensor. Seemingly this makes no difference too, except for the UDP:5555 broadcasts.

P.S.
From the start, valid data from the sensor showed in the terminal window in the setup tab. It shows my old Wifi password from 2 years ago, and stream of ‘healthy’ data:

So it is caching data locally instead of sending it up to the website. And it doesn’t like its Internet connection, although it does connect.

What must it be able to talk to, and on what ports? This is not in the documentation.

It does however hint: ‘Your firewall is blocking the mac address of your SCK’ but that is vague- what ports does it need open outbound or inbound to send the MAC? Surely it is a PUT request from the sensor over TCP:80 or 443? If it is from the Chrome client, that would work too.

Restarting the sensor isn’t helping with the errors, so I inserted a new TF card to see if it would write the logs to that in the meantime. But alas, no difference. Then found the heading in the doc that says it is an extra feature that needs to be added manually.

Anyone have any ideas on what else to try? How to get the data published?

Info now stops updating in babelfish. Not sure what the next step is. Am I done? Or is there another step? Tried many times to press the save button at the top. Not sure if that is necessary or it the process has just stopped.

Often this pops up:To configure your kit you will need to install the Smart Citizen Kit App for ChromeAdd to Chrome You can also install it manually from the Chrome store and refresh the page.

Makes the user think the extension instance is no longer working. But it probably is… anyhow…

My guess is that the SCK is working, but the site is not accepting the data. So one last re-flash, and instead of looking for verification in the babelfish terminal, I’ll rely on seeing the outbound traffic at the wifi network’s gateway.

Which didn’t work wither, as it only makes internet requests when booting and resetting. Maybe I will create a SSID without any encryption- see if it is my 17 char wpa2 that is failing.

OK, so now I am watching the firewall logging every outbound packet from the SCK. (All are allowed to ANY). On resetting the SCK, no data is seen. Only when setting the wifi config oin the babelfish terminal, does the SCK start talking to the network; one UDP packet to 255.255.255.255:55555.