Jump to content

Questions Using MQTT on EISY


Recommended Posts

Posted

I am a long time user of ISY 99i and 994i but just upgraded to EISY with PG3 built-in.  I have installed the MQTT node server on PG3.  In my application, I just want to read values from a broker and will never be writing data back.  I have a few questions.  

1. Since this is on EISY PG3, I cannot access the EISY file system.  Does this mean I cannot use the devfile option to store my configuration file on EISY?  

2. I have an RPi running OWFS for a series of 1-wire devices (humidity & temperature sensors and a counter).  I modified a MQTT python script to read the values from the OWFS system and post them to an MQTT Broker as strings.  Below is a screen shot from MQTT Explorer showing my 1-wire sensors.  My script only posts the string values representing the numeric data for each sensor.  What Type should I use to display my string data?   I have tried analog, temp, and raw but cannot get the values to appear in ISY. 

owfs-mqtt.jpg.9a40ff60304fa8236c5a18ffe3b3a3f8.jpg

3. What are the requirements for the ANALOG and RAW Types with regards to sensor_id, status_topic, and cmd_topic?

4. I have looked at https://github.com/Trilife/udi-mqtt-pg3x/blob/0.40/POLYGLOT_CONFIG.md and have read the Configuration Help in PG3.  Is there some place I can additional information on how to configure each device?  

---

Below is an example of my devlist line.
[{"id": "outside_18b20", "sensor_id": "outside_18b20", "type": "Temp", "status_topic": "tele/owfs/temp/outside_18b20", "cmd_topic":  "cmnd/sensor/POWER"}]

Sincerely,
Emile Victory

Posted

Please disregard my earlier help request on the MQTT node server.

Yesterday I migrated my ISY-994i over to an EISY.  I had previously used a PG1 level node server called NodeLink to communicate with my OWFS (OWLink) and my GenMon.  I was under the impression that these would NOT work in EISY and PG3, which is why I was trying the MQTT node server.

However to my surprise, I found that if I added the port (:8080) to the end of the ISY IP address, the old NodeLink node server started communicating with PG3 and EISY as an unmanaged plugin.

nodelink.jpg.8f5a90b6ef3cb81f0be269957e0b88d6.jpg

Below is a screen shot of an Attic humidity and temperature sensor in EISY.

EISY-1Wire.jpg.7810ff01935e5df8012435914308af97.jpg

I will keep your MQTT plugin (node server) in mind if I try out sonoff devices.

Sincerely,
Emile Victory

Posted
52 minutes ago, EVictory said:

Please disregard my earlier help request on the MQTT node server.

Yesterday I migrated my ISY-994i over to an EISY.  I had previously used a PG1 level node server called NodeLink to communicate with my OWFS (OWLink) and my GenMon.  I was under the impression that these would NOT work in EISY and PG3, which is why I was trying the MQTT node server.

However to my surprise, I found that if I added the port (:8080) to the end of the ISY IP address, the old NodeLink node server started communicating with PG3 and EISY as an unmanaged plugin.

nodelink.jpg.8f5a90b6ef3cb81f0be269957e0b88d6.jpg

Below is a screen shot of an Attic humidity and temperature sensor in EISY.

EISY-1Wire.jpg.7810ff01935e5df8012435914308af97.jpg

I will keep your MQTT plugin (node server) in mind if I try out sonoff devices.

Sincerely,
Emile Victory

Hi @EVictory;

Glad you figured it out.

Cheers.

Guest
This topic is now closed to further replies.

  • Recently Browsing

    • No registered users viewing this page.
  • Who's Online (See full list)

  • Forum Statistics

    • Total Topics
      37.9k
    • Total Posts
      378.8k
×
×
  • Create New...