I am trying to develop an app for Fitbit Versa 3. I am able to connect from my VS code to Fitbit OS simulator, but when I try to install the app using the following two commands:
npx fitbit
bi
I get an error
Loaded appID:c25295d1-e4d6-43e5-a93a-b8d3bef90830 buildID:0x097ede643c977ca5
App requires a device, connecting...
Auto-connecting only known device: Versa 3 Simulator
App requires a phone, connecting...
Auto-connecting only known phone: Simulator
Sideloading app: starting...
Install failed: Internal Error
There are no details on what the Internal error is for. Has someone encountered this error before?
Things I have tried:
Restarting Fitbit OS Simulator and VS code
Generate a new App Id for the Fitbit app
Ensuring that both the Fitbit OS simulator and VS code are connected to same Fitbit account
See: https://community.fitbit.com/t5/SDK-Development/Simulator-SSL-Problem/m-p/5003032/highlight/true#M16148
It is a simulation problem, I believe. You have to delete the cacert.pem in the simulator, and replace with a new and updated version of cacert.pem in the simulator folder for Versa 3 . Click on this forum discussion to find the cacert.pem download and instructions. The simulator has been broken for a while as announced in November on the Fitbit Development Twitter.
Related
I'm trying to install a clock face I made for the Versa 3 onto my Versa 4. On the watch you need to connect the charge cable (to the pc I assume). Then in watch settings there is a place to enable Developer Bridge/USB Debugging which I assume is how one installs an app for testing. This was via WIFI on the Versa 3. No WIFI on Versa 4. On the screen that reads "To connect to developer bridge, enable USB debugging" I select the switch to enable but selecting the "Yes" button just turns off the screen. It does not restart, and Fitbit Studio does not recognize the watch.
The same Yes/No dialog works for Factory Reset and Shutdown so I'm guessing the switch is just not hooked up correctly in the OS.
I've factory reset a couple of times, once connected via the PC app and not phone app. In that scenario the "Settings" button was greyed out so I couldn't even get to the step I am describing.
Is there some step I am missing? Is anyone else able to get USB debugging to work on this device?
The Fitbit Versa 3 SDK is not compatible with the newer Versa 4. Each watch has its own development kit with a special name that must be specified in the .json- Versa 3 is Atlas. If you take a program that works for one build you have to make the correct changes to the .json file, index, and widgets sections to make it work for another build. Follow official guide here: https://dev.fitbit.com/build/guides/migration/
That being said, you currently cannot download or create your own apps or clockfaces for Versa 4 or Sense 2 at all. It does not seem that Fitbit is going to continue allowing 3rd party developers to contribute, and it has no future plans to release an sdk for Sense 2 or Versa 4.
See forum discussion:
https://community.fitbit.com/t5/SDK-Development/Sense-2-and-Versa-4-development/td-p/5245083
Moderators have suggested to leave a feedback vote here along with other users to ask Fitbit to add a Versa 2 and Sense sdk to Fitbit Studio.
https://community.fitbit.com/t5/Feature-Suggestions/3rd-Party-Apps-on-Sense-2-and-Versa-4/idi-p/5248677#comment-on-this
Just want to build Google IOT core with mongoose OS running for sensing temperature data on google PUBSUB.
I have a problem starting from beginning while not able to the connect via an approved google Core IOT Device - "TI CC3200". Its not able to connect to Mongoose OS. Its getting "access denied" on all COM ports, tried almost all changing COM 1,2,34,5…not working at all…10 times restarted system. Already Installed all required COM Drivers required for Windows 10. Just want to connect Mongoose OS and Sensortag CC3200 and later integrate with GCP Core IOT to push data further.
I am referring this blog post provided by Mongoose OS Team for integration.
https://mongoose-os.com/docs/mongoose-os/cloud/google.md
MOS Screen here for reference
I have tried on other windows 10 and Windows 8 PC, but no success. Same error Access Denied on Mongoose OS screen
Access denied on MOS Screen immediately
To make WSO2 IOT work with Android in COPE mode, I've installed the org.wso2.iot.system.service with agent.
When I try to enroll Android, it works but system application appears and I see nothing. And I can't enter a PIN code. I have to enter it manually in the app.
The device is enrolled and seems to sync but operations do not work. Ringing sometime loop, reboot does not work (still IN PROGRESS State), wipe does not work, and system service (see capture) appears on every sync.
I generated apk in debugCOPE mode, but adb logcat does not show anything
adb logcat org.wso2.iot.agent:V *:S
--------- beginning of main
--------- beginning of system
--------- beginning of crash
How did you sign system service app? Do you have your own ROM?
As stated at
WSO2 signing system service app
"system app is targetted towards original equipment manufacturers"
According to the product documentation
https://docs.wso2.com/display/EMM330/Integrating+the+Android+System+Service+Application
you should have firmware signing key.
Environment:
OS: Windows 7 Ultimate 64-bit, SP1 (latest patches)
Hardware: Dell XPS L702X (8GB Ram)
Android Developers Tool (ADT): version adt-bundle-windows-x86_64-20131030
Google USB driver: version 9
Google Glass: "v2" device running XE12
Situation: Debug mode enabled on Google Glass; connected to USB port on computer; no device seen (ADT cannot find glass).
The android_winusb information already contains the following settings for Glass: in NTx86 section:
;Google Glass
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_9001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&MI_01
in NTamd64 section
;Google Glass
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_9001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&MI_01
Update: When I open the device manager, I DO see the "Glass 1" device in the "Portable Devices" section and in "Other devices" session. However, when I open the ADT the Google Glass device is not recognized (even though when I connect my HTC One Kit Kat 4 device shows up, is recognized and I can load an application onto that Android phone).
Suggestions on how to resolve?
Finally able to connect with Google Glass! Here are the steps that I used for the environment in question:
Installed ADT bundle for 64-bit Windows; updated all (took more than one cycle)
Used Android SDK Manager to load API 19 (Kit Kat) and API 15, along with Google Glass Sneak Peak, and ensured current USB driver was updated (to version 9 at this writing)
In ADT, added MyFirstApp (for Android phone) and deployed to HTC One/Sprint (running Kit Kat) device [optional, just to ensure that ADT can recognize something]
Stopped ADT
Opened Device Manager
Connected Google Glass, noted "Glass 1" in BOTH the Portable device and the Other device sections
Selected "Glass 1" in the Other device section (not the Portable device section) and ran update driver command pointing to the xxx\GoogleGlass\adt-bundle\sdk\extras folder to search.
Completion of driver update moved the device to "Android devices" section, noting it is an Android Composite ADB Interface
Once this had completed, I could take a sample application (I used Compass) and ran it as an Android Application!
(Since my device has an automaatic lock -- I assume -- I had to power cycle the device once to be able to get it to respond.)
I had the same issue. Glass was showing as SAMSUNG Android phone as well. My steps to fix the issue:
win7:
Click on: Update Driver
Click on: Browse my computer for driver software
Click on: Let me pick from a list of device drivers on my computer
Click on: Have Disk... (that options is in the bottom right corner)
click on: Browse...
navigate to the location of your edited android_winusb.inf driver then click open then click ok then click next
wait a moment then you should see "Windows has successfully updated your driver software". then click close and close again.
!!!(now here is the important part)!!!
Right click on the device and click uninstall.
check the box "Delete the driver software for the device" then click ok
wait about 5 sec then unplug your Google Glass from the computer. wait 5 more sec then plug it in.
Watch the magic happen!!!! its working!!
I'm trying to do the following:
Installing a Oracle WebLogic 11g Server with the examples in a VMWare Lab Manager (virutal machine Windows XP SP3).
The problem is the following:
According to the installation instruction everything is quite easy and should work out of the box. The installation does not show any errors.
Normally (i tried on a real machine first) it is only needed to got to
Start - Oracle WebLogic - WebLogic Server 11GR1 - Examples - Start Medical Records Server (Spring Edition)
and everything should work fine (a webpage should open).
The problem is, that no Medical webpage shows up.
Digging a little bit deeper:
Start Medical Records Server is only a batch script. On the real machine (same OS) a derby server is started, on VM not.
The batch script on both machines are equal, but both call a setDomainEnv.cmd which containt on the real machine
set DERBY_FLAG=true
and on VM
set DERBY_FLAG=false
Changing the parameter from false to true does start up derby, but the webpage does not open.
The only info message looking liek an error shown on startup is
Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Cl
ass 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raise a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
but the machine finally goes to
Server started in RUNNING mode
Is there something else need to fire up the sample pages?
the admin console starts up at localhost:7011\console , but not the samples