Testing EspruinoHub

[gcgarner]

Thread for issues of espruinohub

[sebi5361]

I have just installed the container with EspruinoHub and it works!
I am able to read BLE signals as MQTT objects ans vice versa, emit BLE signals from MQTT objects.

However I have noticed some elements:

• EspruinoHub in the container might be an older version than the one when doing a native installation, as its interface is different when looking at IP:1888. Could it be updated?
• According to the container log, $TERM is not defined. Shouldn't it be added to the ENV variables to avoid such a message?
• The container network is set to host rather than iotstack_default together with publishing port 1888. Wouldn't those settings be better for consistency with the other containers?

[sebi5361]

I have noticed that the version of EspruinoHub in the container is really not that stable and loses many connections to BLE devices compared to the latest version when doing a native install.

[gcgarner]

Thanks for the feedback, are you running the native and the docker version at the same time?

[gcgarner]

The host grants additional rights over just the network port, it seems to allow access to the bluetooth as well. I would rather not have the container operate at host level but that is the recommendations by the creator.

[gcgarner]

I had a look at the image and it was updated last 2 years ago

there is an alternative on docker hub hat is 2 months old, will have a look at that one radhus/espruinohub

[sebi5361]

Thanks for the feedback, are you running the native and the docker version at the same time?

No, I uninstalled the latest native version to try the docker container from the stack. Thus I have a good comparison standpoint.
Indeed the two month old radhus version might be a better pick.
I didn't know about host level granting bluetooth access, interesting...