Node-RED

• 

  This topic is deleted!
  • iiot2k  

  1
  0
  Votes
  1
  Posts
  32
  Views

  No one has replied

• B

  NodeRed with analog OUTput
  • BeerGeek  

  2
  0
  Votes
  2
  Posts
  643
  Views

  Z

  Hello @beergeek You are right with problem when using analog output in configuration 0-20mA. When we designed nodes, we only implemented voltage output. To fast repair you can add function node to output, that recalculate output value from 0-10 to 0-20. So your input value will be 0 to 10, but output value will be 0-20. We will try to repair output node with support for current output it in next week. Function code to fast implementation: Try to import funtion and connect it as in picture. [{"id":"98b4db11.a43aa8","type":"function","z":"dd6bd412.3bde08","name":"0-20mA","func":"if(msg.payload.value) \n{\n msg.payload.value = msg.payload.value*2.00;\n}\nreturn msg;","outputs":1,"noerr":0,"x":1260,"y":220,"wires":[["a7851ed2.a7d6"]]}] Thank you for your notice.
• N

  Missing events on digital inputs
  • nelliekins  

  2
  0
  Votes
  2
  Posts
  607
  Views

  N

  My bad. The problem was me not detecting multiple messages in the same payload from the Websocket node. :-) All works fine now.
• M

  Read data sent from Omron Plc by serial port using Node-Red
  • Methlouthi Hathemi  

  4
  0
  Votes
  4
  Posts
  1755
  Views

  

  Hi @methlouthi-hathemi, first of all, are you sure you have the correct cable? The cable has to be crossed, not null modem. Second of all - are you sure you have some register number 0? It is common that the number and the address of registers are mismatched (numbers of the registers should go from 1, addresses should go from 0). Best regards, Martin
• J

  group_assignments Node-Red
  • juntiedt  

  2
  0
  Votes
  2
  Posts
  630
  Views

  J

  {"status": "success", "data": {"group_assignments": [[{"value": 0, "pending": false, "circuit": "1", "dev": "relay", "glob_dev_id": 0}, {"value": 0, "pending": false, "circuit": "3", "dev": "relay", "glob_dev_id": 0}, {"value": 0, "pending": false, "circuit": "2", "dev": "relay", "glob_dev_id": 0}, {"value": 0, "pending": false, "circuit": "5", "dev": "relay", "glob_dev_id": 0}, {"value": 0, "pending": true, "circuit": "4", "dev": "relay", "glob_dev_id": 0}, {"value": 0, "pending": false, "circuit": "7", "dev": "relay", "glob_dev_id": 0}, {"value": 0, "pending": false, "circuit": "6", "dev": "relay", "glob_dev_id": 0}, {"value": 1, "pending": false, "circuit": "8", "dev": "relay", "glob_dev_id": 0}]]}}```
• J

  http post
  • juntiedt  

  3
  0
  Votes
  3
  Posts
  873
  Views

  J

  this works as well: msg.url = "http://10.0.0.52:8080/json/relay/3"; msg.headers ='({"content-type":"application/json"})'; msg.payload = '({"value": "1","timeout": "20"})'; return msg;
• S

  Error in the description: Node-RED on UniPi Neuron PDF guide (EN)
  • stonefieldlab  

  3
  0
  Votes
  3
  Posts
  1012
  Views

  J

  Similarly in the CZ version. Working link here bash <(curl -sL https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/update-nodejs-and-nodered) Cheers, Jan
• C

  Multiple 1wire Sensors (Ds18b20)
  • Christian  

  2
  0
  Votes
  2
  Posts
  809
  Views

  

  Hello @Christian, the precision of the sensors cannot be set via Evok. The only way is to do it by some external tool, e.g.: https://raspberrypi.stackexchange.com/questions/14278/how-to-change-ds18b20-reading-resolution. If you cannot read value of any sensor, then it looks more like a HW issue. One faulty sensor can kill whole bus. I would suggest to try one sensor at a time and see if you could read value from all of them. The I2C interval isn't affected by the number of sensors or the time they need for the response. The underlying OWFS reads the values sequentially, one sensor at a time. Best regards, Martin
• B

  Clumsy, complicated...
  • budulinek  

  3
  0
  Votes
  3
  Posts
  1277
  Views

  B

  @martin-kudláček said in Clumsy, complicated...: therefor the websocket URL could be hardcoded into the unipi-input Hardcoded ws URL??? You do not have to hardcode the ws URL if you want to build a standalone input or output node. Just have a look at Nick's node-red-contrib-unipi-evok. Or node-red-contrib-loxone. They both use websocket and the ws URL is not hardcoded. The ws URL is specified by the user in the so called configuration node. You can configure Evok to read 3rd party devices via ModbusRTU. It would be complicated to express this type of data via dedicated input nodes. OK, I got your point. But again, you can configure the device (whether it is a Unipi/Neuron/Axon or some 3rd party modbus) in the configuration node. No need to do that in the input / output node. Or, another common solution. Again, see node-red-contrib-unipi-evok for inspiration. There are actualy 4 nodes in the node-red-contrib-unipi-evok package. Input node, output node, configuration node and "unipi-api" node which (I assume) serves as a simple filter (I do not know the detaills, I have never used it). So you can always build input and output nodes for those who do not use 3rd party devices and a "filter node" for those few users who want see the full communication. Also, if you really need a filter node, one "bidirectional" node should do the job. You do not need two nodes. Just have a look at the built-in "json" mode. Converts between a JSON string and its JavaScript object representation, in either direction. I do not know how it works but it is somehow able to recognize what is being fed into the node. Can you post your flow which causes the SyntaxError? Sorry, I can not, because The transition to our nodes is complicated and once the Nick's package is removed, it's hard to get it back. I am ready to help you, but I do not want to uninstall Nick's package.