Hi,
I know that the dbus-send utility it's not the best thing in order to test
connman, because there are function signatures that have nested containers
which are not supported by dbus-send. But it's the quickest way to test the
functionality parts of connman. I know also that there are a number of
python tests and utilities, but in the embedded system that I use it's not
installed.
What you see in the logs is nominal. ConnMan unregisters the agent as
soon as
dbus-send quits (try quitting connmanctl after registering the agent:
same thing).
The agent is not in ConnMan, it's in the process that registers itself
as the agent.
ConnMan will then request this agent when necessary.
dbus-send it way too limited to act as an agent, since you first need to
register to
ConnMan but then you also need to implement/handle the calls ConnMan can do
to the agent.
Have a look at the test scripts in test directory (connman repo), these
are in python
and sort of easy to read so it should help you to do the same in node-js.
Tomasz
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman
