SonOff POW R2 support

Message

Prutsium · #21 Post by **Prutsium** » 18 Jun 2018, 21:34

TD-er wrote: ↑18 Jun 2018, 21:19 Domoticz is a bit strange in processing data.
You have to deliver the data in the right format and order to match the pre-defined types.
If you want to graph them in separate charts, you have to split the values using rules.

Like this rule:

Code: Select all

On POW_2_Sensors#POW_2_Voltage do
SendToHTTP 192.168.99.5,8080,/json.htm?type=command&param=udevice&idx=93&nvalue=0&svalue=[POW_2_Sensors#POW_2_Voltage] //Send the Voltage data to Domoticz
SendToHTTP 192.168.99.5,8080,/json.htm?type=command&param=udevice&idx=94&nvalue=0&svalue=[POW_2_Sensors#POW_2_Power] //Send the Watt data to Domoticz
SendToHTTP 192.168.99.5,8080,/json.htm?type=command&param=udevice&idx=95&nvalue=0&svalue=[POW_2_Sensors#POW_2_Current] //Send the Amp data to Domoticz
SendToHTTP 192.168.99.5,8080,/json.htm?type=command&param=udevice&idx=96&nvalue=0&svalue=[POW_2_Sensors#POW_2_Pulses] //Send the Usage data to Domoticz
endon

Then you have to create the 4 Dummy's (dont forget to use the right IDX)

Only 1 problem stays: Domoticz cant working with an rotating counter (it sends pulses 0-65535 and returns to 0)
Still working on that one to figure out somehow ...... would be great if ESPEasy could handle that by dividing the pulses by 12530 (means 1KW) and stores this on the ESP so we can read out an actual value.

TD-er · #22 Post by **TD-er** » 18 Jun 2018, 21:36

Support for the POW devices is still very beta (if not alpha), so all suggestions to improve are more than welcome.

Prutsium · #23 Post by **Prutsium** » 18 Jun 2018, 21:37

pa3gmi wrote: ↑18 Jun 2018, 14:42 Hi,
I have the sonoff Pow and did a flasch with ESP_Easy_mega-20180524_hard_SONOFF_POW.bin. I can see the values on the device direct, but only the voltage in Domoticz, I do not understand the way to see all the values, here mentioned by Prutsium, please will You tell me more about that. I am not a programmer 70 years old but I want to learn always something.

See my post above here.
Just make sure rules are active on the ESP and create the rule mentioned in the code above.
Change the IP and IDX to the right ones for your Domoticz.

In Domoticz create 4 Dummy sensors. The first 3 will work flawless the 4th (usage) i am still trying to figure out to get that one right.

Prutsium · #24 Post by **Prutsium** » 18 Jun 2018, 21:39

TD-er wrote: ↑18 Jun 2018, 21:36 Support for the POW devices is still very beta (if not alpha), so all suggestions to improve are more than welcome.

Then my suggestion: Store the real usage on the ESP memory somehow (i know writing in the flash sucks .....)
Not sure what other type of data Domoticz is accepting but other way could be not store every pulse but only the divided ones (12530)

TD-er · #25 Post by **TD-er** » 18 Jun 2018, 21:57

I have these modules myself too, so I will install them in the next coming days I hope.
Then I can really see what's going on and I will think of some way to make them work fine.

The Sonoff POW build was meant to be the first build that's actually "plug-and-play", so there is a lot of the new build options used in that one and I plan to make some flexible complex default settings to try on that build.

The whole idea is to make builds for those Sonoff units that have a proper default setup.

But we're not there yet.

projectsun · #26 Post by **projectsun** » 18 Jun 2018, 23:04

But when I flash this hard_POW bin to my POW ver 2.0 (not R2), after flash complete nothing happens... no webif, no ping, no ESPEasy_0. After flashing a normal or dev bin, ping is there again.
What did I do wrong?

(Tested with 20180524_hard_SONOFF_POW, 20180606_hard_SONOFF_POW, 20180615_hard_SONOFF_POW) all the same. CSE7759 is present.

Can somebody help me with this question?

TD-er · #27 Post by **TD-er** » 18 Jun 2018, 23:56

Sounds like your model is one with an ESP8266 and maybe the one you tried to flash is an ESP8285?

pa3gmi · #28 Post by **pa3gmi** » 19 Jun 2018, 18:56

Thanks for answer, I have done as you say, but until now I can get only the Voltage readout. Is this script also sensitive for the name of the unit or somewhat else?
I have fill in my Domoticz IP and port address and made 3 virtual sensors note the IDX and fill in on the right place, what else can or must I do. Has the Device self an IDX?
Thanks for your patience

Prutsium · #29 Post by **Prutsium** » 19 Jun 2018, 20:59

pa3gmi wrote: ↑19 Jun 2018, 18:56 Thanks for answer, I have done as you say, but until now I can get only the Voltage readout. Is this script also sensitive for the name of the unit or somewhat else?
I have fill in my Domoticz IP and port address and made 3 virtual sensors note the IDX and fill in on the right place, what else can or must I do. Has the Device self an IDX?
Thanks for your patience

I assume you have connected it to 220V and there is some load connected to it?
(And the relay is switched on .....)

What version of ESPEasy are you using the POW one or the DEV that i mentioned before?
Did you also change the names from my example to yours? Please share a screenshot of the device tab like this:

In my case the RED and Blue are corresponding to the names in the script under rules.

pa3gmi · #30 Post by **pa3gmi** » 20 Jun 2018, 09:13

Hi,
I have found some things that where wrong (the blue circle helps)and make them ok, now I see in Domoticz that there is contact to the ESP device my sensors are updated. But still only the voltage is coming in here.
This is the software version I have: The POW print is ver 2
Build 20102 - Mega
Libraries ESP82xx Core 2_4_1, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3
GIT version mega-20180615
Plugins 6 [Normal]
Build Md5 82bc2e38ccca02be1ce841c18b0b5
Md5 check passed.
Build time Jun 15 2018 02:17:36
Binary filename ESP_Easy_mega-20180615_hard_SONOFF_POW.bin

I see difference in the Device name, mine is : Energy (AC) - HLW8012 [TESTING]
Don’t know how to put a screenshot on this site.
In the mean time I have load the build from 19-Jun, but no difference.
This is the log output:
688892: EVENT: POW_2_Sensors#POW_2_Current =0.00
688911: EVENT: POW_2_Sensors#POW_2_Active Power=0.00
688931: EVENT: POW_2_Sensors#POW_2_Power Factor=0.00
694139: HLW8012: Read values - V=223 - A=0.00 - W=0 - Pf%=0
694143: EVENT: POW_2_Sensors#POW_2_Voltage=223.00
694152: ACT : SendToHTTP 192.168.178.49,8080,/json.htm?type=command¶m=udevice&idx=95&nvalue=0&svalue=223.00
694160: Command: sendtohttp
694205: ACT : SendToHTTP 192.168.178.49,8080,/json.htm?type=command¶m=udevice&idx=96&nvalue=0&svalue=
694213: Command: sendtohttp
694249: ACT : SendToHTTP 192.168.178.49,8080,/json.htm?type=command¶m=udevice&idx=97&nvalue=0&svalue=
694256: Command: sendtohttp
694318: EVENT: POW_2_Sensors#POW_2_Current =0.00
694338: EVENT: POW_2_Sensors#POW_2_Active Power=0.00
694359: EVENT: POW_2_Sensors#POW_2_Power Factor=0.00
698842: WD : Uptime 12 ConnectFailures 0 FreeMem 21696

: Vastleggen in volledig scherm 20062018 85542.jpg (23.85 KiB) Viewed 56706 times

Thanks, Rien

grovkillen · #31 Post by **grovkillen** » 20 Jun 2018, 10:21

For screenshots, just add them using the attachments tab below the editing box. (To the right of the options tab)

Prutsium · #32 Post by **Prutsium** » 20 Jun 2018, 10:58

pa3gmi wrote: ↑20 Jun 2018, 09:13 This is the software version I have: The POW print is ver 2
Build 20102 - Mega
Libraries ESP82xx Core 2_4_1, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3
GIT version mega-20180615

Rien,

Try the DEV version so not the POW i run the DEV version with the CSE and all works ok for me.

Prutsium · #33 Post by **Prutsium** » 20 Jun 2018, 11:03

Prutsium wrote: ↑20 Jun 2018, 10:58
pa3gmi wrote: ↑20 Jun 2018, 09:13 This is the software version I have: The POW print is ver 2
Build 20102 - Mega
Libraries ESP82xx Core 2_4_1, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3
GIT version mega-20180615
Rien,

Try the DEV version so not the POW i run the DEV version with the CSE and all works ok for me.
( run actually this one: ESP_Easy_mega-20180606_dev_ESP8266_1024.bin )

pa3gmi · #34 Post by **pa3gmi** » 20 Jun 2018, 11:47

What do you mean with "the CSE"

Thanks anyway for the fast response.

Prutsium · #35 Post by **Prutsium** » 20 Jun 2018, 12:52

pa3gmi wrote: ↑20 Jun 2018, 11:47 What do you mean with "the CSE"

Thanks anyway for the fast response.

CSE7766 is the plugin designed for the POW R2 & S31 (Correct me if i am wrong)

pa3gmi · #36 Post by **pa3gmi** » 20 Jun 2018, 13:08

Hi is it possible that i have not the right POW version on the print is Ver 2.0 the measuring chip is HLW8012
With your configuration I have now no readings at all, so the measuring circuit seems not working.

Rien

Prutsium · #37 Post by **Prutsium** » 20 Jun 2018, 13:32

pa3gmi wrote: ↑20 Jun 2018, 13:08 Hi is it possible that i have not the right POW version on the print is Ver 2.0 the measuring chip is HLW8012
With your configuration I have now no readings at all, so the measuring circuit seems not working.

Rien

Looks like you have the POW V2,0 where i have the new POW R2: https://www.itead.cc/sonoff-pow-r2.html
As this topic was about the R2 i assumed you had the R2 and not the V2.0

pa3gmi · #38 Post by **pa3gmi** » 20 Jun 2018, 13:51

Hi,
I have put theESP_Easy_mega-20180615_hard_SONOFF_POW.bin in the device and now it works, no idea what was the problem.
Thanks for all the help, I keep an eye on this site the teller is of course most interesting.
I see that the voltage measuring is about 10 volt to low, is there a way to correct this?

Rien.

Prutsium · #39 Post by **Prutsium** » 21 Jun 2018, 15:48

Btw ... this is how Domoticz handles right now the incoming data from the POW (R2)

Keep in mind i did not set any divider yet but its clear to see its not adding but just restarting the counter.
Would say this rather might be something to fix in Domoticz wil post same graph in Domoticz forum as maybe someone has a bright idea there.
( http://www.domoticz.com/forum/viewtopic ... 14&t=23878 )

Prutsium · #40 Post by **Prutsium** » 26 Jun 2018, 12:09

Update:
I Went to Tasmota for now as this does exactly what is required. It counts the usage internal and sends 2 values: Current Watt, Total Watt.

Might be an idea to look how its handled in Tasmota and implement similar in ESPEasy
The actual MQT message: 11:08:17 MQT: domoticz/in = {"idx":103,"nvalue":0,"svalue":"48;25.1","Battery":58,"RSSI":6}

sincze · #41 Post by **sincze** » 18 Aug 2018, 13:15

The following rules will allow the POW2 to report the data to domoticz. you create a Voltage, Amp, Watt, and Electric Counter (calculated) in domoticz as virtual devices. In addition you can add a virtual switch to toggle the relais_switch.
https://www.domoticz.com/forum/viewtopi ... 78#p187554

Devices 1: Energy (AC) - CSE7766 [TESTING] Energy
Devices 2: Switch input - Switch SW_1 GPIO-0
Devices 3: Switch input - Switch relais (idx 599) GPIO-12
Devices 4: Generic - System Info POW2_RSSI (idx 601)
Devices 5: Generic - Dummy Device Calculation

Code: Select all

On System#Boot do
	TaskValueSet 5,1,0
	TaskValueSet 5,2,0
	TaskValueSet 5,3,0
EndOn

// LAMP CONTROLLING INCLUDING LED LIGHT

on lamp_on do
	gpio,12,1
	gpio,13,0
endon

on lamp_off do
	gpio,12,0
	gpio,13,1
endon

on SW_1#Switch do
	if [SW_1#Switch]=1
		gpio,12,1
		gpio,13,0
	else
		gpio,12,0
		gpio,13,1
	endif
endon

on Energy#Voltage do

	if Clock#Time=All,**:*0 do
		SendToHTTP 192.168.1.10,8080,/json.htm?type=command&param=udevice&idx=600&nvalue=0&svalue=[Energy#Voltage]
		SendToHTTP 192.168.1.10,8080,/json.htm?type=command&param=udevice&idx=608&nvalue=0&svalue=[Energy#Power]
		SendToHTTP 192.168.1.10,8080,/json.htm?type=command&param=udevice&idx=603&nvalue=0&svalue=[Energy#Power]
		SendToHTTP 192.168.1.10,8080,/json.htm?type=command&param=udevice&idx=604&nvalue=0&svalue=[Energy#Current]
	endif
				
	if [Energy#Voltage]!=[Calculation#Voltage]
		SendToHTTP 192.168.1.10,8080,/json.htm?type=command&param=udevice&idx=600&nvalue=0&svalue=[Energy#Voltage] // Voltage
		TaskValueSet 5,1,[Energy#Voltage]
	endif

	if [Energy#Power]!=[Calculation#Power]
		SendToHTTP 192.168.1.10,8080,/json.htm?type=command&param=udevice&idx=603&nvalue=0&svalue=[Energy#Power] // Calculated KwH.
		SendToHTTP 192.168.1.10,8080,/json.htm?type=command&param=udevice&idx=608&nvalue=0&svalue=[Energy#Power] // Watt only
		TaskValueSet 5,2,[Energy#Power]
	endif

	if [Energy#Current]!=[Calculation#Current]
		SendToHTTP 192.168.1.10,8080,/json.htm?type=command&param=udevice&idx=604&nvalue=0&svalue=[Energy#Current] // Amp
		TaskValueSet 5,3,[Energy#Current]
	endif
		TaskValueSet 5,4,[Energy#Pulses]

endon

TD-er · #42 Post by **TD-er** » 18 Aug 2018, 13:23

sincze wrote: ↑18 Aug 2018, 13:15 The following rules will allow the POW2 to report the data to domoticz. [...]

This should be at the wiki I guess.

sincze · #43 Post by **sincze** » 18 Aug 2018, 13:31

If it is good enough for the Wiki I can add it

TD-er · #44 Post by **TD-er** » 18 Aug 2018, 16:45

sincze wrote: ↑18 Aug 2018, 13:31 If it is good enough for the Wiki I can add it

Well it is clear enough for me, so if I install my own, I know where to look for instructions, but since I am not that well organized I am sure it will take forever to find again

So please do add it to the wiki.

Djoe · #45 Post by **Djoe** » 27 Aug 2018, 09:35

Hi,

@sincze which version of mega do you use?

I have try mega_20180826 and mega_20180719, both correctly show values from CSE7759, but http push from rules doesn't work...

This rules work fine:
On WIFI#RSSI do
SendToHTTP x.x.x.x,8080,/json.htm?type=command&param=udevice&idx=88&nvalue=0&svalue=[POW#Voltage]
endon

Confirmed by logs:
Aug 26 21:32:56 POW EspEasy: SYS : -77.00
Aug 26 21:32:56 POW EspEasy: EVENT: WIFI#RSSI=-77.00
Aug 26 21:32:56 POW EspEasy: ACT : SendToHTTP x.x.x.x,8080,/json.htm?type=command&param=udevice&idx=88&nvalue=0&svalue=235.07
Aug 26 21:32:56 POW EspEasy: Command: sendtohttp

But this one is never triggered:
On POW#Current do
SendToHTTP x.x.x.x,8080,/json.htm?type=command&param=udevice&idx=89&nvalue=0&svalue=[POW#Power];[POW#Pulses]
SendToHTTP x.x.x.x,8080,/json.htm?type=command&param=udevice&idx=90&nvalue=0&svalue=[POW#Current]
endon

Greetings from Tahiti!

sincze · #46 Post by **sincze** » 27 Aug 2018, 10:32

Djoe wrote: ↑27 Aug 2018, 09:35 Hi,

@sincze which version of mega do you use?

I have try mega_20180826 and mega_20180719, both correctly show values from CSE7759, but http push from rules doesn't work...

This rules work fine:
On WIFI#RSSI do
SendToHTTP x.x.x.x,8080,/json.htm?type=command&param=udevice&idx=88&nvalue=0&svalue=[POW#Voltage]
endon

Confirmed by logs:
Aug 26 21:32:56 POW EspEasy: SYS : -77.00
Aug 26 21:32:56 POW EspEasy: EVENT: WIFI#RSSI=-77.00
Aug 26 21:32:56 POW EspEasy: ACT : SendToHTTP x.x.x.x,8080,/json.htm?type=command&param=udevice&idx=88&nvalue=0&svalue=235.07
Aug 26 21:32:56 POW EspEasy: Command: sendtohttp

But this one is never triggered:
On POW#Current do
SendToHTTP x.x.x.x,8080,/json.htm?type=command&param=udevice&idx=89&nvalue=0&svalue=[POW#Power];[POW#Pulses]
SendToHTTP x.x.x.x,8080,/json.htm?type=command&param=udevice&idx=90&nvalue=0&svalue=[POW#Current]
endon

Greetings from Tahiti!

mmm strange indeed. ntp was enabled?? to have the timer work for you?

Code: Select all

On System#Boot do
	TaskValueSet 5,1,0
	TaskValueSet 5,2,0
	TaskValueSet 5,3,0
EndOn

// LAMP CONTROLLING INCLUDING LED LIGHT

on lamp_on do
	gpio,12,1
	gpio,13,0
endon

on lamp_off do
	gpio,12,0
	gpio,13,1
endon

on SW_1#Switch do
	if [SW_1#Switch]=1
		gpio,12,1
		gpio,13,0
	else
		gpio,12,0
		gpio,13,1
	endif
endon

on Energy#Power do

	if Clock#Time=All,**:*0 do
		SendToHTTP x.x.x.x,8080,/json.htm?type=command&param=udevice&idx=11&nvalue=0&svalue=[Energy#Voltage]
		SendToHTTP x.x.x.x,8080,/json.htm?type=command&param=udevice&idx=18&nvalue=0&svalue=[Energy#Power]
		SendToHTTP x.x.x.x,8080,/json.htm?type=command&param=udevice&idx=13&nvalue=0&svalue=[Energy#Power]
		SendToHTTP x.x.x.x,8080,/json.htm?type=command&param=udevice&idx=14&nvalue=0&svalue=[Energy#Current]
	endif
				
	if [Energy#Voltage]!=[Calculation#Voltage]
		SendToHTTP x.x.x.x,8080,/json.htm?type=command&param=udevice&idx=1&nvalue=0&svalue=[Energy#Voltage] // Voltage
		TaskValueSet 5,1,[Energy#Voltage]
	endif

	if [Energy#Power]!=[Calculation#Power]
		SendToHTTP x.x.x.x,8080,/json.htm?type=command&param=udevice&idx=13&nvalue=0&svalue=[Energy#Power] // Calculated KwH.
		SendToHTTP x.x.x.x,8080,/json.htm?type=command&param=udevice&idx=18&nvalue=0&svalue=[Energy#Power] // Watt only
		TaskValueSet 5,2,[Energy#Power]
	endif

	if [Energy#Current]!=[Calculation#Current]
		SendToHTTP x.x.x.x,8080,/json.htm?type=command&param=udevice&idx=14&nvalue=0&svalue=[Energy#Current] // Amp
		TaskValueSet 5,3,[Energy#Current]
	endif
		TaskValueSet 5,4,[Energy#Pulses]

endon

If you modify it like this??
it will now be triggered if the Power value changes.. not the voltage.
Should be okay to get the data into domoticz.
Please let me know.

Djoe · #47 Post by **Djoe** » 28 Aug 2018, 08:59

Thank you for your reply,

I don't use NTP (long time ago it was not stable and all is automated from domoticz).
But if you really want me to test with NTP I can do it (is there a link between NTP and a triggered property?)

I have tested again all properties as "trigger", here below the complete rules:

Code: Select all

On Button#State do
 if [Relay#State]=1
  gpio,12,0
 else
  gpio,12,1
 endif
endon

On System#Boot do
 gpio,12,1
endon

On WIFI#RSSI do
 SendToHTTP xxx,8080,/json.htm?type=command&param=udevice&idx=88&nvalue=0&svalue=[POW#Voltage]
endon

On POW#Power do
 SendToHTTP xxx,8080,/json.htm?type=command&param=udevice&idx=89&nvalue=0&svalue=[POW#Power];[POW#Pulses]
 SendToHTTP xxx,8080,/json.htm?type=command&param=udevice&idx=90&nvalue=0&svalue=[POW#Current]
endon

On POW#Current do
 SendToHTTP xxx,8080,/json.htm?type=command&param=udevice&idx=89&nvalue=0&svalue=[POW#Power];[POW#Pulses]
 SendToHTTP xxx,8080,/json.htm?type=command&param=udevice&idx=90&nvalue=0&svalue=[POW#Current]
endon

On POW#Voltage do
 SendToHTTP xxx,8080,/json.htm?type=command&param=udevice&idx=99&nvalue=0&svalue=test_vol
endon

On POW#Pulses do
 SendToHTTP xxx,8080,/json.htm?type=command&param=udevice&idx=99&nvalue=0&svalue=test_pul
endon

For information the "Pulses" property is configured with the formula : %value%/12530
There is no external sensor connected to this POW.

Here below the log (through syslog with "Info" level) :

Aug 27 20:46:09 POW EspEasy: SYS : -77.00
Aug 27 20:46:09 POW EspEasy: EVENT: WIFI#RSSI=-77.00
Aug 27 20:46:09 POW EspEasy: ACT : SendToHTTP 10.0.0.4,8080,/json.htm?type=command&param=udevice&idx=88&nvalue=0&svalue=232.76
Aug 27 20:46:09 POW EspEasy: Command: sendtohttp
Aug 27 20:46:09 POW EspEasy: SYS : 484.00
Aug 27 20:46:09 POW EspEasy: EVENT: SONOFF#Uptime=484.00
Aug 27 20:46:10 POW EspEasy: Domoticz: Sensortype: 1 idx: 83 values: 484.00
Aug 27 20:46:10 POW EspEasy: WD : Uptime 485 ConnectFailures 0 FreeMem 14560
Aug 27 20:46:39 POW EspEasy: WD : Uptime 485 ConnectFailures 0 FreeMem 14584
Aug 27 20:47:09 POW EspEasy: WD : Uptime 486 ConnectFailures 0 FreeMem 14512
Aug 27 20:47:39 POW EspEasy: WD : Uptime 486 ConnectFailures 0 FreeMem 14512
Aug 27 20:48:09 POW EspEasy: WD : Uptime 487 ConnectFailures 0 FreeMem 14512
Aug 27 20:48:39 POW EspEasy: WD : Uptime 487 ConnectFailures 0 FreeMem 14512
Aug 27 20:49:09 POW EspEasy: WD : Uptime 488 ConnectFailures 0 FreeMem 14512

I have switch on and off 3 times the light connected to the POW... The value are correctly shown on the POW:

Voltage: 232.76
Power: 18.11
Current: 0.13
Pulses: 9949.00

Have you compile your own binary for your POW or are you using a binary delivered by a release?

My POW R2 is written V1.0 on the PCB...

Thank you gain,
Mc/

sincze · #48 Post by **sincze** » 28 Aug 2018, 10:00

I use the following: mega-20180723. (Development)

Regarding NTP usage I once read somewhere it is needed to have the timer function trigger correctly.
However since then I enable it on all my devices. So not sure what happens if I disable it.

ManS-H · #49 Post by **ManS-H** » 28 Aug 2018, 11:32

I like the rules, but my question. Can i also used them for my first generation Sonoff Pow with the HLW8012? And if it's yes what must i change in the rules.

Djoe · #50 Post by **Djoe** » 28 Aug 2018, 11:46

I have upgraded the POW to mega-20180723 (dev), and it's not working better...
Very strange...
I'm going to continue to push CSE7759 data through the wifi#rssi trigger, but it's not a "realtime" push, so not very good for the appliance I would like to run....

I have another POW in a box, I will get it out tomorrow and I will try with this one...

I also use timer (without NTP) on a sonoff basic, like this :

Code: Select all

On Rules#Timer=1 do
 timerSet,2,21600
endon

It work:
Aug 26 16:00:02 Piscine EspEasy: Command: timerset
Aug 26 16:00:04 Piscine EspEasy: EVENT: Rules#Timer=1
Aug 26 16:00:04 Piscine EspEasy: ACT : timerSet,2,21600
Aug 26 16:00:04 Piscine EspEasy: Command: timerset
Aug 26 22:00:05 Piscine EspEasy: EVENT: Rules#Timer=2
Aug 26 22:00:05 Piscine EspEasy: ACT : timerSet,3,21600
Aug 26 22:00:05 Piscine EspEasy: Command: timerset

But if the number of second is to high (I don't remember the limit), I notice some strange behavior (next timer not triggered, or triggered in a shorter time).
Since I use "small" number, it's work perfectly...

sincze · #51 Post by **sincze** » 28 Aug 2018, 15:54

ManS-H wrote: ↑28 Aug 2018, 11:32 I like the rules, but my question. Can i also used them for my first generation Sonoff Pow with the HLW8012? And if it's yes what must i change in the rules.

I don't know for certain, could be if the data is populated in the same way,
The rules are in that way quite universal to use.
However as we can see in the forum. For some people they seem to work for others they don''t. Pretty strange.
Same goes for the timer. It can be used without ntp.

I use a similar setup for my NPN watermeter where I got the idea. That one also works flawless.

Djoe · #52 Post by **Djoe** » 29 Aug 2018, 10:10

I have try a second POW R2 I had.

I have exactly the same behavior : no SYS or EVENT log when a CSE7766 properties is changing (for instance Voltage).
I have activated NTP to be sure it's not due to this config.
And... always the same...
My first and second POW R2 have a similar behavior..

I really don't understand why, with your POW, you can trigger CSE7766 properties !

With mega-20180714 I have a new line in the syslog:

Aug 28 22:07:47 POW2 EspEasy: LoopStats: shortestLoop: 49 longestLoop: 891267 avgLoopDuration: 103.29 systemTimerDuration: 23.94 systemTimerCalls: 31 loopCounterMax: 612244 loopCounterLast: 286060 countFindPluginId: 0

Next time I will activate more debug level to try to understand a little bit better what is happening...

sincze · #53 Post by **sincze** » 29 Aug 2018, 11:15

Djoe wrote: ↑29 Aug 2018, 10:10 I have try a second POW R2 I had.

I have exactly the same behavior : no SYS or EVENT log when a CSE7766 properties is changing (for instance Voltage).
I have activated NTP to be sure it's not due to this config.
And... always the same...
My first and second POW R2 have a similar behavior..

I really don't understand why, with your POW, you can trigger CSE7766 properties !

With mega-20180714 I have a new line in the syslog:

Aug 28 22:07:47 POW2 EspEasy: LoopStats: shortestLoop: 49 longestLoop: 891267 avgLoopDuration: 103.29 systemTimerDuration: 23.94 systemTimerCalls: 31 loopCounterMax: 612244 loopCounterLast: 286060 countFindPluginId: 0

Next time I will activate more debug level to try to understand a little bit better what is happening...

Let's sync both our debug settings to find out what happens okay?

Djoe · #54 Post by **Djoe** » 31 Aug 2018, 11:23

I think I have understood.

My gold was to work as a "push" system.
In my CSE settings, I have put 0 (zero) in "Interval" field.
I was thinking than a trigger was coming when a value is changing (like the "Generic system info" with the RSSI or UPTIME).
It was a mistake.

When I put for instance 10 (seconds) in this "Interval" field, I receive the events:

Code: Select all

Aug 30 22:42:33 POW EspEasy: EVENT: POW#Voltage=233.91
Aug 30 22:42:33 POW EspEasy: EVENT: POW#Power=0.00
Aug 30 22:42:33 POW EspEasy: EVENT: POW#Current=0.00
Aug 30 22:42:33 POW EspEasy: EVENT: POW#Pulses=1.79
Aug 30 22:42:49 POW EspEasy: WD   : Uptime 80 ConnectFailures 0 FreeMem 14672
Aug 30 22:43:17 POW EspEasy: SYS  : -72.00
Aug 30 22:43:17 POW EspEasy: EVENT: WIFI#RSSI=-72.00
Aug 30 22:43:17 POW EspEasy: SYS  : 80.00
Aug 30 22:43:17 POW EspEasy: EVENT: SONOFF#Uptime=80.00
Aug 30 22:43:17 POW EspEasy:  Domoticz: Sensortype: 1 idx: 83 values: 80.00
Aug 30 22:43:19 POW EspEasy: WD   : Uptime 80 ConnectFailures 0 FreeMem 14672
Aug 30 22:43:33 POW EspEasy: EVENT: POW#Voltage=234.20
Aug 30 22:43:33 POW EspEasy: EVENT: POW#Power=0.00
Aug 30 22:43:33 POW EspEasy: EVENT: POW#Current=0.00
Aug 30 22:43:33 POW EspEasy: EVENT: POW#Pulses=1.79

It work like a "pull" system.
Every 10 second, I request the CSE chip to refresh all values.

So now I understand why you are using dummy device in your POW.
The goal is to store in the ESP the last value, to only send HTTP when a value is changing.

So you recreate a "push" system through a "pull" config in the ESP...

sincze · #55 Post by **sincze** » 01 Sep 2018, 15:44

Indeed I use Dummy devices to only send data to domoticz if something was changed

Could you try the following: DIVIDE AND CONQUER

Rules 1:

Code: Select all

On System#Boot do
	TaskValueSet 5,1,0
	TaskValueSet 5,2,0
	TaskValueSet 5,3,0
	TaskValueSet 5,4,0
	TimerSet,1,30
EndOn

on Rules#Timer=1 do  					
	if [Calculation#Voltage]!=[Energy#Voltage]
		SendToHTTP <ipadres>,8080,/json.htm?type=command&param=udevice&idx=600&nvalue=0&svalue=[Energy#Voltage] // Voltage
		TaskValueSet 5,1,[Energy#Voltage]
	endif

	if [Calculation#Power]!=[Energy#Power]
		SendToHTTP <ipadres>,8080,/json.htm?type=command&param=udevice&idx=603&nvalue=0&svalue=[Energy#Power] // KwH.
		SendToHTTP <ipadres>,8080,/json.htm?type=command&param=udevice&idx=608&nvalue=0&svalue=[Energy#Power] // Watt
		TaskValueSet 5,2,[Energy#Power]
	endif

	if [Calculation#Current]!=[Energy#Current]
		SendToHTTP <ipadres>,8080,/json.htm?type=command&param=udevice&idx=604&nvalue=0&svalue=[Energy#Current] // Amp
		TaskValueSet 5,3,[Energy#Current]
	endif

	TaskValueSet 5,4,[Energy#Pulses]
	TimerSet,1,30
endon

Rules 2

Code: Select all

// LAMP CONTROLLING INCLUDING LED LIGHT

on lamp_on do
	gpio,12,1
	gpio,13,0
endon

on lamp_off do
	gpio,12,0
	gpio,13,1
endon

on SW_1#Switch do
	if [SW_1#Switch]=1
		gpio,12,1
		gpio,13,0
	else
		gpio,12,0
		gpio,13,1
	endif
endon

Rules 3

Code: Select all

on Clock#Time=All,**:*0 do
	SendToHTTP <ipadres>,8080,/json.htm?type=command&param=udevice&idx=600&nvalue=0&svalue=[Energy#Voltage]
	SendToHTTP <ipadres>,8080,/json.htm?type=command&param=udevice&idx=608&nvalue=0&svalue=[Energy#Power]
	SendToHTTP <ipadres>,8080,/json.htm?type=command&param=udevice&idx=603&nvalue=0&svalue=[Energy#Power]
	SendToHTTP <ipadres>,8080,/json.htm?type=command&param=udevice&idx=604&nvalue=0&svalue=[Energy#Current]
endon

That should give you the result you want.

and leave the interval at 10 as you discovered.

Djoe · #56 Post by **Djoe** » 02 Sep 2018, 06:17

Yes now it's working, I have simplify the rules like this :

Code: Select all

On Button#State do // To have the local button working for ON OFF
 if [Relay#State]=1
  gpio,12,0
 else
  gpio,12,1
 endif
endon

On System#Boot do // To have the relay ON after reboot
 gpio,12,1
endon

On WIFI#RSSI do // To send voltage every 5 minutes
 SendToHTTP ip,8080,/json.htm?type=command&param=udevice&idx=88&nvalue=0&svalue=[POW#Voltage]
endon

On POW#Current do // To send power and current only when the current change
 if [POW#Current]!=[LAST#Current]
  SendToHTTP ip,8080,/json.htm?type=command&param=udevice&idx=89&nvalue=0&svalue=[POW#Power]
  SendToHTTP ip,8080,/json.htm?type=command&param=udevice&idx=90&nvalue=0&svalue=[POW#Current]
  TaskValueSet 6,1,[POW#Power]
  TaskValueSet 6,2,[POW#Current]
 endif
endon

I trigger the Current only and not the Power because the power is changing to mush time (to avoid a JSON push every 10 sec).

The interval on the WIFI device is 300 sec.
The interval on CSE device is 10 sec.

The only last issue is that my device is rebooting regularly.

Code: Select all

Boot	Manual reboot (26)
Reset Reason	Hardware Watchdog

I think it's normal because the CSE code is in development / testing.
I have disabled it just now to see if the reboot continue or not for the next 48 hours.

I have never try to go in the code to debug the plugin..
I have download Visual Studio Code and PlaformIO plugin but when I load the source code I have some issue...

Have you try to go in the code to understand better how it work ?

Have a good week-end!

TD-er · #57 Post by **TD-er** » 02 Sep 2018, 09:32

This hardware watchdog issue has been reported a lot by other users and for now I have not really a clue what is causing it.

sincze · #58 Post by **sincze** » 02 Sep 2018, 09:49

I did not see the HW watchdog.

Does it stop measuring and then reboot?
Or just reboot without any notice?

As a reboot results in a system that is -off- I should have noticed.

It is monitoring my stove. So not in use daily however switched on.
To avoid red bars in domoticz I push all data every 10 minutes at least. "":"0. Can of course be modified to every hour/day or so.

sincze · #59 Post by **sincze** » 02 Sep 2018, 12:56

Talk of the devil.. First hardware watchdog this morning at 11:46.
Would it be the 10 sec read-out?

Unfortunately the following does not switch the relais on after the reboot .. well after a reboot it switches on for 1 sec and then back off.
So maybe it starts with the rules from there.. Don't know yet.

Code: Select all

On System#Boot do // To have the relay ON after reboot
 gpio,12,1
endon

Same if I set the hardware GPIO to HIGH by default... it is the same result. On for 1 sec and then back off.

Djoe · #60 Post by **Djoe** » 05 Sep 2018, 09:06

@sincze
"well after a reboot it switches on for 1 sec and then back off"

I had a behavior like this a couple of week before, I have changed the mega version and the issue was solved.
Actually I'm testing mega-20180804 and the relay stay on after reboot.

@TD-er

The POW is my only device which have hardware watchdog.
I have try to disabled the CMS plugin : no better results.
I have deleted the CMS plugin in the device tab : no better results.

I have 2 other Sonoff Basic (with external sensors) + 1 Sonoff Touch (without external sensor) that reboot regularly (1000 to 4000 minutes uptime).
But there is no reference to a "Reset reason".. For instance:

Uptime 0 days 1 hours 38 minutes
Load 8% (LC=12409)
Free Mem 12896 (12112 - sendContentBlocking)
Boot Manual reboot (37)

I have only 1 Sonoff Basic (without external sensor) with a big uptime (more than 40000 minutes). The installed firmware is mega-20180503...

When I will have more time I will try to go in your code..... I hope it will not be a empty promise !

Djoe · #61 Post by **Djoe** » 09 Sep 2018, 07:25

@sincze

I have found the issue about

Code: Select all

On System#Boot do // To have the relay ON after reboot
 gpio,12,1
endon

to avoid switching on then off after 1 sec. I guest that you have a switch in domoticz to control the relay in the POW, and the issue come from domoticz in my automation. It's strange because the mega-20180808 didn't have this issue (all release after have the "issue").

You have to :
- let the "Pin mode 12" as default in "GPIO boot states"
- put 0sec interval in the relay device (gpio-12)
- untick the "send boot state" in the relay device

I saw a mix between the command from the POW to domoticz (to yes "hey I'm switched on"), and the command from domoticz to the POW (the domoticz switch, when it receive a ON state, send back the same command to the POW, so a gpio,12,1). It's not clear for me who is send the command before the real state of the POW's relay, but if you don't send the initial state to the domoticz server, it working on my side.

If you put a interval greater than 0, it's send the initial state too.

sincze · #62 Post by **sincze** » 09 Sep 2018, 11:26

Djoe wrote: ↑09 Sep 2018, 07:25
You have to :
- let the "Pin mode 12" as default in "GPIO boot states"
- put 0sec interval in the relay device (gpio-12)
- untick the "send boot state" in the relay device

If you put a interval greater than 0, it's send the initial state too.

Tnx

, got it. And have implemented your suggestions 1,2,3. DId not try the interval > 0 yet.
Issued a: Tools -> Reboot ESP.

The Relais Switch value stays 0, i would expect 1. Will have to walk to the machine to view the actual state.

By the way all Sonoff would have a 1024 Flash I believe. Preventing OTA update, so that is what I thought.
Playing around with your suggestions. I noticed:

Code: Select all

Flash Chip ID	Vendor: 0xEF Device: 0x4016
Flash Chip Real Size:	4096 kB
Flash IDE Size:	1024 kB
Flash IDE speed:	40 MHz
Flash IDE mode:	DOUT

I guess OTA update is possible for the POW R2?

TD-er · #63 Post by **TD-er** » 09 Sep 2018, 22:14

If that one really has a 4 MB flash, it would be worth to flash to 4M version.
Only thing is, you will have to flash it either using a 2-step OTA or via serial.
You will also loose the settings.

In short, the flash layout is:
Active sketch => free space for OTA => SPIFFS (filesystem for settings) => end of flash-space.
There is more, but generally speaking, the flash has this layout.

So changing from 1M to 4M will erase the SPIFFS and thus your settings.
Also, for an OTA update there is simply no room when it is setup for 1M flash.

Djoe · #64 Post by **Djoe** » 11 Sep 2018, 09:14

All my sonoff basic have 1024 flash (v1.1 and R2).
All my sonoff pow have 4096 flash (only R2).

I always update my POW through OTA without any issue (I use the dev-4096 release).

About sonoff basic, I only update through serial connection.
The 2-step OTA firmware is too big to be store in the free space of a 1024 flash (if we use the "ready to use" firmware in each the release) :
- Sketch Size 660 kB (212 kB free)
- we need 276848 free space for the ESPEasyUploaderMega

But I haven't yet compile my own firmware, perhaps it's the better solution to reduce the size of the firmware..
I will do... when I will have time... Like everybody

sincze · #65 Post by **sincze** » 11 Sep 2018, 14:31

Ota update possible from 1024 version to 4096 release?

sincze · #66 Post by **sincze** » 14 Sep 2018, 18:57

I moved the Sonoff from powering stove + led strip to just the Stove.

It has now been running for several days without a hardware watchdog reset

: Sonoff POW R2-5-days.JPG (36.78 KiB) Viewed 36592 times

Djoe · #67 Post by **Djoe** » 15 Sep 2018, 07:29

Strange..
I continue to have hardware watchdog (every day)..
I have read a little bit more about it, it's triggered when the watchdog timer is not reset during 8 sec.
So that mean that the code is in a deadlock somewhere (probably)..

I just arrive this evening to compile the firmware..
Investigation is continuing...

TD-er · #68 Post by **TD-er** » 16 Sep 2018, 10:48

Djoe wrote: ↑15 Sep 2018, 07:29 Strange..
I continue to have hardware watchdog (every day)..
I have read a little bit more about it, it's triggered when the watchdog timer is not reset during 8 sec.
So that mean that the code is in a deadlock somewhere (probably)..

I just arrive this evening to compile the firmware..
Investigation is continuing...

A lot of people have reported these and it is well on my radar.
If you found something, please open a new topic about it here on the forum.

My suspicion is something network related since updating to core library 2.4.2: https://github.com/esp8266/Arduino/releases/tag/2.4.2

sincze · #69 Post by **sincze** » 20 Sep 2018, 20:30

TD-er wrote: ↑16 Sep 2018, 10:48
A lot of people have reported these and it is well on my radar.
If you found something, please open a new topic about it here on the forum.

My suspicion is something network related since updating to core library 2.4.2: https://github.com/esp8266/Arduino/releases/tag/2.4.2

Mmm I guess @TD'er is looking in the right direction. My POW R2 works fine..
However when I make WIFI changes (as I just bought UnifI stuff for the complete house) and do something with the WIFI (restart, enable functionalities) the POW R2 watchdog kicks is.. If I leave the WIFI network alone... it runs fine for at least 6 days...

grovkillen · #70 Post by **grovkillen** » 20 Sep 2018, 20:39

We really need to test how different WiFi environments is working with our firmware. We suspect that it has more impact on the system then previously thought.

A great deal is happening behind the scenes now that we're turning this initiative into a company but we hope to pick up the speed soon.

Who is online