I can confirm that with 23 hours the scheduler works perfectly now! Thanks a lot!

@jkandasa I was using Compare, but yeah that solved the issue!!! Thanks!

@mitjaxp Great news!!! Many thanks for posting the solution here :thumbs_up:

@jkandasa said in Variable not update in sleep node: @wanvo Whether it is possible to make so that on a command from a node Yes, it is possible. I see some error in your request command, should be as, for more information refer this, you h request (ID_TIME_SLEEP, V_VAR5); How it is possible from the side of a node to inform in MуController, that it sleeping? And how to process this message in MyController for the automatic check box "Node Slepping" in the node properties? For now, it is not possible to mention it as a sleeping node. Please add a request on GitHub. Really everything works great! The variable of the required type is created. I inattentively read the documentation and added an extra parameter "S_CUSTOM". Many thanks for the advice! This request created. I will be very grateful if you can add this feature.

@njbuch Have you had any success?

@Axel Thanks for the logs and backup file. I do not see any issue with MyController restored in my local(I tested with SNAPSHOT version). From your log file, I see that MyController takes a lot of time to start[57, 62, 67, 1807 seconds]. seems like your raspberry PI loaded with some other application? If yes, I request to stop all other application running in your raspberry PI and try again. I recommend using RASPBIAN OS LITE edition.

@samuelmills great work!!

@wanvo Make sure you set "Alphabetical key case" to "lower", this will prevent string errors that you might see overtime

@ragflyer Yes, I guess InfluxDB will give you better result for metrics

What a stupid error! Thank you very much!

You're right, it's effectively due to the too frequent call to smartSleep. I substituted it with wait and now everything goes fine. Thanks!

@andyphan

8 Days and looking good - no errors, no crashes. Just a couple of nodes that misbehave sometimes...... On that note, today I noticed one node had not sent data for many hours and when I got to it, the led connected to pin 13 was rapidly flashing. This is not normally the case, but I can't spare the laptop to monitor the serial port for a week+ just in case it happens again - any ideas? This was using the standard MYS prog for bmp180 pressure sensor. Running on mains powered 5v pro mini.

@jkandasa Thank you!

@heyjay good!

@skywatch Could it be the oinclusion botton from another post, What happens if you setup everything without any inclusion stuff?

@Tag See update here.... https://forum.mycontroller.org/topic/224/booting-rpi3-mycontroller-from-usb-only

This is the reason I moved to a pi3 for MYC. It can boot from USB and that is the way I think best to go, just need to read up on how it all works!

@staffan Hi, Did you check the user manual file? available on download section? If your MySensors gateway is USB, select as follows, [image: 1508474314826-0d214ad7-684c-4384-86b0-053807ee98b3-image.png] Tx message processing delay: Transmission delay between on each message from MyController to this gateway to avoid the collision on MySensors network. Driver: Keep it as Auto Port name: default /dev/ttyUSB0 Baud rate: default 115200 Retry frequency: For some reason, if your gateway goes down. MyController attempt to reconnect every X seconds once. Connect your gateway on RPI USB port, run this command to know your USB port name: ls -lh /dev/ttyUSB* Once you setup the gateway on MyController, your gateway should show UP. now click on Action button on gateway and select Discover, [Note: You should have added about your node data on presentation() block of your node code.] [image: 1508475340514-f531a78d-46ca-4c88-8698-38bd375eecd3-image.png]. Now you can see your gateway and nodes on MyController.