-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Electrodragon woes #284
Comments
for the ntp issue, check what ntpserver1, ntpserver2, ntpserver3 respond. There
was a bug around that version where ntp servers became a config option, but it
wasn't stored in the flash (try with the latest version and see if you still
have a problem)
k
|
Thanks. I managed to update the device using file upload rather than web. Now running version 4.1.0 so that's good. Pleased to report that NTP now works so log entries are correctly timestamped. Poweronstate still doesn't work. I'm going to need that functionality to ensure my house fails-safe in the event WiFi, mqtt, or node-red loses the plot. Such fails tend to have a poor WAF in my experience |
please provide the output of poweronstate |
Here is the startup and status0 log. Part my fault, I've only just found the savestate command. I've now found poweronstate is honoured for channel 2 but not channel 1. Is this intended? I've turned mqtt off to ensure isolation from domoticz and node-red. Peter 00:00:00 APP: Project sonoff Electro-105 (Topic Electro-105, Fallback DVES_075369, GroupTopic electros) Version 4.1.0 |
Are you able to control the relays with power commands? Do you have a schematic of the ElectroDragon v1.5? Just tested PowerOnState with a Sonoff 4CH and it works fine: All relays are powered on. |
Curiouser, and curiouser. Toggle 1 switches relay 1, and 2 switches 2. And no, i don't have a diagram. What's odd is, when i power up the dragon, neither of the relays operate and the status 0 LED is illuminated. The web interface shows relay 2 as on as indeed does the log which you have evidenced. Subsequently, pressing the toggle 1 and 2 buttons on the web interface switches the appropriate relay. Time to break out another module methinks. I'll get back to you. Thanks for sticking with me on this. Btw. I'm confused how poweronstate and savestate interact. Which takes precedence? |
Different dragon, similar results, poweronstate is not honoured. Here's the log. 17:48:35 MQTT: Connected |
savestate off means no power state is saved. A poweronstate of toggle will therefoe never work. Suggest to leave powersave set to 1 and try again with poweronstate set to 1. You will need to remove power and reapply power for poweronstate to work; a restart only will not work. |
Sorry, forgot to include the status 0 output last time. 00:00:00 Config: Loaded configuration from flash at F7 and count 152 |
FYI A third dragon seems to exhibit the same behaviour. 00:00:02 Wifi: Checking connection... |
And another 00:00:03 mDNS: Initialized |
And now with a power cycle instead of a restart as I noticed e few answers ago... |
Btw i only ever power cycle the devices, never restart when doing these tests for you. Peter |
Well as long as INFO3 returns the wrong message it will never work in your case. Power off. Wait a minute and power on again. You should see a message like:
|
Aha! Might not have been giving the units enough time to power reset. That said, the unit seems to go through the reset process. I'll try again when i get home. |
Here is the log having switched off the unit for a few minutes. What message should i be expecting info 3? 00:00:00 Wifi: Connecting to AP1 Police-Surveillance-CAM-1 in mode 11N as dragon-103-0088... |
See my previous answer info3. Weird it still responds with external system... |
Sorry, misread! Don't think I've ever seen a power on type message when using electrodragons. I'll try with my sonoff just to see what i should be expecting. Sorry this is dragging on. |
Ok. Just tried with dragon that i had loaded your software onto a week ago. Looked at the console l log and found that it reported "started external system". Seems to me that version 1.5 of the dragons don't correctly report how they've been powered up. Perhaps someone with earlier versions of these devices can report their experiences. All 5 of my rev 1.5 dragons seem to behave the same way Thanks again for your patience. Btw. Want to save more memory? Consider getting rid of the "configure other" menu and either the upload or update command. |
Can you tell me the criteria the dragons use to determine how they've been started up. I don't understand what "started external system" means anyway, please enlighten! |
What does"started external system" mean? How do you differentiate between the various startup modes? Regards |
I rely on the Arduino-ESP8266 library which in turn relies on the Espressif provided SDK. The SDK should respond with the correct reboot status but for some reason fails to detect a power cycle on your ElectroDragon. There were issues with previous SDK's as can be found on the issues page of the Arduino-ESP8266 library but they should have been solved for the current used SDK 1.5.3. |
Presumably I'm neither the first nor the last to encounter this issue so the SDK will get fixed in the fullness of time. Thanks for your patience. Issue gotta stay open i guess. Peter |
Hi, a couple of things: Thanks again, Peter |
On Sat, 15 Apr 2017, CommodoreWhite wrote:
1 I've found the code that implements poweronstate. What's the smallest change you'd recommend to force my dragons to always power-up in an On state,
you should not need to make any code changes, you should be able to just set the
poweronstate in the config.
|
... except that the poweronstate setting depends on the cpu returning "power on" as the reset reason. for some reason my dragons return "external system" so poweronstate is never actioned. c.f.
Regards |
Right! I've successfully used platform.io in Windows to upload TASMOTA to my electrodragon switch. I'd hoped it was both the first and last time because a) I found the programming environment confusing, and b) you provide firmware.bin files which I've since used to upgrade my dragons using the web interface. I'd like to create my own firmware.bin file, but can't figure the magic commands. A clue would be appreciated. |
firmware.bin is created by the platformio build process. Using the arduino IDE it build the fle sonoff.ino.bin instead. go through the "getting started" pages in order. I'm closing this issue as it's now not electrodragon related. open another issue if you continue to have build problems (and if the docs are confusing, please help us make them better once you figure out how things work) |
it sort of is electrodragon related because i wouldn't have had to do any
of this if my dragons produced the correct message at startup as you have
seen in the logs. Nevertheless, happy to close the issue since the problem
doesn't seem to be with your code.
Peter
On 23 Apr 2017 12:14, "David Lang" <notifications@github.com> wrote:
firmware.bin is created by the platformio build process. Using the arduino
IDE it build the fle sonoff.ino.bin instead. go through the "getting
started" pages in order.
I'm closing this issue as it's now not electrodragon related. open another
issue if you continue to have build problems (and if the docs are
confusing, please help us make them better once you figure out how things
work)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#284 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFyj0bujuJxDWH2cUsMvGvR0X-zfd2IJks5ryzJ7gaJpZM4MpGrm>
.
|
Yep. The time problem vanished on later versions of tasmota. Thanks.
…On 25 Mar 2017 15:29, "David Lang" ***@***.***> wrote:
for the ntp issue, check what ntpserver1, ntpserver2, ntpserver3 respond.
There
was a bug around that version where ntp servers became a config option,
but it
wasn't stored in the flash (try with the latest version and see if you
still
have a problem)
k
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#284 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFyj0Xu5MCszWtBSzQpqR6-85x8uE2qCks5rpTLxgaJpZM4MpGrm>
.
|
Will test for "External System" too when powered on in next version |
5.0.1 20170429 * Adjust Sonoff SC messages to prepare for display feature * Move static data from RAM to Flash * Fix PowerOnState for some devices not reporting "Power on" state (arendst#284, arendst#380, arendst#383)
I have several issues with my v1.5 version of the electrodragon dual switch running 4.0.5. of this
splendid software which i compiled and uploaded using programming.io. I'm hoping if i list them someone might identify what I've done wrong.
I've successfully updated a sonoff basic using smadds web site. If i go through the same process on my electrodragon, nothing happens
The NTP service doesn't work, timestamps are based on the Unix epoch
Poweronstate doesn't work. I've switched off my mqtt service to ensure it doesn't get involved. I set poweronstate to ON and cycle the device but it stubbornly stays off, my sonoff basic works fine. The command shows the parameter as stored correctly.
Help would be appreciated.
The text was updated successfully, but these errors were encountered: