Let's Control It

Dick60

Sorry, I forgot to mention that the log was the result of the adjusted script I changed already. So the result of the log is from this script: on Stekkerdoos_houtSW1#State do If [Stekkerdoos_houtSW1#State]=0 GPIO,33,0 else GPIO,33,1 endif AsyncEvent,checkSwitches endon on Stekkerdoos_houtSW2#State d...

Dick60

Push SW1(gpio13) resulting activate ST1(gpio33) and turn on the LED(gpio16). SW : GPIO=13 State=1 Output value=0 EVENT: Stekkerdoos_houtSW1#State=0 ACT : GPIO,33,0 GPIO : port#33: set to 0 ACT : AsyncEvent,checkSwitches EVENT: checkSwitches ACT : LogEntry,'checkSwitches: current state: [ST1 Or ST2]...

Dick60

The Push button is defined in my project as a PUSH BUTTON ACTIVE HIGH so monitoring the trigger on the button is possible in my opinion. but it result in sw(itch)1 actvite st(ekker)1 turns on the led (sw2 and st1 both inactive. sw(itch) 2 active st(ekker)2 turns on but turn off the led even st1 is a...

Dick60

The project is a 220v switchboard with 4 push switches (Sw1-SW4/ for manual switching the status of the relais (ST1-ST4). If one of the relais (ST1-ST4) has the status 1 (ON) a led must turn on as an indicator that one of the relais is still active. As soon as al the relais are 0 (OFF), the led is t...

Dick60

This is what I have for now: on Stekkerdoos_houtSW1#State do AsyncEvent,checkSwitches If [Stekkerdoos_houtSW1#State]=0 GPIO,33,0 else GPIO,33,1 endif endon on Stekkerdoos_houtSW2#State do AsyncEvent,checkSwitches If [Stekkerdoos_houtSW2#State]=0 GPIO,22,0 else GPIO,22,1 endif endon on checkSwitches ...

Dick60

I hoped that this would work using 2 switches but changing sw1 or sw2 will turn On the led because st1 or st2 or both changed the status but I want to keep the led on untill all ST1 AND ST2 are off. This is what I thought: on Stekkerdoos_houtSW1#State do AsyncEvent,checkSwitches If [Stekkerdoos_hout...

Dick60

This works perfectly, now I try to understand what is happening and implement it also for the other 3 switches. Thanks for now.

Dick60

this is it so probably I miss something. Now reading more carefully ATH suggested but I thought it was a nice to have but it is manditory i assume.

Dick60

This is fired. Push button activates the Relay: on Stekkerdoos_houtSW1#State do If [Stekkerdoos_houtSW1#State]=0 and [Stekkerdoos_houtRestart#State]=0 GPIO,33,0 else GPIO,33,1 endif endon This one is during Reboot to prevent unnecessary switching: On System#Boot do GPIO,4,1 //prevent activating GPIO...

Dick60

No it is not fired. After activating/deactivating the Relay I only get this in my log or tu : HTTP: GPIO,33,1 6921458: GPIO : port#33: set to 1 6921543: SW : GPIO=33 State=1 Output value=0 6921573: EVENT: Stekkerdoos_houtST1#State=0 or this one 7043752: HTTP: GPIO,33,0 7043757: GPIO : port#33: set t...

Dick60

It looked that easy but in practice it is another story. I ave installed the latest firmware on my ESP32. I have some push switches and some relays. The pushswitches activate the relay using the rules option. All works fine. If one of the switches is active, a led need to be activated as in indicati...

Dick60

Question, the name

on checkSwitches do

is one you gave. I used always the name of a switch like

on Switch1#State do

but that is not mandatory? I can use any name?

Dick60

What is the best way to handle my problem: I have 4 switches and a led indicator. If mindestens one of the 4 switches is active, the led must be turned on untill all switches are inactive. Because there is a limitation on both the AND and IF option, I see no solution for me to solve this problem.

Dick60

tested the new release and Yes, connecting wifi is much faster. Thanks to the (in dutch) "de PAASBULT"

Dick60

I've got is. The Event is called "spanningsmeter#All ". I changed it and it is switching. The final and working result is: on spanningsmeter#All do // %eventvalue% is the actual value that triggered the event if %eventvalue1%<11.80 // Above this voltage the loader is turned on GPIO,14,1 en...

Dick60

This is the entry of my log:
14122771: INA219 0x40: Voltage: 12.02
14122784: EVENT: spanningsmeter#All=12.02,0,0

Dick60

: Node82b.png (47.61 KiB) Viewed 2091 times

: Node82a.png (31.35 KiB) Viewed 2091 times

But I deactivated the GPIO14 but the relay was not activated

Dick60

I disabled the GPIO14 switch, waited for the measurement but the event is not started. But deactivating the GPIO14 than it is not possible to change the relay state because the esp doesn't know that there is a relay on GPIO14 ( I think).

Dick60

14 is my Relay to turn on the 220v of the charger. Removing the 14? In that case I cannot activate the relay

Dick60

Can you open the image? I did not know how to so I hope it works

Dick60

It is an INA219, Voltage measurement module and turn on a Battery charger

Dick60

as soon as the measurements go below or above the settings in the script the GPIO14 is not activated or deactivated. Also the event does not start.

Dick60

On my ESP8266 I loaded the 20230306 NORMAL formware. I used to have an ESP32 but that broke down. The script I used on the ESP32 was on spanningsmeter#Voltage do // %eventvalue% is the actual value that triggered the event if %eventvalue%<12.10 // Above this voltage the loader is turned on GPIO,32,1...

Dick60

I checked the config.dat of the previous firmware version and it is called config_ESP_Easy_U132_Build20116_202307. So this was the working firmware version. Can you do something with this info?

Dick60

I upgraded my ESP8266 to the latest firmware version. There is a rule to turn On/Off my Milight using Domoticz. It worked perfect untill the firmware upgrade. Turning On SendToHTTP xxx.xxx.x.xxx,8080,/json.htm?type=command&param=setcolbrightnessvalue&idx=507&hex=ffffff&brightness=100...

Dick60

latest development, I don't know why the previous solution did not work but this works for me on Clock#Time=All,**:** do if %systm_hm% < %sunrise% and %systime% < 12:00:00 // Early morning, Is Dark outside Let,2,0 //notify 1,"sunset!" else let,2,1 endif if %systime% > %sunset% and %systime...

Dick60

as far I can see, it is not started during reboot.I did some more testing and simplified the rule On Time#Initialized do if [Sunrise#State]=0 and %systime% > %sunrise% Gpio,4,1 else Gpio,4,0 endif endon Also this Event was not started. Tested The %systime% and %sunrise% in the CMD aria, the results ...

Dick60

I try to implement the solution discussed in this topic but it does not work for me. I use the mega-20220809_57b0c0c and a mega-20230306 firmware on an ESP8266 (on both the rule is not working). Coordinate are set, both %sunrise% %sunset% in the CMD are working and give the correct time. Is there a ...

Dick60

I just saw your last remark and that sound very logic. Befor I add this part I want to say that everything is working now. As soon as the light intensity came above 60 and movement was detected, the lidstrip went on. I add the new part so it is approaching the point of perfection,

Dick60

Now it seems to work. i'm glad to finish this project. Great work!

Dick60

this morning the light went on entering the room. The switch Beweging went to 1. After 30 min the lights went out, still Beweging switch had the status 1. In my opinion it has to do somenthing with the vaiables and the 30min timer. This is the log: 173664848: EVENT: serre_lichtmeting#Analog=194 1736...

Dick60

It seems to work now. I see entries in the Log that gpio 10 and 13 are turned on and that is what I missed in the solution I implemented during the day. I test it and hope, tomrrow morning, i get up and movement is is there, the lights turn on. I let you know.

Dick60

This was not the latest solution from IT aadmin but it was alost a full working solution. After my change it worked completely on UpdateLightIntensity do if [Plugin#GPIO#Pinstate#2]=0 and [int#1]=1 // Manual mode is not active, and no recent motion detected. // So we must turn off the lights. gpio,1...

Dick60

There is no more scripting in my project so this it is but I was playing around and found this part what I changed and after that changed it worked after movement: on UpdateLightIntensity do if [Plugin#GPIO#Pinstate#2]=0 and [int#1]=0 // Manual mode is not active, and no recent motion detected. // S...

Dick60

The log could help me to get more info what is happening. But still, I just copied the acual log serre_lichtmeting#Analog=483 and after this message I expect more like changing gpio10 and 13 and a PMW action . But nothing. I find that strange. I am not in coding but what I can extract from the scrip...

Dick60

In answere of your last message, that is correct. If manual mode is active, no PIR activity will turn on the leds. Perhaps some explanation, GPIO 13 is a relay that turn on the external power source for the ledstrip, G{IO 10 is a switch which is an indication if the ledstrip is On or Off. Because I ...

Dick60

Manual is active but in the log I also see no pwm settings. I turned on 13,1 manualy and leds are off. Manual http://xx.xx.xx.xxx/control?pwm=GPIO,16,100 and leds turn on. So I think that the PWm is not set, gpio 10 en 13 are not set to 1 if the lightintencity in >60. At this moment situation: Light...

Dick60

at this moment, the light intencity is 66 so I expected gpio 10 and 13 to turn on (1) but no reaction. Beweging is 1 so indicators are ok but the gpios do not switch. any idea?
Also no set for variables
%v1% 0 0

Dick60

Thanks, I'm gonna test it this evening.

Dick60

I think this is the final one. I added comment just behind your OPTIONS comment.Can you check if this is correct? on UpdateLightIntensity do if [Plugin#GPIO#Pinstate#2]=0 and [int#1]=0 // Manual mode is not active, and no recent motion detected. // So we must turn off the lights. gpio,10,0 gpio,13,0...

Dick60

I found that the var1 is not set and that the GPIO10 and 13 are not set to 1 if "Beweging " has the status of 1. I do not want to mess-up my partly working script but tried to solve it to add the GPIO,10,1 and GPIO,13,1 but that did not work and would not solve the NOT storing the VAR. Her...

Dick60

Thanks for the extra info.

Dick60

This weekend I tested your solution but the first evening, I had a major disaster, the unit worked and on a given moment it start flickering and my unit stuck in a loop. Could not restart it so I refreshed the firmware and started over again. This morning first start and it works great. One remark: ...

Dick60

Yes it make sense for me now. For a long time I wanted to do more with Variables, now it is time to read the documentation for that item.
It will test the script. Everything is in place and restarted the unit, so lets hope.

Dick60

Wauw, that was more complicated as expected. Thanks for the explanation and I test the script functionality and try to understand every part of it.

Dick60

Oh, I understand what the problem is.I did not realize. The function of the pir is, if leave the house or went to bed, the lights will turn off after finishing the 30 min pir activation. Enjoy your DINER !

Dick60

Manual mode enabled -No reaction needed from the motion sensor -Lights turn on if the light intensity is >60 but also turn off <60 -If lights on, PWM will in (de)crease the intensity of the leds. Manual mode diabled -Reaction of the motion sensor is required -Lights turn on if the light intensity is...

Dick60

I tested the script and still not the behavior I expected. The light intensity is >60 and manual mode is off and movement is on. The leds turn on but if I turn off the movement, the leds do not turn of. So both Manual mode and Movement are off and light intensity is 80.

Dick60

OK, misunderstanding. I move it and test the solution this evening

Dick60

I addapted to the PIR switch. Is this what you ment? If so, I can test it this evening. FYI the GPIO 10 gives the status (1,0) of the leds. On Beweging#State do If [Plugin#GPIO#Pinstate#2]=1 or [Plugin#GPIO#Pinstate#0]=1 If %eventvalue1%<60 GPIO,10,0 GPIO,13,0 Else GPIO,10,1 GPIO,13,1 Endif If %even...

Search found 244 matches