Question: toggle button in OFF state

[Petruzzo73]

Is there a way to assign an OFF state to a toggle button (type="toggle") at startup? Anytime i plug USB cable or at a pico reboot the button is in ON state and i have to toggle it manually.

Thanks

[mjrgh]

I'll have a take a look at it - I'd actually expect the initial state to always be OFF, so there might be something there to fix. But one way or the other, it would probably be a good idea to add an option to set the initial state to either ON or OFF as desired. I'll let you know what I find when I have a chance to look at it.

[Petruzzo73]

Thank you

[mjrgh]

So it looks like it should be starting in OFF state as I'd expect. However, that assumes that the underlying physical button is ALSO reading as OFF initially, Is there any chance that the underlying button is reading as ON by default? For example, this would be the case if you're using a GPIO that you've wired so that pressing it connects it to GND, but it's set to active: "high" (or just doesn't have the active: property set at all, since "high" is the default). If the underlying physical control is reading as ON at startup, the toggle will immediately flip to ON state itself the first time the firmware checks its state, since the firmware will interpret the underlying button ON state as meaning that it should initiate a flip immediately.

If that doesn't shine any light on, it would probably help if you could attach your JSON configuration so I can take a look at your button setup.

[Petruzzo73]

I assigned Nightmode to toggle button and it's always ON at startup. Tried also with active: "low" with no luck.
I'm using a button board with 4 buttons and it happens only if assign "nightmode" to the button:

     {
         source: { type: "gpio", gp: 5 },
     type: "toggle",
         action: { type: "nightmode" },
     },	

     {
         source: { type: "gpio", gp: 27 },        
         action: { type: "key", key: "+" },  
     },
 
     {
         source: { type: "gpio", gp: 26 },        
         action: { type: "key", key: "-" },  
     },


     {
         source: { type: "gpio", gp: 16 },        
         action: { type: "key", key: "end" },  
     },

[mjrgh]

Can you also show me the active: "low" version, just to make sure it's in the right place?

[Petruzzo73]

    {
         source: { active: "low", type: "gpio", gp: 5 },
     type: "toggle",
         action: { type: "nightmode" },
     },	

I think the issue is related to nightmode functionality, which does not "toggle" by default but it works only when the button is pressed. So I must use type: "toggle" to get it working.

[mjrgh]

Confirmed the toggled-on-at-startup behavior. It's a bug in the software initialization that occurs when the underlying physical GPIO source is in active-low mode. I've fixed this for the next update.

[Petruzzo73]

Thanks for releasing v1.0! Looks like that this behavior is still present at startup:

    {
         source: { active: "low", type: "gpio", gp: 9 },
     type: "toggle",
         action: { type: "nightmode", mode: "toggle" },
     },	

[mjrgh]

Try taking the type: "toggle" out of the main button. That shouldn't be necessary now that the nightmode action handles that.

[Petruzzo73]

     {
         source: { active: "low", type: "gpio", gp: 5 },

// type: "toggle",
action: { type: "nightmode", mode: "toggle" },
},

Nightmode works only if you keep button pressed. No "toggle" function.

[Petruzzo73]

UPDATE: my bad, it works correctly.

Thanks