SonOff POW R2 support

Moderators: Voyager, BertB, rtenklooster, Stuntteam, grovkillen, TD-er

Message
Author
sincze
Normal user
Posts: 23
Joined: 15 Jul 2016, 12:54

Re: SonOff POW R2 support

#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
Normal user
Posts: 16
Joined: 27 Aug 2018, 09:04

Re: SonOff POW R2 support

#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
Normal user
Posts: 23
Joined: 15 Jul 2016, 12:54

Re: SonOff POW R2 support

#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
Normal user
Posts: 16
Joined: 27 Aug 2018, 09:04

Re: SonOff POW R2 support

#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
Normal user
Posts: 23
Joined: 15 Jul 2016, 12:54

Re: SonOff POW R2 support

#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. :D and leave the interval at 10 as you discovered.

Djoe
Normal user
Posts: 16
Joined: 27 Aug 2018, 09:04

Re: SonOff POW R2 support

#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
Normal user
Posts: 1154
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: SonOff POW R2 support

#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
Normal user
Posts: 23
Joined: 15 Jul 2016, 12:54

Re: SonOff POW R2 support

#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
Normal user
Posts: 23
Joined: 15 Jul 2016, 12:54

Re: SonOff POW R2 support

#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
Normal user
Posts: 16
Joined: 27 Aug 2018, 09:04

Re: SonOff POW R2 support

#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
Normal user
Posts: 16
Joined: 27 Aug 2018, 09:04

Re: SonOff POW R2 support

#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
Normal user
Posts: 23
Joined: 15 Jul 2016, 12:54

Re: SonOff POW R2 support

#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 :D , 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. :D

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
Normal user
Posts: 1154
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: SonOff POW R2 support

#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
Normal user
Posts: 16
Joined: 27 Aug 2018, 09:04

Re: SonOff POW R2 support

#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
Normal user
Posts: 23
Joined: 15 Jul 2016, 12:54

Re: SonOff POW R2 support

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

Ota update possible from 1024 version to 4096 release?

sincze
Normal user
Posts: 23
Joined: 15 Jul 2016, 12:54

Re: SonOff POW R2 support

#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 :lol: :D
Sonoff POW R2-5-days.JPG
Sonoff POW R2-5-days.JPG (36.78 KiB) Viewed 2109 times

Djoe
Normal user
Posts: 16
Joined: 27 Aug 2018, 09:04

Re: SonOff POW R2 support

#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
Normal user
Posts: 1154
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: SonOff POW R2 support

#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
Normal user
Posts: 23
Joined: 15 Jul 2016, 12:54

Re: SonOff POW R2 support

#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...

User avatar
grovkillen
Normal user
Posts: 2240
Joined: 19 Jan 2017, 12:56
Location: Hudiksvall, Sweden
Contact:

Re: SonOff POW R2 support

#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.
ESP Easy Flasher [flash tool and wifi setup at flash time]
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Official shop: https://firstbyte.shop/
Sponsor ESP Easy, we need you :idea: :idea: :idea:

sincze
Normal user
Posts: 23
Joined: 15 Jul 2016, 12:54

Re: SonOff POW R2 support

#71 Post by sincze » 23 Sep 2018, 11:37

grovkillen wrote:
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.
Excellent, just some more things I noticed:
I've been using this ESPEasy on several devices from the reliable 1.xx versions (uptime 23908 minutes) to the latest development builds..
After reading some more about my Unifi hardware it seems that every changes where my AP's are involved will result in a restart (reboot) of the specific AP. All clients will lose communication.
- When you make a configuration change, all involved AP's will reboot. So changes have to be done outside office hours if you don't want unhappy users.
For version 1.x this does not seem to matter. (uptime 23908 minutes)
For the later ESP versions after AP reboot:

WEMOS: ESP_Easy_mega-20180606_normal_ESP8266_4096.bin -> Reset Reason Hardware Watchdog -> (201) No AP found
POW2: ESP_Easy_mega-20180723_dev_ESP8266_1024.bin -> Reset Reason Hardware Watchdog -> Last Disconnect Reason (1) Unspecified

I never noticed an error before as they just reconnect fine and continue to work.
However downside for the POW2 is that the relais switches off,and it seems I am unable to tell it to automatically go back on after a reboot.

Ah and indeed a watchdog kick in for a temporarily wifi loss... :lol: seems a bit of an overkill. Hope you guys can fix it..

sincze
Normal user
Posts: 23
Joined: 15 Jul 2016, 12:54

Re: SonOff POW R2 support

#72 Post by sincze » 03 Oct 2018, 20:14

After not touching my wifi settings and leaving them as is. that means working ;-) the ESP is still online.
Sonoff POW R2-9-days.JPG
Sonoff POW R2-9-days.JPG (23.09 KiB) Viewed 989 times
So I guess we are looking in the right direction regarding the wifi being the root cause of the watchdog resets.

Djoe
Normal user
Posts: 16
Joined: 27 Aug 2018, 09:04

Re: SonOff POW R2 support

#73 Post by Djoe » 26 Oct 2018, 08:43

Hi all,

On my side I'm in the same situation..
My pow, without changing the firmware version, have a 59165 minutes uptime...
And, or course, if I have changed a config somewhere, I don't remember what...

Have a good day !

Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests