Let's Control It

costo wrote:A small bug seems to exists in R147 (and earlier versions too).
In the Firefox browser I get an error message after I give a url command like this:

http ://192.168.178.111/control?cmd=GPIO,4,0 or http ://192.168.178.111/control?cmd=PWM,4,10

I get this message before the normal response while the command is still executed in the normal way:

There was an error parsing the JSON document. The document may not be well-formed.
expected ',' or '}' after property value in object at line 2 column 15

after the message the command is properly executed so it is just a warning.
Apparantly the FF-browser likes to see the comma punctuation mark right after the pinnumber and before the statevalue.
In the Chromium browser I do not see this errormessage.

B.t.w. I only use linux versions of the browsers, I did not test this on windows or Mac versions.

BertB wrote:

jbaumann wrote:I2C/BME280 Problems:

Ok, now I put the 147 onto the Sonoff device. On the plus side, I now can choose whether the address to use is 0x76 or 0x77, on the minus side, I no longer see the device when scanning. The device is still on address 0x77, the default when receiving the breakout board. Pullups are used as well. Do I really have to change the address?

Cheers, Joe

I2C works okay for me on a WeMos D1 on Rx and Tx ports, but it is important to reboot after changing the ports.

Martinus wrote:Bug #15 Feedback so far:

....

Statistics: 5 to 7 (42% reported as bug)
Still only 12 reports. Does this mean that we only have 12 ESP Easy users?

As Tonia reported, it could also somehow depend on the Wifi environment like type of router or maybe traffic, distance, etc...
...

//ceiling lamp with sonoff

on switchon do
    TaskValueSet 2,2,1 //State#Relay=1
    gpio 12,1                  //Relay on
    pwm 13,1024          //LED off (pin low = LED on) 
endon

on switchoff do
    TaskValueSet 2,2,0          //State#Relay=0
    gpio 12,0                           //Relay off
    pwm 13,[State#Bright] //LED on
endon

on Button#Switch do //not really needed, pushbutton is hidden in lamp
    if [Button#Switch]=1
        TaskValueSet 1,1,0 //set switch to 0, avoids double press if event was triggered remotely
        event switchon
    else
        event switchoff
    endif
endon

on System#Boot do
    if[Clock#Time]>7:59
        TaskValueSet 2,1,500 //LED medium brightness
    endif
    if[Clock#Time]>19:59
        TaskValueSet 2,1,990 //LED dim 
    endif
    event switchon
endon

on Clock#Time=All,20:00 do //dim LED at night
    TaskValueSet 2,1,990
    If [State#Relay]=0
        PWM 13,990,5000
    Endif
endon

on Clock#Time=All,8:00 do //medium LED at day
    TaskValueSet 2,1,500
    If [State#Relay]=0
        PWM 13,500,5000
    Endif
endon

paxi wrote:Update to the post above:
this unit still hangs sometimes while the other 2 Sonoff's run solid.

EDreamZ wrote:

Martinus wrote:Current status:

• Bug #01 FIXED in R138 : Clock event at system boot issues
  Bug #02 FIXED in R139 : Domoticz MQTT support was completely broken as of R109 (so it also affects R120!)
  Bug #03 FIXED in R140 : I2C Scanner would not show PCF8574A at default address
  Bug #04 FIXED in R141 : Pulsecounter value display style elements
  Bug #05 FIXED in R141 : Some missing I2C scanner 'known devices'
  Bug #06 FIXED in R145 : Task value name remains after clearing task
  Bug #07 OPEN : Pulse counter total increases every second without pulse? - Unable to reproduce...
  Bug #08 FIXED in R142 : Missing BMP180 in I2C scanner
  Bug #09 FIXED in R142 : Missing MLX90614 in I2C scanner
  Bug #10 FIXED in R412 : Intermittent issue getting NTP time during boot
  Bug #11 FIXED in R145 : WDT crash using ADC/MQTT OpenHAB
  Bug #12 CLOSED : R142 resets configuration - (Upgrade from R143 to R145 went fine on all my units)
  Bug #13 CLOSED : IP display errors - erroneous bug report...
  Bug #14 FIXED in R146 : Ser2Net RXwait would only work as expected when used on tasknr 1
  Bug #15 OPEN: ESP server processes (Web, ICMP) become unresponsive in certain environments under certain conditions?
  Bug #16 OPEN: using single negative values in formulas produce wrong values

Bug #15 Feedback so far:

Reported as issue:
- grhhm, 16-11, MQTT
- Shardan, 17-11, no MQTT (breadboard setup?)
- Cherowly, 22-11, no MQTT
- Haggycz, 22-11, HTTP-Domoticz
- Tonia's brother, 27-11, EmonCMS, Huawei B315 4G

Reported as NON issue:
- Martinus, 26-11, HTTP-Domoticz, Linksys E3000 with DD-WRT, -69dB (outside unit)
- papperone, 26-11, MQTT-OpenHAB
- BertB, 26-11, HTTP-Domoticz
- hvdwolf, 27-11, HTTP-Pimatic
- beic, 29-11, HTTP-Domoticz, TP-Link TP-WA500G
- Tonia, 27-11, EmonCMS, Linksys WRT54GL on DD-WRT
- Shardan, 29-11, Standalone, Ubiquity UAP-AC-LR

Statistics: 5 to 7 (42% reported as bug)
Still only 12 reports. Does this mean that we only have 12 ESP Easy users?

As Tonia reported, it could also somehow depend on the Wifi environment like type of router or maybe traffic, distance, etc...
(should we all move to DD-WRT ?)
I think it's interesting to also report the RSSI value in future posts.

I've just installed an additional Access Point (Dlink DIR 505) in my home and moved two ESP Easy unit's to that AP.
See what happens during the next couple of days...

Hi all and merry christmas,

i want to share with you my experience, should be related to Bug #15...i have 10 devices in my network divided in ESP12, SONOFF and POW, all loaded with R120, networking is hosted from a cisco AP with a cisco ROUTER in cascade. Every device have its own setup and works very good with local tasks, when i try to "switch" a remote device with a SendTo command, sometime it works, sometime it doesn't.

i found that sometimes randomly, nodes disappear from the Node List of the main page, also if they are still online and reachable from the network via IP...i've also found a workaround for it...if i put a continuosly ping to every node from my pc...all nodes appear stable in all Node List of each device...

should be a Bug ? a network related problem ? Or am i wrong something in the configuration ?

Thanks in advance and sorry for my english...
Giuseppe

Ton_vN wrote:@Toffel969

Perhaps kicking an open door, but do you apply for coverage of your premises 1 single Wifi-AP, or multiple APs, or 1*AP+repeaters?

Have the own experience that for a setup with physically wide-spread ESP8266s, 1 single AP/router is hardly sufficient to cover the premises.
Only the 2 other configurations (= 1*router + multiple APs OR 1*AP/router + multiple Repeaters) assure communication-coverage of sufficient strength, although the latter setup has the handicap of reduced capacity.

Ton_vN wrote:@Toffel969

Perhaps kicking an open door, but do you apply for coverage of your premises 1 single Wifi-AP, or multiple APs, or 1*AP+repeaters?

Have the own experience that for a setup with physically wide-spread ESP8266s, 1 single AP/router is hardly sufficient to cover the premises.
Only the 2 other configurations (= 1*router + multiple APs OR 1*AP/router + multiple Repeaters) assure communication-coverage of sufficient strength, although the latter setup has the handicap of reduced capacity.