Thanks for your quick reply.
Yes, my powers supply and the connection meet PELV standards.
Best posts made by budulinek
Latest posts made by budulinek
PELV power supply?
according to the specs, Neuron should be powered by 24V DC SELV supply. Is it also possible to use Neuron within PELV circuits?
At the moment, my Neuron is connected within a SELV circuit, but I need to change it to PELV (I need to connect -24V and PE).
RE: 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.
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.
I really appreciate your effort to develop "official" nodes for node red. My initial reaction was really WOW! I have been using Node Red for almost a year. I am not a developer, I can not write my own code and Node Red helped me a lot in integrating Neuron into my home automation. I rely on node-red-contrib-unipi-evok which is great but unfortunately no longer maintained by phillipsnick and I am happy to see you guys taking over the mainetance of node-red-contrib-unipi-evok...
Your new nodes are a step back from the "unofficial" node-red-contrib-unipi-evok
by phillipsnick (https://github.com/phillipsnick/node-red-contrib-unipi-evok). Here are my comments:
Why did you build only "filters" and not standard "input" and "output" nodes? Node red is supposed to be "very intuitive and user-friendly". Standard "input" and "output" nodes are intuitive. However, your "filters" are not very intuitive.
Since your nodes are just "filters" (and not standalone input/output nodes), they require connection to websocket node. Which makes the whole flow more complicated (more nodes, more connections). Standalone input/output nodes are better - at least from user point of view.
I really miss the "fetch available relays / outputs / inputs" feature. The old nodes by phillipsnick were able to automatically fetch all available devices. One could simply pick relay / output / input from a drop-down menu. Now you need to copy-paste the name of the relay from Neuron's WebGUI... This is very user-unfriendly and a huge step back.
I really got lost in all those "circuits" and "devices". Your new nodes look like some kind of "barebone" GUI for existing websocket. A very simple transposition of the websocket syntax into a GUI. I really think that you should not bother Node Red users (who are looking for intuitive and user-friendly tool) with some "devices" and "circuits". They would like to see intuitive UI with "relays", "inputs" and "outputs".
After two minutes I was like OMG! How can I get back to the old nodes? Because you did not bother to rename the nodes, I had to delete all nodes by phillipsnick and uninstall the old node-red-contrib-unipi-evok package only to test your nodes. Re-installing phillipsnick's package was also a challenge. It is no longer available in "Manage palette". Thanks god the old package can still be installed manually by npm i node-red-contrib-unipi-evok...
Anyway, I really appretiate your enthusiasm for Node Red (which I share!). But I only hope that this was just some kind of prematurely released alpha version and more serious development will follow either by you or by your young colleagues from Beroun... At the moment, I stick to the old package by phillipsnick. My house depends on it....
P.S. On a more technical note, I am flooded with "SyntaxError: Unexpected token e in JSON at position 1" error messages.
I can not establish sending notifications via webhook. Evok sends notification, but without any values. This is what I recieve:
0000 50 4f 53 54 20 2f 20 48 54 54 50 2f 31 2e 31 0d POST / HTTP/1.1. 0010 0a 43 6f 6e 74 65 6e 74 2d 54 79 70 65 3a 20 61 .Content-Type: a 0020 70 70 6c 69 63 61 74 69 6f 6e 2f 78 2d 77 77 77 pplication/x-www 0030 2d 66 6f 72 6d 2d 75 72 6c 65 6e 63 6f 64 65 64 -form-urlencoded 0040 0d 0a 43 6f 6e 6e 65 63 74 69 6f 6e 3a 20 63 6c ..Connection: cl 0050 6f 73 65 0d 0a 43 6f 6e 74 65 6e 74 2d 4c 65 6e ose..Content-Len 0060 67 74 68 3a 20 39 31 0d 0a 48 6f 73 74 3a 20 31 gth: 91..Host: 1 0070 39 32 2e 31 36 38 2e 31 2e 31 39 34 3a 38 30 0d 126.96.36.199:80. 0080 0a 41 63 63 65 70 74 2d 45 6e 63 6f 64 69 6e 67 .Accept-Encoding 0090 3a 20 67 7a 69 70 0d 0a 0d 0a 5b 22 67 6c 6f 62 : gzip....["glob 00a0 5f 64 65 76 5f 69 64 22 2c 20 22 75 6e 69 74 22 _dev_id", "unit" 00b0 2c 20 22 76 61 6c 75 65 22 2c 20 22 63 69 72 63 , "value", "circ 00c0 75 69 74 22 2c 20 22 72 61 6e 67 65 5f 6d 6f 64 uit", "range_mod 00d0 65 73 22 2c 20 22 6d 6f 64 65 73 22 2c 20 22 72 es", "modes", "r 00e0 61 6e 67 65 22 2c 20 22 64 65 76 22 2c 20 22 6d ange", "dev", "m 00f0 6f 64 65 22 5d ode"]
Thank you for your help.