I can't find the bug

[PeteKnight]

I’d start by reading this:

Keep your void loop() clean

and make better use of your timers.

Also, you don’t need to do this:

@Anthony101

// the timer object
SimpleTimer timerminute;
SimpleTimer timerhour;

and this:

@Anthony101

    timerminute.run(); 
    timerhour.run(); 

A single BlynkTimer object can support up to 16 timer instances.

See the “Creating Interval Timers” section of this post:

Using BlynkTimer or SimpleTimer

Many users seem to struggle with the basic concepts of using BlynkTimer in their projects, despite the excellent discussions and tutorials that exist on this forum, so I thought I’d write a guide that will hopefully help clarify things. It’s rather long, as it attempts to explain the reasoning behind why and how we use timers, and covers some more advanced subjects, but I’ve tried to organise it in a way that helps people to find answers to specific questions… Why use a timer at all? Let’s say …

Also, it’s usual (although not strictly necessary) to use the “V” prefix when referencing virtual pins in BLYNK_WRITE, Blynk.virtualWrite and Blynk.syncVirtual commands so that they’d look like this:

Blynk.virtualWrite(V0, counter);

This would make your code more readable from most Blynkers point of view.

Also, this in your void setup won’t work:

@Anthony101

  Blynk.syncVirtual(2); //This gets the virtual pin value from server. (Needed for example after power loss)
  Blynk.syncVirtual(3);
  Blynk.syncVirtual(4);
  Blynk.syncVirtual(5);
  Blynk.syncVirtual(7);
  Blynk.syncVirtual(10);

Instead, these Blynk.syncVirtual commands should be in a BLYNK_CONNECTED() callback function
See the “Synchronising the output state with the app at startup” section of this post for more info:

Using Virtual Pins to control physical devices

I thought I’d write a guide about how to use virtual pins with app widgets such as buttons, to control physical devices such as relays, LEDs etc… Why use virtual pins anyway? I’d always recommend using virtual pins over physical pins when developing your code. There are a number of reasons, but here are what I consider to be the main ones: Virtual pins are hardware independent. This means that it’s far easier to port your code from one hardware platform to another in future (when you realise…

Pete.