@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).
I'll try to summarize, I do apologies if I didn't understand well:
To fix the repeat of node 25, I would suggest adding a delay after receiving the message and before sending it to the gateway.
IMHO, when waiting for some time (1500 ns would be theoretically perfect giving current MySensors settings) after a write will cause issue for nodes that will write an answer to you, as you're still waiting after the original write, so you may think about waiting this delay before and after the write (the first one will ensure that the sender finished waiting for the ACK you sent to its write, the second one you received the ACK to your write).
As side effect, this could also fix the relay issue, as we're not protected against chance 
@Snyfir: Maybe a timing issue in MySensors code? Are both node and gateway on the same kind of hardware?
It seems also (at least for me) that 2.3.1 may be more concerned by timing issues than 2.3.0, even if I don't saw in the code what could be the real cause. You may perhaps revert to 2.3.0 and see if you still have this kind of issue?
Concerning RF24 Plus datasheet, it seems that a more recent version is available at https://infocenter.nordicsemi.com/pdf/nRF24L01P_PS_v1.0.pdf?cp=8_4_0_0
@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.
@alowhum: Perhaps something like
boolean sendWithPermission(MyMessage &msg)
{
// Check permission and send here
if (connecting_allowed){
send(msg);
}
}```@mrhutchinsonmn Even if I know we're on a MySensors forum, you may also have a look to SigFox controllers (like MKR1200, should you want something with radio already built). Consumption if very low, and radio is off until you turn it on. You can be few hundreds of kilometers away from a base station and may use SigFox portal to send an alert to any device then (i.e. SMS).
Concerning RF24 Plus datasheet, it seems that a more recent version is available at https://infocenter.nordicsemi.com/pdf/nRF24L01P_PS_v1.0.pdf?cp=8_4_0_0
@alphaHotel A bit far from a compiler, so I don't test it, but did you try to define MY_DEBUG_OTA to TRUE ?
@mrhutchinsonmn Even if I know we're on a MySensors forum, you may also have a look to SigFox controllers (like MKR1200, should you want something with radio already built). Consumption if very low, and radio is off until you turn it on. You can be few hundreds of kilometers away from a base station and may use SigFox portal to send an alert to any device then (i.e. SMS).
@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 ?