@koewacko said in Reset values measured by Power Meter Pulse?:

I have looked everywhere in Domoticz how to reset the value(s) but i cannot find it.

As far I know, there's no way to remove only one value with Domoticz (as suggested, you can delete the sensor to destroy all values, but this may seems a bit aggressive

The way I do, when incorrect values are stored, is to modify Domoticz's database directly. As usual, you have to backup the DB before changing something, as doing it badly can just corrupt your DB, so your Domoticz (as almost everything is stored here).

Should you still want to proceed with DB changes, at your own risk, you may want to identify the sensor, stored in "DeviceStatus" table. As soon as you get the device idx (you may also find it on the Web interface), you should find the table(s) where data is store, which depends on device type. I don't have power pulse, so can't help you, but for energy meter, last day data is stored in "Meter" and historical data in "MeterCalendar". I usually change this table, either by modifying value and counter, or just deleting the row (depending on initial issue).

I've got a small Unix shell file that stops Domoticz, run a .sql file (where you have to insert your SQL orders) and restart Domoticz that I can share, on request.

@mfalkvidd said in Newbie wants to do everything wired:

MySensors with rs485 transport should fit your use case pretty well.

Getting back to your request, you need some kind of wired protocol to discuss between your sensors and your gateway.

Depending on cables you have, max speed of communication will vary. With UTP/STP CAT 5 or more, you may think about Ethernet. With less sophisticated cables, any serial protocol will do it. You may think about 2 end points system (RS 232) or multi-node (RS485).

As soon you have defined the physical layer, you have to think about the format of packets to be exchanged. Obviously, MySensors do it properly, and is already integrated (throughout gateways) to some popular controllers.

This is probably the reason @mfalkvidd advice you to use RS485 with MySensors

@yveaux : you're right! PIR are not so fast.

@yveaux: Would 30 seconds be a short wait time?

@alowhum: Perhaps something like

boolean sendWithPermission(MyMessage &msg)
{
  // Check permission and send here
  if (connecting_allowed){
    send(msg);
  }
}```

@alowhum said in MySensors Library - v2.x:

Being able to disable storing the routing table in memory.. implies that normally the routing table is stored somewhere else? In eeprom?

For simple network, with all nodes sending to gateway, this may just be ... nowhere, and systematically send to the destination node, without any routing.

You may also define static neighbor (like MY_NEIGHBOR_ID in the same spirit as MY_NODE_ID).

Any specific reason not using V_RAIN and send any float value ?

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?

Did you activate the child(ren) through the "Setup" > "Devices" list? If yes, the arrow on the child(ren) should be oriented to the left side. If not, activate them, giving a name. You'll then see them on the associated tabs. Note that device type depends on the type sent during presentation (so don't expect being able to declare device as a switch if you don't use the right child type)

... or you may want to connect the radio to one node, and link to the other by some means (like pins, serial ports, I2C ...)

Have a look, for example, to https://create.arduino.cc/projecthub/MajorLeeDuVoLAB/nano-i2c-io-expander-3e76fc?ref=platform&ref_id=424_updated___&offset=1262