This was my understanding as well. Companies need to stop using IFTTT as a crutch and lame first option integration method. IFTTT is STRICTLY a secondary integration method. It is not even close to good enough. Iota should really think about what Steve is saying. With the smartthings community working on smartapps to use with iota, the completely complicated iota system could be broken down for end users who were not expecting having to come here and go through all this information they do not understand to even approach a use for iota.
@mbattistello Interesting. That may reflect a bug with what happens to the firmware when the button is pressed relating to the LED. We'll look into that. The getUserCoordinates needs to run on the phone to work, because the simulator does not know your location, only the phone gps does.
If you'd like to test what you are getting, for now I'd suggest scheduling a notification with the contents of the getUserCoordinates results as the title or body, and viewing it that way.
Can you get notifications to fire for your mod on button press with the scheduleNotificationNow method?
@mbattistello Technically the only flow you need to do is click. This is enough to get it republished:
This will cause your script to appear in the settings screen of your Iota as unsaved (unless it was already saved as something else)
But to have your script saved under a certain name, you must click save before running. The new script should always appear in the Iota app in the specific Iota screen if you get the notification saying "Running code...".
@Fred42 Admittedly our manufacturing process wasn't as smooth as it could have been. We definitely didn't approach the case in the correct manner. As for the LED, what problems are you experiencing with it? Is it not turning on at all? Are you testing it with any specific apps?
1x is right on top of the Dot, 5x should be size of a big room. We left it as 1x to 5x as opposed to exact feet measurements because different devices with different chips would produce different ranges.
We weren't intentionally trying to mislead anyone. I apologize if you're unhappy with the case. We were transparent in our updates that we had to change it. @GonZoUK We also might be able to release some CAD files of our many alternative designs. I'll contact @anuj_iota to see if this is possible.
The Mirai botnet that took advantage of unprotected IoT devices did so for internet connected hardware such as video cameras and DVRs. It used these to send large amount of ping requests to the Dyn DNS server.
Dots are not Internet-enabled so a hacker cannot exploit it to do something similar. Because Dots are Bluetooth-based, no one can remotely access Dots and avoids this problem. Hope this helps!
The Dot is going to be 1 inch in diameter and .5 inches in width. It's possible these dimensions could change slightly as we interface with manufacturers. But generally, we're aiming to make it as aesthetic and small as possible.
We are experimenting with different sticking substances. We can update you guys in the testing process if you're interested, but right now we're trying everything from 3M Sticky Backs to different sticking polymers that we would speckle onto the Dot.