Closed JE3001 closed 2 years ago
Hi @coolchip, I had this up and running 2 years ago, it was doing pretty fine but needed to cancel the installation. As I tried to install everything a RPI4 + newest Node Red docker image I'm getting the same error.
Thanks for your help, P1Rebo
@JE3001 I've added a config parameter "debugging" in v0.6.0. This enables you to put smartmeter-obis in debug mode. You are then able to send HEX output to the smartmeter-obis maintainer Apollon77.
@P1Rebo Please also use debug mode and ask Apollon77.
Anything new concerning this topic? I get these messages, too.
Sorry. I cannot you help with this. I only use the lib from Apollon77. For me the node is still working fine and delivers me the data from my smart meter. I use Node v12.x and Node-RED 2.1.3.
If you get "No or too long answer" then enable debugging and post your HEX data. If no hex data is received check your signal source. If you use Node-RED in a Docker container be sure the docker container can use the hardware ressource (IR Reader) from your host.
I could solve the problem by changing the USB plug to another port of the Pi. Strange...
Fine. I also had curious problems for a very long time with several usb to serial converters. Changing the power source from my SBC does the trick. Since I use the new one the problems are gone.
I've tried to read my electrical smart meter with node red via the contrib-smartmeter node. The node outputs the following error massage: "smartmeter-obis error: Error: No or too long answer from Serial Device after last request."
I've checked the IR interface with Minicom and got some cryptic inputs (see attached screen shot)
, so my assumption is that the interface works fine. I've also attached the settings of the node, node red version, etc.
I use following HW:
Can anybody help here.