Domoticz

Couldnt get it to work, so the gas and powermeters where replaced after a call to the Energy company. The new P1 smartmeters is connected with usb to Domoticz and works like a charm! Topic can be closed.

@anand There was vastly more time wasted trying to get the original concept to work, than it look to learn basics of Domoticz scripting after finding a solution used by others. The sketch complexity and size is dramarically reduced for the Node, it still responds to changes in boiler or PSU condition within a second, and reports temperatures and power condition regularly. Domoticz reconciles everything to default 5 minute time slots, this method provides boiler run times to an accuracy of a minute which is quite adequate.

SOLVED I did not managed to get i working, shifted to a Raspberry PI, that works perfect - It seems that I also get version 1.x data from the gateway, Interesting if the gateway both can receive 1.x and 2.x data from sensors.

Why not purchase a Raspberry Pie and a SD card + casing , then you have a server?

Thank you for your help. It was enough to add the if condition depending on the message.sensor.

@nca78 Nope, you didn't misunderstand at all, my experience using Domoticz is limited to basics thus far... Will look into that.. Before this PV problem arose, had been looking at recording daily pump run times for both the domestic-supply and borehole pumps, easy enough for the borehole circuit, but the domestic runs LevControl->Contactor->PressureSwitch->Pump, so the auxiliary no-volts on the Contactor is permanently closed, hence a potential solution using a vibration sensor. Thinking about this overnight it may be possible to rewire LevControl->PressureSwitch->Contactor to solve the on/off indication from the auxilary on the main Contactor. If the number of starts per 10 minutes/hour exceed a threshold , a separate alarm flag could be signalled by your suggested method. Many thanks...

@atermentis I noticed the sketch has the ”demo” DEADBEEFFEED mac address. Do all sketches have the same address? All mac addresses on a ethernet network must be unique. If they are not unique, strange communication problems will occur.

Exactly the same thing my students made 10 years ago :-)

Check out the reply I got. Hope it helps you too. https://www.domoticz.com/forum/viewtopic.php?f=6&t=28925&p=220914#p220916

After some faffing around and zero Linux confidence, tried fsck to recover the old setup and drive but still could not get the usual domoticz 8080 screen showing. Some scrolling through the Wiki troubleshooting guide later, stopped the service, chown-ed the file permissions, manual test start and the old system was back. Stopped that then started the service properly and it is all back up and running again, so once it has updated all the nodes properly will do a complete backup in preparation for a UPS powered changeover.

@dbemowsk said in New to Domoticz, joining it with Vera and Mysensors question: @homer My first question would be, what devices are not working on your Vera controller? The problem I have is that I want to use some of the cheap rf433 sensors. I have been trying to get the Candle Hub working but haven't been successful, so I'm thinking about using RF Link, which I know works with Domoticz. I'm hoping to be able to use the rf433 devices using the RF Link and having that talk to Domoticz, and then my Vera controller getting that info from Domoticz.

If you are using a serial gateway, then no, you cannot. The serial messages can only go to one place, so one of the two controllers will win. It might get mixed up - some messages to one, some to the other. I don't know about the other two types of gateway.

Hi @jack, welcome to the forum! GatewaySerial.ino is the right one. See https://www.mysensors.org/build/serial_gateway for details. SerialGateway is probably left from an old MySensors installation. It is no longer present in the MySensors code.

@flyingdomotic I tried that, only then the text status will not appear in domoticz. I didn't use/tried it for the analog value, maybe i'll try that, thank you!

In addition to the remark on declaring sensor to Domoticz, the sketch itself seems to me a bit confusing. Normally, you should do setup into setup function (stuff like pin mode, even eventually reading saved config and setting relay in correct state), presentation should contain only sendsketchinfo() & present(), loop should do the repetitive job. You should avoid blocking the loop, especially if you want to receive messages (as you did). You're using relay from pin 2 to 6 but sensor 1 to 5, but when receiving an order to set sensor x, you set pin x (instead of x+1). Result may not exactly be what you want/imagine. You're turning pump off only when receiving a message (as the test is done here), instead in the loop. You're using digitalWrite() on some analog pin (A1) ;-) You're sending udpdates every 2 seconds, while sending either changes or data at larger interval may fit better. In addition, you may also want to simplify: send(msgNEPA.set(sensorState?"0":"0")) by send(msgNEPA.set(0)) (in addition, this will send numeric value instead of string, don't think that sending a string is what you want) and send(msgNEPA.set(sensorState?"1":"1")) by send(msgNEPA.set(1)) May I suggest you explain what you have, and what you want to do, for us to guide you setting the sensors properly?

@eme If you are talking on the side of the nRF24 radio module then yes, the 4.7uf or above AFAIK is recommended in here as a minimum. I could see this happening if there were occasional packet collisions with the gateway because the radio cannot refresh fast enough due to of the quick draw of power on the radio.