Domoticz

I have been busy for two long days and I just can't seem to figure out why I can't get this to work
I did (I think) exactly what was described in topic "Re: Get sensor values with MQTT into Domoticz"

Is there anyone who has an idea maybe?

Goal:
To get MQTT values from my second Raspberry Pi to my first RBPi Dummy Device via/with domoticz ánd mosquito ánd node-red.

Situation:
I have installed and running:
domoticz ánd mosquito ánd node-red on my Raspberry Pi 3B.
With "mosquitto_sub -v -t '#' " I do see all messages coming by via putty (see bottom)

Problem:
All goes fine exépt for the data to be updated in the domoticz-Device (idx).


Situation/what I have:
MQTT Hardware set in domotics with these settings:
Data Timeout: Disabled
Remote Address: localhost
Port 1883
Publish Topic: Index

A Dummy device created with name: GAS, type: gas, Idx: 289

Node-Red:
MQTT object, with the following settings:
Topic: p1monitor/smartmeter/consumption_gas_m3
Output: a parsed JSON object
Server: localhost : 1883
Client ID: p1monitor

JSON node:
Action: Convert between JSON string & object

Function:
switch (msg.topic) {
case "p1monitor/smartmeter/consumption_gas_m3":

msg.payload = {"command":"udevice","idx":289,"nvalue":0,"svalue": msg.payload};
}
return msg;

* Note: I also changed this to:
msg.payload = {"command":"udevice","idx":289,"nvalue":0,"svalue": 40 };
and
msg.payload = {"command":"udevice","idx":289,"nvalue":0,"svalue": "40"};

but that makes no differtence: the device won't update with the given value...

Debug output: mosquitto_sub -v -t '#'
pi@raspberrypi:~ $ mosquitto_sub -v -t '#'
p1monitor/smartmeter/timestamp_local 2021-10-18 23:34:13
p1monitor/smartmeter/timestamp_utc 1634592853
p1monitor/smartmeter/consumption_gas_m3 1389.693
p1monitor/smartmeter/consumption_kwh_high 1656.412
p1monitor/smartmeter/consumption_kwh_low 1597.443
p1monitor/smartmeter/consumption_kw 0.555
p1monitor/smartmeter/production_kwh_high 1583.278
p1monitor/smartmeter/production_kwh_low 657.426
p1monitor/smartmeter/production_kw 0.0
p1monitor/smartmeter/tarifcode D
p1monitor/smartmeter/record_is_processed 0
p1monitor/phase/timestamp_local 2021-10-18 23:34:13
p1monitor/phase/timestamp_utc 1634592853
p1monitor/phase/consumption_l1_w 0.547
p1monitor/phase/consumption_l2_w 0.0
p1monitor/phase/consumption_l3_w 0.0
p1monitor/phase/production_l1_w 0.0
p1monitor/phase/production_l2_w 0.0
p1monitor/phase/production_l3_w 0.0
p1monitor/phase/l1_v 235.2
p1monitor/phase/l2_v 0.0
p1monitor/phase/l3_v 0.0
p1monitor/phase/l1_a 2.0
p1monitor/phase/l2_a 0.0
p1monitor/phase/l3_a 0.0


It is almost as if node-red misses some kind of package responsible for communicating with domoticz itself...

Any suggestion someone maybe?

Hello @Quasimodo,

If I look to your screenshot with the Domoticz flow I see at the very left a MQTT input node called Domoticz In.
Does this mean that the topic is also domoticz/in? If so, it's not correct.

I do not see any MQTT output node.

Remember:

Domoticz publishes by default to domoticz/out and subscribes by default to domoticz/in.

That means that the MQTT input node should use as topic domoticz/out and the MQTT output node should have as topic domoticz/in.

I also see that the message is correct, but the topic is still wrong (p1monitor/smartmeter/consumption_gas_m3).

As you do not send anything to Domoticz, you have the red bar at the top, because the sensor timed out.

Can you publish your flow?

Regards

Firewizard,

I think you might be right!
I cannot test it anymore, since I decided to swap my Raspberry(1) for my Raspberry(2) (meaning now my
new bought raspberry(2) is directly attached to my smart meter P1).

In the above situation I got messages from RBPi-1, which was directly connected to the smart meter.
So in my RBPi-2 the above is what I saw, and now that you mention, I see that the object was pushed to:
"p1monitor/smartmeter/consumption_gas_m3"
And I assume that has to be "domoticz/in" indeed....

By the way, I got things working now directly in domoticz on my RBPi(2) So all happy
With using dzVents scripting Quite new to that but I start understanding it more and more.
And once you get it.... a whole world of opportunities open up Really enthusiastic

Thanks for the help in this case. Still very usefull in case I go back to the old situation....

Firewizard,

I figured it out
For personal reasons I had to go back to the old situation...

The problem was within what you described, so I needed a MQTT out so to say.
And the second problem was:

This was my function: And this is how it should have been (and now is...): That simple...
Now it works like charm

For those beginners like me who would like to use this as an example, just import: Enjoy

Hello @Quasimodo,

Please allow me to add a few things to your solution.

The question has often been raised, what is better, to use multiple if-then-else statements or the switch-case statement.

I do not present an opinion here, but you might want to read: https://www.geeksforgeeks.org/switch-vs-else/ and also https://www.javatpoint.com/if-else-vs-switch

In general, it is the opinion that in case of 5 or more nested if-then-else statements, a switch-case is faster.

I prefer also a switch-case statement, because of its readability

So you can also use in your "Function" node, the following code:
I thought this remark would offer something to choose from.

Regards