tmorse305

Turns out, not VirtualSmartHome. I just had the same problem when I tried to code this into a plugin. The issue was the headers not whether it was HTTP/1.1 or HTTP/2. With the proper headers it works with either one. POST or GET also work.

Thanks for your replies, I opened a ticket, and Michel quickly identified the problem: "It (the Virtual Server) does not accept http 1.1. It's expecting http2 which Network resources do not support." Thanks to Michel for the great support!

Is there a character limit when creating the "Path" for a network resource? I have a 135 character "path" which adds ok. I can see the whole path but when I test it I get a 403 error. If I take the whole url and paste it into a browser it works fine. I have lots of network resources configured that work fine but nothing close to the length of this one. This is the url: https://www.virtualsmarthome.xyz/url_routine_trigger/activate.php?trigger=023dfc97-3d2e-4c32-a3e2-b8ee5c0e7ca9&token=af23886c-91a9-4b84-****-1541bc9237b9&response=html I have it set to https, POST, Port 443, Timeout 10000, Mode: URL-Encoded I've tried C Escaped but same result I've tried the 2 check boxes but no luck there either. Thanks for any advice. Update: I've confirmed that the entire url is being sent by eisy, using Wireshark, so that's not the issue.

Hi @sjenkins, I decided to take a swing at creating the new node. I've made some progress; I have 3 of the status reporting into the AC. See screen shot. I'm still trying to figure out how to get the query to work. It turns out there is no UOM for liters/min. I'm using liters/hour as a placeholder. How do you add to the UOM list? Thanks for your support and inspiration to give this a try.

Sounds good, thank you!

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

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.

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.

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.

When I installed my 1TB NVMe SSD I did not create a VM partition. Is there any way to add it now? Not sure if I still have the mirror or I removed it. Thank you Update: Submitted a ticket, will report back on UD guidance in case anyone else is considering this.

Thank you!

Hi @Javi, Here you go: Editor.txt Node Def.txt n012_sonoff2 is the node: <nodeInfo> <node flag="0" nodeDefId="MQSW"> <address>n012_sonoff2</address> <name>NANO bit0</name> <family instance="12">10</family> <hint>4.2.0.0</hint> <parent type="1">n012_mqctrl</parent> <type>4.2.0.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>n012_mqctrl</pnode> </node> <properties> <property id="ST" value="0" formatted="Off" uom="78" name=""/> </properties> </nodeInfo>

12

Thanks @Javi, Here you go: <profiles> <profile family="10" id="1"> <files dir="nls"> <file name="en_us.txt"/> </files> <files dir="editor"> <file name="editors.xml"/> </files> <files dir="nodedef"> <file name="nodedefs.xml"/> </files> </profile> <profile family="10" id="2"> <files dir="nodedef"> <file name="nodedefs.xml"/> </files> <files dir="editor"> <file name="editors.xml"/> </files> <files dir="nls"> <file name="en_us.txt"/> </files> </profile> <profile family="10" id="3"> <files dir="editor"> <file name="editors.xml"/> </files> <files dir="nodedef"> <file name="nodedefs.xml"/> </files> <files dir="nls"> <file name="en_us.txt"/> </files> </profile> <profile family="10" id="4"> <files dir="editor"> <file name="udmobile.xml"/> <file name="hometele.xml"/> <file name="custom.xml"/> <file name="editors.xml"/> </files> <files dir="nls"> <file name="en_us.txt"/> </files> <files dir="nodedef"> <file name="hometele.xml"/> <file name="nodedefs.xml"/> </files> </profile> <profile family="10" id="5"> <files dir="editor"> <file name="editors.xml"/> </files> <files dir="nls"> <file name="en_us.txt"/> </files> <files dir="nodedef"> <file name="nodedef.xml"/> </files> </profile> <profile family="10" id="6"> <files dir="editor"> <file name="editors.xml"/> </files> <files dir="nls"> <file name="en_us.txt"/> </files> <files dir="nodedef"> <file name="nodedefs.xml"/> </files> </profile> <profile family="10" id="7"> <files dir="nodedef"> <file name="nodedef.xml"/> </files> <files dir="nls"> <file name="en_us.txt"/> </files> <files dir="editor"> <file name="editor.xml"/> </files> </profile> <profile family="10" id="8"> <files dir="editor"> <file name="editors.xml"/> </files> <files dir="nodedef"> <file name="nodedefs.xml"/> </files> <files dir="nls"> <file name="en_us.txt"/> </files> </profile> <profile family="10" id="9"> <files dir="editor"> <file name="editors.xml"/> </files> <files dir="nodedef"> <file name="nodedefs.xml"/> </files> <files dir="nls"> <file name="en_us.txt"/> </files> </profile> <profile family="10" id="10"> <files dir="nls"> <file name="en_us.txt"/> </files> <files dir="editor"> <file name="editor.xml"/> </files> <files dir="nodedef"> <file name="nodedef.xml"/> </files> </profile> <profile family="10" id="11"> <files dir="nls"> <file name="en_us.txt"/> </files> <files dir="nodedef"> <file name="nodedefs.xml"/> <file name="custom.xml"/> </files> <files dir="editor"> <file name="editors.xml"/> <file name="custom.xml"/> </files> </profile> <profile family="10" id="12"> <files dir="editor"> <file name="editors.xml"/> </files> <files dir="nls"> <file name="en_us.txt"/> </files> <files dir="nodedef"> <file name="nodedefs.xml"/> </files> </profile> </profiles>

Hi @Javi, I can't create advance status configuration for the 4 tiles that have Nano in the description. No trouble with any other that I know of. Those tiles are associated with the MQTT plugin. Maybe that's the issue? Thanks, Tim