1.5.4 is a few versions back now so it will help if you post the code you are using, even if it is the standard version. That will give us a starting point to work from.
Also what controller are you using.

Yes i can see your wiring now and no you are not likely to get any sort of reading with that circuit. You have the 712 wired in parallel with the charge wire, it needs to be in series instead. The load needs to be connected to the same side that the charge wire is on. So a quick re-draw of your circuit would look like this.

Don't forget to add a fuse at the battery positive.

The original drawing from earlier in this thread would also be ok

Your only getting 0 sent for the relay so it certainly won't be changing status. Perhaps post the code you are using .

@unfadingpyro I can't see your wiring diagram.

@alexsh1 I ended up using the dust sensor type for both readings. In Domoticz it allows you to set the letters to be used after the number so was easy to just add km to the end.

The original post where using dust was discussed is here

@ago1980 It should work but as I said i have not tested it. You may still need to tweak it to suit your setup.

To add extra relays I usually just duplicate the code if it is only two relays but more than that you will probably want to use a loop and perhaps an array to assign the variables etc. You will also need to add some code to your void receive function to sort out which switch/relay the incoming message is for.

The RelayActuator sketch in the MySensors examples shows a way to add more than one relay.

You could also have a look at my AC power controller project for an idea of how to use a case statement in the receive function to filter the incoming messages.

@ago1980 said in relay as a switch not as a button (domoticz):

so if I use switches I should not have problems?

Other than the issues I have outlined in my post above the toggle switch will work just like the button.

The basic re-write of the original button with relay sketch so it will work with a toggle switch and no uplink to the gateway is shown below. Remember it does not try and keep in sync with the controller other than notifying it of a change by the switch.
As @dbemowsk has already said you should also try and find out why the node is losing its uplink to the gateway.

Sketch untested but I think should be ok

/*
   Relay with toggle switch sketch
   modified to work with no uplink
   to gateway
   Toggle switch connected between pin3 and ground.
*/


#define MY_DEBUG                               // Enable debug prints to serial monitor

#define MY_RADIO_NRF24                         // Enable and select radio type attached

#define MY_TRANSPORT_WAIT_READY_MS 5000        //set how long to wait for transport ready in milliseconds

#include <MySensors.h>
#include <Bounce2.h>

#define RELAY_PIN  4      // Arduino Digital I/O pin number for relay 
#define SWITCH_PIN  3     // Arduino Digital I/O pin number for switch 
#define CHILD_ID 1        // Id of the sensor child
#define RELAY_ON 1
#define RELAY_OFF 0

Bounce debouncer = Bounce();
int oldswitchState = 0;
bool state = false;
bool firstStart = true;
MyMessage msg(CHILD_ID, V_STATUS);

void setup(){
  pinMode(SWITCH_PIN, INPUT_PULLUP);           // Setup the button pin, Activate internal pull-up  
  debouncer.attach(SWITCH_PIN);                // After setting up the button, setup debouncer
  debouncer.interval(5);

  pinMode(RELAY_PIN, OUTPUT);                 // set relay pin in output mode
  digitalWrite(RELAY_PIN, RELAY_OFF);         // Make sure relay is off when starting up
}

void presentation()  {
  // Send the sketch version information to the gateway and Controller
  sendSketchInfo("Relay & Toggle", "1.0");

  // Register all sensors to gw (they will be created as child devices)
  present(CHILD_ID, S_BINARY);
}


void loop(){

if (firstStart) {                            // this code is only run once at startup
  debouncer.update();
  oldswitchState = debouncer.read();         // set oldswitchState to the current toggle switch state
  send(msg.set(false), false);                              // notify controller of current state no ack 
  firstStart = false;                       // set firstStart flag false to prevent code from running again
}  
  debouncer.update();
  int switchState = debouncer.read();                               // Get the update value
  if (switchState != oldswitchState) {                                    // check for new throw of toggle switch
    state =  !state;                                          // Toggle the state
    digitalWrite(RELAY_PIN, state ? RELAY_ON : RELAY_OFF);    // switch the relay to the new state
    send(msg.set(state), false);                              // notify controller of current state no ack   
   oldswitchState = switchState;
  }
}

/*-------------------start of functions--------------------------*/

void receive(const MyMessage &message) {
  if (message.type == V_STATUS) {                                   // check to see if incoming message is for a switch                                      
        state = message.getBool();                                  // get the new state
        digitalWrite(RELAY_PIN, state ? RELAY_ON : RELAY_OFF);      // switch relay to new state
        
        /*---- Write some debug info----*/
        Serial.print("Incoming change for sensor:");
        Serial.print(message.sensor);
        Serial.print(", New status: ");
        Serial.println(message.getBool());         
  }
}

@ago1980 said in relay as a switch not as a button (domoticz):

I mean if GATEWAY does not work for some problem the node does not work does not turn on light

The original sketch relies on an ack from the gateway to trigger the relay, so if the gateway is not available the relay state cannot be changed by the local switch or even the controller.

Under most circumstances it would be desirable to have the local switch function no matter what the state of the network is. To do this you will need to modify the sketch so it no longer relies on the ack to make the change.

In MySensors 2.1.1 by default a node will not boot through to the loop section of your sketch if it cannot find the gateway, so the first thing you need to do is force it to move on.

The line shown below will do just that. The number at the end is how long you want the node to wait for an uplink to be established before it will move on to the rest of your sketch. It is in milliseconds, so in the example below it will wait 5 seconds. This line needs to be inserted near the top of your sketch before the #include <MySensors.h> line.

#define MY_TRANSPORT_WAIT_READY_MS 5000

After adding that you will then need to change the sketch so it no longer relies on the ack to change the relay state. that is pretty straight forward and once done your relay will then be able to be switched by the local switch no mater what the uplink status is.

The next problem you will encounter is trying to keep your controller in sync with the local node. As you can now change the state of the relay without a connection to the controller it may loose its sync to the node. So you may find your controller thinks the relay is on when it is actually off. This is where it gets a little trickier so if it is important to you that the controller stays in sync you may need to experiment a bit to find what will give you the best results.

I have some examples of relay nodes that explore ways to switch locally and try to maintain sync with the controller.
The last sketch I posted there uses requestTime() to check to see if the controller is available and though there is a trade off in how quickly you can flick the switch back and forward it at least confirms that the controller is available. Other methods may only check for the gateways presence.

Have a look you may find something of use.

Synchronising Light switch

Its a bit of an old post but some of these issues (using a toggle switch and making the switch always work) were also discussed in this post

@ryan-dick said in Imperial Units:

I believe the problem is this line:

> float temperature = static_cast<float>(static_cast<int>((getControllerConfig().isMetric?sensors.getTempCByIndex(i):sensors.getTempFByIndex(i)) * 10.)) / 10.;

You are right, that line is asking your controller as to whether you are using metric or imperial and then giving the answer in the appropriate type.

I do not use openhab but it should have a place in settings to select the correct units to be used. If you already have imperial selected in openhab it may be that openhab does not support getControllerConfig() so is not returning the correct result.

If you only ever want the results to be in imperial you could just modify the line so it no longer asks for the config from the controller and just uses imperial. I have not tried it but something like this should work

float temperature = static_cast<float>(static_cast<int>((sensors.getTempFByIndex(i)) * 10.)) / 10.;

@andrew At the moment any data enforcing you require will need to be coded in your sketch and as I have said there are ways to determine the data type required.

I am not sure as to why it is not present in the MySensors library, it may be worthwhile to start another thread on this and see what other information you can get.