FYI looks like on the 2.3.1 beta the transport has been changed to rf24 instead of nrf24

@mvader said in queuing and sending messages:

I want to be able to issue commands (reboot, firmware update, etc) and when they wake up to transmit via motion or ti

can anyone point me in the right direction?

I have several battery powered nodes. I want to be able to issue commands (reboot, firmware update, etc) and when they wake up to transmit via motion or timed sending of data. they receive and execute whatever command i have sent. so far i can't get this to work. if i send a reboot command from the controller during the OTA wait period. the node receives the request and reboots.. if the OTA period is over, then the node never follows the command. even after waking up. it still never executes said command.
so it seems the gateway is not queuing up the command or it's not sending when the node wakes up.

what is the correct approach to implement this and how can i troubleshoot if the GW is receiving, queuing and sending commands for a sleeping node?
running lib 2.2.0
and the gw is 2.2.0 on a RPI3

Thanks!

@tbowmo said in Sensebender Micro:

@mvader

Is it the default dualoptiboot bootloader? Then the bootloader itself does not support OTA FW. You need to put a sketch on it, that supports OTA. (Default sensebender micro sketches doesn't)

yes it's the default bootloader. yes i have OTA added to the sketch. it works if i reset the device via manual reset. but what i'd like to do is send the reboot command from myscontroller. but it seems to do nothing ever. does the bootloader support reboot? or is that something i also have to add to the sketch?

situation: i have about 15 sensors all over the house. if i update, i'd like to be able to assign the firmware, and then issue the reboot command. so upon reboot, they take the assigned firmware. what i don't want to do is have to go to each one and manually press the reset button to get it to take the firmware. i'm sure it's healthier to run up and down 3 flights of stairs. but i'm lazy

Am I able to remote reboot the sensebender micro? I can send an OTA firmware if i manually press the reset button.
but can i use the reboot command in MYScontroller? it doesn't seem to do anything when issued.

@user2684 said in NodeManager:

@mvader thanks for the feedback, I've added this issue on Github so to fix this in the next dev release https://github.com/mysensors/NodeManager/issues/344

Thanks!! here is the setup and loop part from the sketch

setup
pinMode(7, OUTPUT); // “power pin” for Light Sensor
digitalWrite(7, LOW); // switch power off

loop
  digitalWrite(7, HIGH); // switch power on to LDR
  sendLight(forceTransmit);
  digitalWrite(7, LOW); // switch power off to LDR

and the function
/*
 * Sends Ambient Light Sensor information
 * 
 * Parameters
 * - force : Forces transmission of a value
 */

void sendLight(bool force) // Get light level
{
  if (force) lastLightLevel = -1;
  int rlightLevel =  analogRead(LIGHT_PIN);
  int lightLevel =  (analogRead(LIGHT_PIN) / 10.23) ;
  if (lightLevel != lastLightLevel) {
   gw.send(msgLight.set(lightLevel));
    lastLightLevel = lightLevel;
  }

@user2684 in the sensebender sketch we turn on digital pin 7 to provide power to the LDR to read it.
i have many sensors in my house and would rather not re-wire all of them.
how can i add this cleanly in nodemgr to make it work as before?
pinMode(7, OUTPUT); // “power pin” for Light Sensor
digitalWrite(7, LOW); // switch power off

Thanks!

@gohan said in Building a Raspberry Pi Gateway:

@masmat have you tried with ethernet gateway? If I have time I'll try the mqtt this weekend

@mvader I never noticed that.... is it the mqtt GW?

I'm not using mqtt.
for debug purposes i use MYSController
every 10 seconds on the dot. it shows me the version of the gateway.

201	3/15/2018 20:47:15	RX	0 - Gateway	INTERNAL	C_INTERNAL	NO	I_VERSION	2.2.0
202	3/15/2018 20:47:25	RX	0 - Gateway	INTERNAL	C_INTERNAL	NO	I_VERSION	2.2.0
203	3/15/2018 20:47:35	RX	0 - Gateway	INTERNAL	C_INTERNAL	NO	I_VERSION	2.2.0
204	3/15/2018 20:47:45	RX	0 - Gateway	INTERNAL	C_INTERNAL	NO	I_VERSION	2.2.0
205	3/15/2018 20:47:55	RX	0 - Gateway	INTERNAL	C_INTERNAL	NO	I_VERSION	2.2.0
206	3/15/2018 20:48:05	RX	0 - Gateway	INTERNAL	C_INTERNAL	NO	I_VERSION	2.2.0

@marceloaqno any ideas about that?

1st patch is still working good for me. have had no issues since applying it.

question. is it normal/correct for the gateway to ping or spam? every 10 seconds i see the gateway announce it's version.
its not doing the full restart or anything.. just giving the 2.2.0 every 10 seconds.

@marceloaqno said in Building a Raspberry Pi Gateway:

@otto001 I'm trying to reproduce this problem, but so far I've got nothing beyond the normal behavior of mysgw.
I tried with a RPi1 and RPi3 using the fhem controller with the latest raspbian.

My uptime is at 4 days now. so far still working with your patch. CPU is at 2% and sensor network still working correctly. will report if that changes.