@rado-mori Welcome to MySensors. Does it have to be a 2560? That seems a bit overkill for what you are trying to do. A 328P should handle those few things.

@kernelpanic Output like that in most cases means that your arduino is set to communicate on a different baud rate than what you have your terminal set for. Look at the sketch you are using in the setup() method and see what value is in this statement:

Serial.begin(9600);

In this case, the baud rate is being set to 9600bps (bits per second). When you open your terminal program, you should select the same baud rate prior to opening the com port. If those two numbers do not match you can see output similar to what you are seeing.

@mfalkvidd I guess I had never tried installing the MySensors library through the library manager. I just checked my Library Manager on my linux box and I do see MySensors available. I don't typically do a lot of my Arduino stuff on my linux box. I do the majority of it on my Windows laptop. I had it installed on my linux box mainly for installing Marlin on my 3D printer main board.

@tbowmo I noticed the same thing about him running as root. It was one of the big red flags that caught my eye.

@fipster First, as your non root user that you normally log in as, open the arduino IDE and click on File > Preferences. Note the Sketchbook location at the top of the preferences window. On my Fedora linux box it is "/home/{username}/Arduino". If you have all of your sketches in a different folder such as "/root/sketchbook" in your case, copy (or move) the contents of that folder to the listed sketchbook location listed in the IDE. That folder should contain a folder called libraries. The libraries folder is where the MySensors library folder needs to go. Downloading it from github, it might name the folder "MySensors-master". Rename the folder to just "MySensors". Now restart the IDE and load your sketch and see if it will compile by hitting the checkmark icon:

It is critical that you restart the IDE after making any changes to the libraries folder and before loading your sketch. This allows the IDE to re-sync the available libraries so your sketch knows they are there. It is also critical that the MySensors library be renamed from it's github name to just "MySensors". If this is not done, the compiler will never find the MySensors.h file.

Hope that helps.

I did some googling and I didn't find anything on the XY1F specifically, but I found information on other Gree remotes. They appear to be an air conditioner manufacturer. Here is a link to a different Gree AC remote: https://www.amazon.com/Replacement-Conditioner-Remote-Control-YB1F2F/dp/B075N92FM4

Replacement GREE Air Conditioner Remote Control Model Number (Part Number) YB1F2 YB1F2F YB1FA YB1FAF

$8.47

2 available

@homer said in Quick question about sketches:

When it comes to sketches, it doesn't matter what type of controller we are using when it comes to how the sketch looks and what libraries we use, right?

In some cases a library may not work with a certain chip/controller, but for the most part you just have to compile the sketch for whatever chip/controller you are using and it should work.

The libraries that we include area purely for getting the hardware to actually work right?

Yes, the libraries are written to the specifications of the particular piece of hardware and are designed to make a piece of hardware function.

And it's the controller and it's plugins that determine how to use the info sent to it right?

If by plugins you are referring to the board definitions, then yes. The board definitions tell the compiler the specifications of the MCU chip being programmed so it knows how to compile the code.

So basically if I create a sensor of some sort, I can use different libraries not mentioned here?

Yes. You are not limited to the libraries listed here, although there can be cases where a piece of hardware has more than one available library. With that, in some cases, certain hardware may require a certain library for it to function correctly with MySensors. If you have trouble with a library, search the forums for information and if you can't find the answer to your question, post a comment in the forum.

@snyfir Looking at your code, I don't see any debug prints that you have defined yourself. You will however get debug info from the MySensors library. Also, I need to correct myself. You are better off using wait(ms) over delay(ms). Delay will halt all MySensors processing for the specified period of time where using wait(ms) will allow the process() method to continue to run.

I see that you have a call to wait(100) in your main loop. Did you just add that, or is that part of the code that fails with debug off?

@snyfir Without seeing your code we can't comment too much, but just judging from what you are saying, if it works fine with debug turned on, but not well with it off, you may need some short delay in your main loop. The delay in time that it takes to do the serial sends may be enough to make it work. Putting the delay in there may mimic those delays. Something like this might work:

#ifdef DEBUG
    Serial.println("your debug message");
#else
    delay(1);
#endif

You probably only need to do this for one debug print and then adjust the delay time to your needs.

Outside of that, post your code and we can help better.

@dzjr Thank you. Many here will appreciate that as it makes it much easier to read.

@omemanti Nice DIN rail enclosure.