MySensors is built around nodes that collect data and send it over radio to a gateway connected to the controller.
For your application, it sounds like you would create a node that collects information from your controller. Then you would need to add a MySensors gateway to your Domoticz setup.
I'm not sure what you mean when you say your controller can transmit the information. If your controller and Domoticz are on the same network, you could have your controller send data directly to Domoticz using http. There is info about that in the Domoticz Wiki. Or, if your controller and Domotics are on the same network, you could add a MySensors MQTT gateway to the network and have your controller sent data using MQTT messages.
Take a look at the Getting Started and Build pages on this site and you will get a good idea of how MySensors could fit in.
Hi @David-Marlinge
I have struggled with these meters in Domoticz also. I am using an S_Power meter for an energy monitor which looks like what you are using. This is my understanding:
The value on the top of the bar is the power you have most recently sent (in Watts).
Domoticz calculates kWh from the watts and the time it was sent.
kWh used today is shown on the Utility screen (your 2036.992).
Overall kWh is what is shown on the device tab (your 2311414.016).
I present an S_POWER device, then measure the current and multiply by the voltage to get the power in watts. Then I send that with a V_WATT message. I don't calculate the kWh. Domoticz calculates kWh from the Watts I send and time I send it.
For example:
present(CHILD_ID_PWR, S_POWER, "Emon 38/26H");
. . . . . . . .
MyMessage Msg_Pwr(CHILD_ID_POWER, V_WATT);
. . . . . .
send(Msg_Pwr.set(Pwr, 1));
Then the Pwr value should show up in that top bar. Domoticz will calculate the kWh used based on the time of the power updates.
I have not really used the V_KWH variable, so I'm not sure how that fits in with this one.
Yes errors on the commands given through domoticz
only one in three and taken into account
terminal copy serial
Changement entrant pour le capteur:3, New status: 0
Changement entrant pour le capteur:3, New status: 1
Changement entrant pour le capteur:3, New status: 0
Changement entrant pour le capteur:3, New status: 0
Changement entrant pour le capteur:3, New status: 0
Changement entrant pour le capteur:3, New status: 1
Changement entrant pour le capteur:3, New status: 0
Changement entrant pour le capteur:3, New status: 0
...and the local push button commands are not taken into account
in the loop something that dies its tail ??
// Inform controller if state change from input
if (debouncer.update())
{
bool newState = !digitalRead(CONTROL_INPUT_PIN);
if (newState != currentState)
{
currentState = newState;
if (currentState != controllerState)
{
send(msg.set(currentState));
}
}
}
merci Boum
@Eme Thanks for letting us know how you solved the problem - helps us all to learn. I've recently upgraded my Raspberry Pi 1b to 4 and just got it working as an ethernet gateway with standard NRF24 radio. I'm curious about a few things as I've been trying to also use a PA LNA radio but without success;
Any reason you have set up your gateway as serial and not ethernet?
What did you mean by "Don't rely on GPIO pins to power it, use a regulator". By regulator did you mean the capacitor, did you use another regulator component - I can't see from your image
Did you change the power setting of you configuration file MyConfig.h -lowering the power to "RF24_PA_LOW'?
@boum I did it in this way from some time, but it looks less elegant. I have to make many virtual devices in domoticz, devices which send data to my lcd node. It works, but i think sending data directly to lcd will work better (or not... :))
The best solution would be ask directly domoticz (gw) about data sending from other node, but propably its not work in that way
