Clarify in documentation which device versions are supported

[dala318]

There are currently two Blue Connect versions available on the market, Go and Pro. The Pro has some more connectivity alternatives and "premium app". Would be great if this documentation clarified how/if the device version affects the functionality of the integration

[dala318]

So I got my Blue Connect Go today and integrated it successfully in Home Assistant with this method. Didn't go for the Pro since we are outside Sigfox coverage and therefore went with the WiFi extender instead. Now realizing that without the Premium subscription that comes with the Pro or for ~60 EUR per year you have to initiate measurements manually to get updates in app and HA. Should probably also be noted if no good workaround can be found.

[LordMike]

Actually, you can run a special command for that on a schedule.

What actually happens is the blue will send measurements over BLE and Wifi 20 times a day, Blue Riiot will store this for you - and when you click "measurement" it will release the latest measurement for you.

I made an MQTT endpoint that calls this release API.

I didn't document it out front because it is maybe on the edge of what can be justified.. but you can find it here: https://github.com/LordMike/MBW.BlueRiiot2MQTT/blob/a035cd458d5988dc2a36fd6d071eddf6674fc22a/MBW.BlueRiiot2MQTT/Commands/ReleaseLastUnprocessedCommand.cs#L25-L28

So by sending a message to /commands/release_last_unprocessed/<device id> you'll get a measurement.

[DAVIZINH0]

hello, i edit my message because, now i understand your previous message :-(

Now i have a extender and im making test with the mqttexplorer. now i have the homeassistant topic as "pool"

to get a measurement i must launch this topic? pool/commands/release_last_unprocessed/pool_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx as json?

or im wrong?

I publis this and nothing happend: mosquitto_pub -h 192.168.1.2 -m '{}' -t 'pool/commands/release_last_unprocessed/xxxxx' where xxx is "key" in blueconnect app

mosquitto_pub -h 192.168.1.2 -m '{}' -t 'pool/commands/release_last_unprocessed/xxxx' where xxx is "serial number" in blueconnect app

The device_id is this log id or the short that apears in the app?

thanks a lot!

EDIT AGAIN: The solution for me is this command: mosquitto_pub -h 192.168.1.2 -p 1883 -m "" -t 'blueriiot/commands/release_last_unprocessed/xxxx' where xxx is "key" in blueconnect app the important for me is that "blueriiot" is the firs part of topic, not "pool", i have "pool" as HASS_discoveryprefix" in docker, but the command need "blueriiot" :-) Great functionality thanks a lot!!!

[naThnaabu]

hello, i edit my message because, now i understand your previous message :-(

Now i have a extender and im making test with the mqttexplorer. now i have the homeassistant topic as "pool"

to get a measurement i must launch this topic? pool/commands/release_last_unprocessed/pool_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx as json?

or im wrong?

I publis this and nothing happend: mosquitto_pub -h 192.168.1.2 -m '{}' -t 'pool/commands/release_last_unprocessed/xxxxx' where xxx is "key" in blueconnect app

mosquitto_pub -h 192.168.1.2 -m '{}' -t 'pool/commands/release_last_unprocessed/xxxx' where xxx is "serial number" in blueconnect app

The device_id is this log id or the short that apears in the app?

thanks a lot!

EDIT AGAIN: The solution for me is this command: mosquitto_pub -h 192.168.1.2 -p 1883 -m "" -t 'blueriiot/commands/release_last_unprocessed/xxxx' where xxx is "key" in blueconnect app the important for me is that "blueriiot" is the firs part of topic, not "pool", i have "pool" as HASS_discoveryprefix" in docker, but the command need "blueriiot" :-) Great functionality thanks a lot!!!

Hi to clarify you mean that i have to set the topic to blueriiot and then the filed below /commands/release_last_unprocessed/IDOFDEVICEFROM APP

like this?