I’m not so sure this process actually works. I have followed these steps and the ones that came with it to do a hard reset, and it doesn’t seem to actually do a hard reset…or if it does, then a hard reset isn’t what mine needs lol
It says to hold the WiFi button in for 8 seconds. I did that (many times).
Then, the power light comes on, and the WiFi light starts blinking red.
Then, when it gets the password that I gave it in the app, the WiFi light turns amber (orange).
Then, after a long time, the WiFi light starts fast-blinking green.
At that point, it is available on my network with the IP address that I gave it via static DHCP assignment (sorry; I was being a bit careless with terminology before)
Nothing different ever happens.
I suspect that their system has already registered this unit when I connected it the first time, and they don’t have a way of letting this unit’s code release to be used again…or something like that.
At any rate, I ordered another one, and will deal with this broken one once they finally respond (I assume they will eventually respond).
This is what I get if I leave it to get a dynamic (read from bottom to top):
203 Feb 15 16:44:16 DHCP INFO DHCPS:Send ACK to 192.168.x.x
202 Feb 15 16:44:16 DHCP INFO DHCPS:Recv REQUEST from 04:E6:76:83:21:CD
201 Feb 15 16:44:16 DHCP INFO DHCPS:Send OFFER with ip 192.168.x.x
200 Feb 15 16:44:16 DHCP WARNING DHCPS:lease host name not found
199 Feb 15 16:44:16 DHCP INFO DHCPS:Recv DISCOVER from 04:E6:76:83:21:CD
And this is what I get if I set a static(read from top to bottom):
Feb 14 08:22:16 DHCP INFO DHCPS:Recv DISCOVER from 04:E6:76:83:21:CD
Feb 14 08:22:17 DHCP INFO DHCPS:Send OFFER with ip 192.168.x.x(different from above and configured static address)
Feb 14 08:22:17 DHCP INFO DHCPS:Recv REQUEST from 04:E6:76:83:21:CD
Feb 14 08:22:17 DHCP INFO DHCPS:Wrong Server id or request an invalid ip
Feb 14 08:22:17 DHCP INFO DHCPS:Send NAK
I had to reset once to get mine working, after initially realizing I was trying to connect via 5Ghz (despite their obvious warning) and the 8 second thing worked. Mind you I hadn’t activated it to my bloomsky account yet since it hadn’t actually connected to anything.
I was able to rename the device via the Bloomsky portal though, but that won’t help you I don’t think.
I would think you’d get an error with a second account, saying it can’t be joined to more than one, never get something like that?
Unless you do a “block all, allow some” type of firewall security, ports won’t matter. This device creates a socket out to Bloomsky first then uploads it’s data, so port blocking on the ISP/firewall side should have no affect on this. Assumptions being (haven’t packet captured) that it connects via 443 outbound, with randomly assigned inbound as per every other kind of connection basically.
I was planning on doing a packet cap this week when I have some free time, simply out of curiosity.
Actually, since I knew it was already connected to my network (but just not connecting to the BloomSky system and my online account), this time, instead of doing the whole reset thing, I decided to just re-run through the normal setup in the app, and it connected right away.
Now I’m just waiting the initial five minutes or so to see if it actually starts uploading data…
Does anyone have experience yet with transferring their BloomSky (one that is already set up and uploading data to your online account) from one WiFi SSID to another?
The reason I ask is that, while troubleshooting, I thought, ‘perhaps there’s something goofy with my SSID’. So, I changed it to something else temporarily.
However, now that it is up and running, I realized it and want to change it back to what I had it named before (lots of devices all over the house are pissed; looking for their missing WiFi connection).
I just wonder if it’s going to be OK to transfer it from the temp one back to the real one.
I guess I’m just about to find out…
@michaelahess
I don’t see that in the portal. Where did you find it?
Find the device you added in the My Device section click on it to open up it’s page. Next to preferences click Edit, and add the api key from bloomsky here then click save.
The service manager sets all the correct info for the device. No need to do anything other than hit done within the connect app. If you changed anything in the IDE for the device is recommend uninstalling and reinstalling.
I got that error for a long time after, hours. Then it started working. I want to say it gave the error because it was in night mode and thus not uploading images, then in the morning it started again and the error went away.
I am having the same problem. And there is no data in any of the cells for the device… How does the Connect app know to link to the device? I don’t think they are talking to each other.
In the Bloomsky app on your phone/tablet. open the settings ( little gear in upper right corner) Click on your current device name and it opens another page where you can edit it
[quote=“Turb02, post:433, topic:38202, full:true”]
Can anyone provide the MAC of their bloomsky?[/quote]
I figured it out for everyone now (I think)…
As we’ve already figured out, they are most likely all 04:E6:76:##:##:##
Well, it just so happens to be that the unique portion is on a bar code sticker on the movable part that has the camera.
The six characters directly under the bar code (surrounded by an asterisk on each end) are the unique part to your BloomSky’s MAC address.
There. Now I’ve actually contributed something (trivial as it is) instead of just a bunch of useless troubleshooting posts. lol
