My problem is solved somehow. Because at the beginning of the problem my idx 178 virtual sensor had a value that did not move so inevitably an undefined result in the debug screen. In addition, domoticz only transmit parameters that move.
Thank you again mrf68, I learned a lot today.
Have a good ...
Search found 11 matches
- Saturday 29 December 2018 19:57
- Forum: Suggestions
- Topic: [90] MQTT Support
- Replies: 370
- Views: 146537
- Saturday 29 December 2018 18:53
- Forum: Suggestions
- Topic: [90] MQTT Support
- Replies: 370
- Views: 146537
Re: [90] MQTT Support
mrf68,
I'm late because my Mosquitto on my Raspberry did not want to connect anymore. I had to reinstall it completely.
I approved your message such as:
- MQTT node domoticz / in:
server: 192.168.1.17:1883
topic: domoticz / in
QOS 2
- JSON node:
action: Convert between JSON string & object ...
I'm late because my Mosquitto on my Raspberry did not want to connect anymore. I had to reinstall it completely.
I approved your message such as:
- MQTT node domoticz / in:
server: 192.168.1.17:1883
topic: domoticz / in
QOS 2
- JSON node:
action: Convert between JSON string & object ...
- Saturday 29 December 2018 16:12
- Forum: Suggestions
- Topic: [90] MQTT Support
- Replies: 370
- Views: 146537
Re: [90] MQTT Support
mrf68,
I added the JSON node and the Switch node. And I changed the switch settings such as:
name: msg.payload.idx
== 0/9 140 (from idx)
After Deploy, I have this in the debug screen:
domoticz / out: 29/12/2018 at 16: 01: 53node: ad57d776.782158
domoticz / out: msg.payload.svalue1: string [5 ...
I added the JSON node and the Switch node. And I changed the switch settings such as:
name: msg.payload.idx
== 0/9 140 (from idx)
After Deploy, I have this in the debug screen:
domoticz / out: 29/12/2018 at 16: 01: 53node: ad57d776.782158
domoticz / out: msg.payload.svalue1: string [5 ...
- Saturday 29 December 2018 15:02
- Forum: Suggestions
- Topic: [90] MQTT Support
- Replies: 370
- Views: 146537
Re: [90] MQTT Support
I redefined the properties of the debug node on normal (= msg.payload) and I observe the scrolled data. Here is an example :
{
"Battery": 255,
"RSSI": 12,
"description": "",
"dtype": "General",
"id": "0000044D",
"idx": 140,
"name": "CPU_Usage Raspberry",
"nvalue": 0,
"stype": "Percentage ...
{
"Battery": 255,
"RSSI": 12,
"description": "",
"dtype": "General",
"id": "0000044D",
"idx": 140,
"name": "CPU_Usage Raspberry",
"nvalue": 0,
"stype": "Percentage ...
- Saturday 29 December 2018 14:28
- Forum: Suggestions
- Topic: [90] MQTT Support
- Replies: 370
- Views: 146537
Re: [90] MQTT Support
mrf68,
ok, at the exit of the 1st node MQTT (domoticz / out), I connected a debug node (msg.payload.svalue1).
After a Deploy, the result is negative (on the right of the screen): domoticz / out: msg.payload.svalue1: undefined
While my 1st MQTT node is seen connected (green LED) below the node
ok, at the exit of the 1st node MQTT (domoticz / out), I connected a debug node (msg.payload.svalue1).
After a Deploy, the result is negative (on the right of the screen): domoticz / out: msg.payload.svalue1: undefined
While my 1st MQTT node is seen connected (green LED) below the node
- Saturday 29 December 2018 13:27
- Forum: Suggestions
- Topic: [90] MQTT Support
- Replies: 370
- Views: 146537
Re: [90] MQTT Support
mrf68,
yes, I see the visual difference.
So I copied your line :
msg.payload = "{\"command\": \"udevice\", \"idx\": 178, \"svalue\": \"" + (msg.payload.svalue1) + "\"}";
and replaced my line but nothing helps. After a Deploy, the result is always this (on the right of the screen) :
{"command ...
yes, I see the visual difference.
So I copied your line :
msg.payload = "{\"command\": \"udevice\", \"idx\": 178, \"svalue\": \"" + (msg.payload.svalue1) + "\"}";
and replaced my line but nothing helps. After a Deploy, the result is always this (on the right of the screen) :
{"command ...
- Saturday 29 December 2018 10:45
- Forum: Suggestions
- Topic: [90] MQTT Support
- Replies: 370
- Views: 146537
Re: [90] MQTT Support
Hello mrf68,
Thank you for your reply.
What exactly does your phrase mean " You need to manually set the idx of the virtual sensor, not the idx of the original input."?
For my part, I can not get the result. Here is my installation:
- for the MQTT node :
Server: 192.168.1.17:1883
Topic: domoticz ...
Thank you for your reply.
What exactly does your phrase mean " You need to manually set the idx of the virtual sensor, not the idx of the original input."?
For my part, I can not get the result. Here is my installation:
- for the MQTT node :
Server: 192.168.1.17:1883
Topic: domoticz ...
- Friday 28 December 2018 22:09
- Forum: Suggestions
- Topic: [90] MQTT Support
- Replies: 370
- Views: 146537
Re: [90] MQTT Support
hello mrf68 and to all,
here I have followed your little tutorial page 16 from Monday 02/2018 with a fictitious idx 178 sensor but nothing works: on the one hand, although at the exit of the 1st node named json I have this :
{
"Battery": 255,
"RSSI": 12,
"description": "",
"dtype": "Usage ...
here I have followed your little tutorial page 16 from Monday 02/2018 with a fictitious idx 178 sensor but nothing works: on the one hand, although at the exit of the 1st node named json I have this :
{
"Battery": 255,
"RSSI": 12,
"description": "",
"dtype": "Usage ...
- Friday 12 October 2018 12:25
- Forum: Others
- Topic: NODON STP-2-1-05 Manufacturer unknown
- Replies: 6
- Views: 2182
Re: NODON STP-2-1-05 Manufacturer unknown
hello to D'rMorris,
thank you for your answer but it looks complicated for a beginner ...
What I'm looking for is just what did StephaneG, add "{0x046," Nodon "}".
Where is "hardware / EnOceanESP2.cpp" on my Raspberry PI3? It is a file? And how to update and compile?
Patric
thank you for your answer but it looks complicated for a beginner ...
What I'm looking for is just what did StephaneG, add "{0x046," Nodon "}".
Where is "hardware / EnOceanESP2.cpp" on my Raspberry PI3? It is a file? And how to update and compile?
Patric
- Friday 12 October 2018 11:17
- Forum: Others
- Topic: NODON STP-2-1-05 Manufacturer unknown
- Replies: 6
- Views: 2182
Re: NODON STP-2-1-05 Manufacturer unknown
Hello,
I'm new and I'm interested in updating the manufacturers table: but how?
Where do we find this table? With which software to open it?
Compile: with which compiler?
In short, I do not know how to do it. Thank you for any help.
Patric
I'm new and I'm interested in updating the manufacturers table: but how?
Where do we find this table? With which software to open it?
Compile: with which compiler?
In short, I do not know how to do it. Thank you for any help.
Patric
- Tuesday 31 July 2018 13:27
- Forum: Other questions and discussions
- Topic: error in the wiki "Camera Setup"
- Replies: 1
- Views: 382
error in the wiki "Camera Setup"
Hello,
there is an error in the wiki "Camera Setup" on the site https://www.domoticz.com/wiki/Camera_Setup#Raspberry_PI_Camera in paragraph "1.2 raspberry pi", we have:
"To add the camera in domotic use the following parameters:
IP Address: Your domoticz IP address
Port: 8080 "
the IP address must ...
there is an error in the wiki "Camera Setup" on the site https://www.domoticz.com/wiki/Camera_Setup#Raspberry_PI_Camera in paragraph "1.2 raspberry pi", we have:
"To add the camera in domotic use the following parameters:
IP Address: Your domoticz IP address
Port: 8080 "
the IP address must ...