Using the numbers from the drawing above: 1 = RTS : this needs to be put high to sent data every 10 seconds. it needs to be connected to +5V (as it looks to be ) 2 = GND : needs to connected to the emitter of the BS170 + GND of USB (as it looks to be ) The 10K pull-up to the collector is needed to ...

If have seen that the gas meter OBIS code can be different over the different meters and different installations. in this case it is the channel number The OBIS reference Channel number (n) will be defined by the installing order of the M-Bus devices. So for example a Gas meter can be installed on ...

I expect the issue with argument passing to curl. try double quotes : "$message"

Interesting solution. I could see 2 concerns: 1. It will require the owners of Domoticz to add the '--script' option to the standard source, otherwise this will have to be included every time manually when a new version has been created and one can not use the beta-versions (at least have not seen ...

I don't expect the USB to have a problem, but I have an add-on board on the GPIO pins..

Seems there are some issues with the DT overlay for the serial port on P3 https://www.raspberrypi.org/forums/view ... ty#p918021. This might impact the Razberry, the good news is they are working on it..

you could use this article : https://www.domoticz.com/wiki/Installin ... spberry_PI

maybe a Json() updatedevice call can do the job to retrigger, (but I am not sure)

you need the source code to build Domoticz from the start to include this file : https://github.com/domoticz/domoticz.

Paul

I have done the same. I update the gas (and electricity) values with a separate daemon. I already made an interface to collect the P1 values and store that in an Access database. I want to keep that for now, hence i did not use P1 hardware interface in Domoticz. Where it shows 35.036 for you, it ...

I gave a try to make some updates the Gpio.cpp: it will now support all the GPIO up to 31 it SHOULD now support 45 GPIO on Compute Module. However as I don't have a Compute Module I can not test. Maybe the owners of Domoticz want to include this in a next Beta, otherwise if you know how to compile ...

This will have to be a question to the owners of Domoticz. I expect the hardware interface will need an update. it is going to take a bit of work on the interface does not use pins or wiringPI. FROM THE INTERFACE SOURCE: "As we cannot assume domoticz runs as root (which is bad), we won't take ...

what Domoticz interface did you use before with RS232 connection ?
can you share sample of the data you can extract ?

regards,
Paul

I expect that creating a device on top of the dummy hardware layer. Then have a background task running that is extracting the information and then updating that device information with json() udevice calls is the best way forward.

I expect the problem is related to updated "gpio readall" output. That has changed according to http://wiringpi.com/wiringpi-and-the-raspberry-pi-compute-board. If you look in hardware/Gpio.cpp around line 395, you will see that a certain layout is expected and parsed. That is very different to what ...

does not seem to be able to find the pins.

Any log messages e.g. around not exported pins ?

does the script have the right permission?

Yyour number 1 for idx could be correct , but make sure you idx number is the same as for the device in the devices tab

The current implementation will only provide a log entry on failure. The best way forward is to create a script that is called in the on-off action of the switch instead of http-request directly. That way you could also implement with json() calls to reset to switch in case it was not successful.

for sure it does. 1 or 2 watt can be measured. When I plug in my phone charger to the Cresta and see 0.09W... (just did that to test )