AntPlus, simulator, sensors

2) I am able to read light status information using a VivoActive HR watch. I realize the edge devices are typically used for control of bike lights. Apparently the VivoActive has the required functions. Is there are reason why this watch could not control bike lights?

3) lightNetwork: setHeadlightsMode, setTaillightsMode, restoreHeadlightsNetworkModeControl, restoreTaillightsNetworkModeControl
Documentation for all these functions indicates they return 'object' but there is no information at all about what this is. Any ideas? some sort of status. So far i only get null returns.

Does the simulator support this?

I do not know the answer to this, but it seems to me that this should be supported. I'll talk this over with Brian.ConnectIQ in the morning to verify, but if this should be supported, I'll get something filed for you.

Is there are reason why this watch could not control bike lights?

If you have access to the functions (i.e., you can call them without a symbol not found error), then the functionality should work.

Any ideas? some sort of status. So far i only get null returns.

This is a quirk in the documentation.. it indicates a return of type Object but the functions actually return nothing (which is technically a null object). It doesn't really make sense for these functions to return anything, and I can't think of a single place where the API returns an object from a setter.

Thanks Travis. Getting the simulator to work with AntPlus would be a help.

Things do compile ok. I am also able to read device information fine using the AntPlus connect iq functions.
So far it seems all commands i send to the lights have no effect.
Also when i read back from AntPlus.BikeLight.mode the value seems unchanged.

I asked about this partly having seen this post which indicated a certain firmware level causing certain light modes not to work.
https://forums.garmin.com/forum/into-sports/cycling/varia/1238277-varia-radar-how-to-downgrade-the-firmware-to-v3-40

In general it seems that maybe there is not much offered in the way of error code returns from ant/antplus, for example if a command should fail for some reason.

It seems the light functions are mostly intended for the bike computers. Wonder if perhaps the firmware in the watches may not be fully supported, or less well tested.

So i have now got an edge 820 also. Using my same code on it works much better than on the vivoactive HR.
Is there a way to better understand what state firmware support for lights is within the vivoactive hr, and perhaps if there are known limitations/bugs in this area.
Understanding about the simulator with AntPlus, ANT usb plug per my first question would be helpful also.
thanks.

Using item number from previous messages and adding a few more..

1) i have not heard back regarding the simulator along with AntPlus functions. It does work with Ant functions but never seems to connect with AntPlus. I must deploy code to device to test AntPlus. Perhaps the logic of the Edge which forms a network is not present in the simulator?

2) did not hear back re vivoactive hr - i presume it is just not supported, it appears perhaps it lacks the control logic to form a light network

4) There are several places in the documentation with an example like this.
var message = new Ant.Message; It should look like this, missing ()
var message = new Ant.Message(); 5) I am wondering how mature, tested etc the AntPlus functions are. Do existing apps using lights use Ant or AntPlus typically? In particular i wonder if retry logic is in place within AntPlus lightnetwork, many of the functions do not return any indication of success/failure. The Ant functions look like they would allow a lot more control, but require a lot more work to use.

Tested the simulator with an AntPlus bike light and paired ok using Settings > Manage ANT+ Sensors in SDK 2.4.5.

Vivoactive HR should be supported, paired ok in the simulator using an internal test and on a physical device.

We filed a ticket a little while back to update the documentation so it should just be a matter of time.