Hi All, I have written a small python script to send and receive MQTT messages. Messages are send when inputs on the UniPi are changed, and UniPi outputs are changes if MQTT messages are received.

More information here; https://github.com/matthijsberg/unipi-mqtt/

Don't expect clean of fancy coding, just an amateur that build this for his own purpose, integrating UniPi into my Home Assistant setup.

@martin_triska said in 1-wire sensor and modbus sensor:

in this case, you have to tie the wires manually ON THE SENSOR. According to the photo, you have to connect dark-green and light-brown wires together ON THE PCB

Yes, that did the trick!

Thanks for the education and superb support here Martin. Really enjoy using your products.

Here is a picture

@martin_triska I tried connecting the modules via this drawing;

So 2 wires to + and 2 wires to GND and I needed to change wires to other ports from my previous situation. Does not show up at all now anymore now. :-(

Also, I do not understand where to bridge the wires to make it a daisy chain. Do i just need to place a wire on the sensor between 1W> and 1W< to loop it?

Am I following the right picture?

Hi All,

I just got a PRO380 to measure energy from my solar panels from my Neuron device. Since I don't want to run (learn ;-)) NodeRed and there is no turn key solution for native integration of the MOD380 in Evok I searched the internet and found this; https://github.com/volkszaehler/mbmd

This spins up a webserver with API and MQTT / InfluxDB integration for different energy meter including the PRO380. Works like a charm for me.

Some steps I did;

• Connect the meter to a RS485 port on the Unipi and enable the dip-switch
• Make sure that for that particular RS485 port there is no config in /etc/evok.conf (So yes, you need a unused / free port). When I had the port configured in the conf file I did not work, presumably because Evok is intercepting the traffic)
• Download the pre-compiled binaries from GitHub and extract as documented
• Perform a scan over modbus to see if your device is found with the command /usr/local/bin/mbmd scan --rtu -v --raw --comset 8E1 -a /dev/ttyNS1 . Note that ttyNS1 is my SECOND port on my device (2.01). Adjust this as needed for your device.
  My Output was the following (I changed the ID of the PRO380 to 5 on the device:
  2020/11/25 09:47:52 config: creating RTU connection for /dev/ttyNS1 (9600baud, 8E1)
2020/11/25 09:47:52 starting bus scan on /dev/ttyNS1
2020/11/25 09:47:56 device 1: n/a
2020/11/25 09:48:00 device 2: n/a
2020/11/25 09:48:04 device 3: n/a
2020/11/25 09:48:08 device 4: n/a
2020/11/25 09:48:10 device 5: INEPRO type device found, VoltageL1: 239.90
• Start the webserver with the command /usr/local/bin/mbmd run --rtu --comset 8E1 -a /dev/ttyNS1 -d INEPRO:5 --mqtt-broker tcp://1.1.1.1:1883 --api 0.0.0.0:1380. Also make sure you adjust the ttyNS port numer. As example I included a MQTT broker IP. Please read the docs for further config or InfluxDB integration.

Do Note that I redirect the webserver port to 1380 because 8080 is already in use. Go to the IP of your Neuron device on port 1380 and see what happens. I see the information coming up nicely. :-). There are API possibilities too to extract data, or push via MQTT or InfluxDB.

If this is what you want to keep, set up a service to start with your device, how to is also in the docs.

Perhaps this helps someone. It fairly easy to use. :-)

@martin_triska said in 1-wire sensor and modbus sensor:

have tied data lines (

No, I don't believe I did. Is the order of the wires relevant? So if I would switch the data lines on a sensor, would that explain this behavior?

I used my 2nd system to try this. I have 3 sensors connected to a 8 port hub. The sensors work, those are test sensors from my other setup.

@martin_triska said in 1-wire sensor and modbus sensor:

Go to http://<your unit IP address>/rest/all and look for the 1wdevice objects - are all sensors connected listed here?

No, only the sensor I see in the GUI is listed here.

Can you describe your application (exact components used and wiring diagram)?

It's fairly simple, a std UTP cable between my Unipi and the 8 port HUB, and 3 device from there;

I do have to note that I have sensors from SEDtronic directly too, since they can come coated. The first sensor in line is of that type for outdoor temp / hum measurement.

Hi All,

I have 2 unipi devices with Evok and attached to that some 1-wire sensors via an 8 port hub. Some of those sensors show up as a 1-wire sensors, where others show up as mod-bus devices. I also think that if they show up as modbus devices only one sensors is recognized. (I have multiple connected, only 1 shows up - not in screenshot)

The sensor recognized as 1-wire is a DS18B20 sensor.
The sensor recognized as modbus is a 1W-TH sensor.

Can someone help me with this? Is this expected behavior (hope not) or do I need to change something in hard- or software?

Here is a screenshot;

Hi All, I have written a small python script to send and receive MQTT messages. Messages are send when inputs on the UniPi are changed, and UniPi outputs are changes if MQTT messages are received.

More information here; https://github.com/matthijsberg/unipi-mqtt/

Don't expect clean of fancy coding, just an amateur that build this for his own purpose, integrating UniPi into my Home Assistant setup.

@tomas_knot ok, thanks for responding. Love to see MQTT into the base neuron by default in the future.

@tomas_knot Hi, Would it be possible to share this websocket to MQTT script? I have a websocket configured now that runs all the time (perfectly stable btw) and inititates a rest call to update a Domoticz switch if needed, however I would like to explore making this push pull with MQTT for myself te learn and to see if that's a bit more resources friendly.