Using eebus-go stack with nodejs

[jiklas-nust]

Hi everyone,

I'm an intern and I'm trying to create a connection between EEBus and Nodejs. Specifically I want to "mimic" an EEBus Node that can function both as server and client. It should p.ex. be able to subscribe to other EEBus Nodes and publish received information via MQTT.

I've been trying different approaches but to be honest the amount of different repositories and the fact that I am new to Go, are not really helping me make any progress.

I've read some of the other discussions in this repo and found out there is some kind of remote api i could use. At least if I understood that correctly.

Is there an intended way to use this stack from other languages and environments?

Any help would be appreciated. Even just helping me understand how things might work together.

Thanks in advance

[DerAndereAndi]

Hi,

you can look into the /examples/remote/ folder, which introduces a JSON-RPC interface for the expose go API. Out of the box the stack does not have any none-go interface, that would need to be developed by someone. The code in /examples/remote is meant to be put into an extra repository in the future, because it is out of scope for the purpose of this repository.

Please note, that what you are trying to accomplish is not an easy task. You will need to write Go code, understand how EEBUS works and how this stack implements the protocol.

[jiklas-nust]

Hi, thanks for your answer.
In order to understand the implementation I'm currently trying to connect the Devices App from your other repo to the remote example.
To prevent the automatic denial of the pairing approach of the Devices App I went ahead and did the following inside examples/remote/main.go:
r.service.UserIsAbleToApproveOrCancelPairingRequests(true)
r.service.SetAutoAccept(true)

Now for my question. Why is the pairing process not finishing? The web interface just shows

Pairing is in progress

indefinitely.

I have added the console output to this answer if that helps identifying the problem.
log.txt

Thanks again

[DerAndereAndi]

Hi, the log says it is all fine. There is probably a UI problem in the devices app, the data sent to the web ui shows that the remote service trusted it successfully: {"ski":"e6cc8eaf57f3edcce500ae69f02c0268987c9c7d","trusted":true, ...

[jiklas-nust]

Hi,

so I got it to show the usecase data now.
The Devices App failed to load into the third tab because it was parsing the discovery data which is an empty string. Therefore json.parse ran into an error because it handles an empty string as unvalid json.

Thanks for pointing me into the right direction with the problem.

I don't know why Discovery was empty for me but I fixed it when I removed a line of code that I added back when I was still thinking it wouldn't connect:

I had this piece of code sitting in the main.go file of remote:

r.service.RegisterRemoteSKI(<SKI of the Devices App>)

I thought it might be necessary to accept the pairing attempt of the Devices App.

[jiklas-nust]

Hi again,

I made some progress and have some new questions.
I managed to get the remote example running inside a Docker container in my nodejs project.
In my last reply I mentioned that I thought that the Discovery data was empty because I left some code that wasn't needed.

Now inside the Docker container Discovery data is once again empty. Could you tell me what discovery data is used for and where its getting set?

Until now I'm just guessing that it might be some kind of list of eebus nodes that the remote example had discovered on its own. Like it might contain its own data with the itself field set to true and also the Devices App and so on if other nodes are present.

Thanks.

[sthelen-enqs]

Hi,

if you're running the remote example in docker you'll need to run it
with host networking (or set up port forwarding and mdns proxying).

If with Discovery data you mean the RemoteServices, those are the EEBus
devices in the current local network.