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
ESP12E or Wemos PRO min reboots when pressing the button of adjustment of a cold-warm luminescence from the FUT089 panel #297
Comments
What version are you using? |
Good afternoon! I tried esp8266_milight_hub-1.7.0, esp8266_milight_hub-1.7.1, esp8266_milight_hub-1.8.0. Only this button freezes up. |
from a web of the interface and team on MQTT are fulfilled! Everything is normal! hangs at reception of team from the panel. When pressing the slider |
#include <GDBStub.h> Linking .pioenvs\nodemcuv2\firmware.elf |
How to catch a mistake? |
What are you trying to do here? Are you adding libraries? Sounds like the compiled firmware won't fit. There's not really anything you can do except trim down the code. |
No! I try in any ways to find a mistake which leads to lag. |
I tried to connect debugging. Nothing good left. |
Thanks for the video. I'm having a hard time reproducing this. I tried:
I don't have a physical FUT089 remote, unfortunately. Could you:
We can decode the stacktrace with this. Have you already tried a pre-compiled binary? https://github.com/sidoh/esp8266_milight_hub/releases/tag/1.7.1 |
Have you already tried a pre-compiled binary? I haven't understood a little what needs to be made with firmware.elf |
Initial codes of working decoding. I don't know a source. new video It can do as be to help? |
Kind to you time of day! And if to buy you the panel given fut089! Will you be able to correct these lags? I am ready to send money for PayPal for his purchase. ))) |
I found! the file - FUT089PacketFormatter.cpp
in the procedure BulbId FUT089PacketFormatter::parsePacket(const uint8_t *packet, JsonObject& result) { V2RFEncoding::decodeV2Packet(packetCopy); BulbId bulbId( uint8_t command = (packetCopy[V2_COMMAND_INDEX] & 0x7F); if (command == FUT089_ON) { !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! } else if (command == FUT089_MODE) { |
I will write result on video soon ))))) |
I just ordered a FUT089, but will take a few weeks to get here from China.
Just a heads up -- it'll probably be a few days between responses. |
And just to be clear, running with the firmware above, please provide a stacktrace like you did in your original post on this issue ( |
The file loaded your bin. The first start of an error did not give out! Subsequent give an error message. That is there are moments when your algorithm works. But in a few minutes 1-3 also I began to reboot. $⸮⸮�⸮8⸮⸮⸮*WM: Setup complete (version 1.7.1) Exception (28): ctx: cont
Setup complete (version 1.7.1) |
After long search I it solved problems. As wrote above where a problem. |
Hey @vsv78vrn, just had time to watch your video. This is super helpful. Thanks for finding the line causing the crash. |
Good luck and progress to you in your project! Excellent project! I will help further you with development of this project))) |
Got the remote, and was able to reproduce the issue. Pretty strange that it doesn't come up with iBox. Don't have time to dig into what's going on right now, but hopefully will over the next couple of days. |
@vsv78vrn -- will be fixed in 1.8.0-dev2. |
The problem was There are probably two fixes here:
I feel that (2) is the preferable option here, but the patch is (3) because it's the easiest. @cmidgley do you recall why we removed https://github.com/sidoh/esp8266_milight_hub/pull/227/files#diff-38661d39e1320654e10bcf3aa2871ab1L49 |
I believe the answer is that we moved stateStore from a property of the method to become a property of the object. So "stateStore" is still available, just no longer passed in. Is this what you are asking? |
Yeah, just wondering why we decided to make the change. The issue with passing it in is that it's possible for it to be unset. There's no compile-time guarantee that the appropriate method to set it has been called. I think that's more error prone than explicitly passing it in either in the constructor, or in the methods that need access to it. The bug described in this ticket happened because I think it'd be difficult to pass them into the constructor right now. Would basically have to layer things in factories. So passing it into the methods is probably easier. Just wondering if there was a reason we removed it other than saving callers the effort of passing it in. |
It was a case of having to hack it into a large number of methods to get it passed "low enough" where it was needed. Rather than changing a ton of method signatures just to pass it down, I thought it was cleaner to make it a property. An alternative might be to switch it to be a reference to another object that we can query to get state, and use it as a state container. Just an idea. |
Thanks Chris! That helps me understand. :) |
Just noticed this as well with my FUT089 and NODEMCUv2 (official latest release). Now i noticed that color_temp isnt working and the remote stops working for a few seconds if i try to change it. (Thats when it reboots i guess) Anyway, thanks for fixing the problem ! |
Radio is available
Packet received: 909C9ECF41DEBF724163Packet transformed: 093979F3827BFD4E82C6Failed CRC: expected 33540, got 33478
Radio is available
Packet received: 909C9ECF41DEBF724163Packet transformed: 093979F3827BFD4E82C6Failed CRC: expected 33540, got 33478
Radio is available
Packet received: 909C9ECF41DEBF724163ADB3Packet transformed: 093979F3827BFD4E82C6B5CDSuccessfully parsed packet of length 10
Received packet (len = 10)!
NRF24MiLightRadio - received packet!
NRF24MiLightRadio - Checking packet length (expecting 10, is 10)
Packet id: 14790
Exception (28):
epc1=0x40218dd3 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000008 depc=0x00000000
ctx: cont
sp: 3fff1eb0 end: 3fff2320 offset: 01a0
ets Jan 8 2013,rst cause:2, boot mode:(3,6)
load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v614f7c32
~ld
MqttClient - Connecting to: m20.cloudmqtt.com:18217
MqttClient - connecting
MqttClient - subscribing to topic: milight/+/+/+
MqttClient - Successfully connected to MQTT server
*WM:
*WM: AutoConnect
*WM: Connecting as wifi client...
*WM: Already connected. Bailing out.
*WM: IP Address:
*WM: 192.168.1.182
Wifi connected succesfully
Setup complete (version UNKNOWN)
The text was updated successfully, but these errors were encountered: