Trying to add a non-sonoff flow sensor

[tmorse305]

I'm trying to add a non-sonoff flow sensor to eisy.

I know the topic and I'm receiving MQTT packets from the sensor but the payload includes the word "flow".

Log file:

2025-08-08 11:51:45.574 paho-mqtt-client- udi_interface INFO Controller:_on_message: Received _on_message {"flow":16.16} from droplet-BA7C/state

2025-08-08 11:51:45.575 paho-mqtt-client- udi_interface INFO Controller:_on_message: _else: Payload = {"flow":16.16}, Topic = droplet-BA7C/state

 

I've tried combinations of "type" and "status_topic" but to no avail.  

 

How do I deal with the label "flow" in the payload?

 

Thanks.

 

[sjenkins]

@tmorse305 , 

have you tried changing your topic in your set-up from:

droplet-BA7C/state

to:

droplet-BA7C/state/flow

 

[tmorse305]

Hi @sjenkins, thanks for the suggestion.  I did try that.  The result is that the packets are not recognized by MQTT so there is no activity recorded in the log.  

I was looking at some of the node files, the MQSensor.py in particular shows the payload being tested for text.  Here is an example:

 # temperature
        if "temperature" in data:
            self.setDriver("CLITEMP", data["temperature"])
        # heatIndex
        if "heatIndex" in data:
            self.setDriver("GPV", data["heatIndex"])

I probably need to create a custom file to test for "flow" but not sure how to go about that.

This is the flow sensor.  Maybe if there were others using it we might be able to have someone create it.

Droplet the Smart Home Water Sensor - Hydrific, part of LIXIL

It currently has an integration for Home Assistant, but it would be great to create a direct connection to eisy.

[sjenkins]

@tmorse305 we would need to add a device which creates a node for your flow device.

Is flow the only data sent?  also, no control?  what are the units?

knowing the above its not a huge deal to make another node.  let me know.

[tmorse305]

Hi @sjenkins,  There is no control, only status from the device.   There are 3 things it sends, flow rate, online status, and signal strength.  Let me get the details together.  Thank you for the offer to create the node.

[sjenkins]

3 hours ago, tmorse305 said:

Hi @sjenkins,  There is no control, only status from the device.   There are 3 things it sends, flow rate, online status, and signal strength.  Let me get the details together.  Thank you for the offer to create the node.

will need to know for each of those what the number is and the unit.

for online status, what are the possibilities:  eg, (0,1,99) or (ONLINE, OFFLINE, UNKNOWN) or (online, disconnected, none)

need to know these exactly.

[tmorse305]

Hi @sjenkins,  

I think I have the information needed to configure this sensor.  It was a combination of hints from the manufacturer (no API doc yet) and looking at the communication with MQTTX.

Here is a summary with additional details attached:

Topic	Key word	Payload	UoM	Notes
droplet-<identifier>/state	flow	x.xx	l/Min	Sent periodically even if flow is 0.00
	signal	Initializing No Signal Weak Signal Strong Signal	n/a	Sent on query or if there is a change; no regular update
	server	Connected Connecting Disconnected	n/a	Sent on query or if there is a change; no regular update
droplet-<identifier>/health	n/a	online	n/a	Sent every second from client
<discovery prefix>/device/droplet-<identifier>/config	n/a	online	n/a	Sent by broker to trigger update to signal and server keywords and meta data
<discovery prefix>/device/droplet-<identifier>/config	n/a	See next page	n/a	Response from client from broker query of config topic

 

It turns out there is a sensor query.  It provides a lot of information (in attachment) but nothing that I need to capture in the plugin for my purposes.  The query does seem to trigger an update to the keywords signal and server.  Otherwise, they don't update unless something changes.  Sending the query at the start up of the plugin or providing a button in the AC would be great but is a want not a must.  The important thing is displaying the payloads from the 3 keywords flow, signal, and server.

Thank you for considering this.

API info for Droplet.docx

[sjenkins]

hi @tmorse305, 

looks like good work here.

Give me some time ; I've got a couple projects backed up & unfortunately I still work.

I would look to make a new node in the mqtt plugin framework

will start simple & add info & bells & whistles in layers

will need you in the test loop, sending me logs as we go.

likely will have some clarifying questions too; a snapshot pic of your mqtt explorer screen with some of the above fields populated will colour between some lines

I'll update here as I have something ; before then feel free to ping if I go dark too long for a pulse check.

 

[tmorse305]

Sounds good, thank you!