ESP reboots after connecting to Generic HTTP controller

[rvakkeren]

Steps to reproduce

When using a Generic HTTP controller instead of Domoticz controller

Actual behavior

I want to use the Generic HTTP controller instead of the Domoticz controller. But everytime the ESP wants to connect to the raspberry (via the generic http controller), it reboots. Disabling the controller solves this problem, but the data won't be sent.

System configuration

Hardware: ESP 12-F, MH-Z19 Software or git version: Mega branch

[psy0rz]

can you try again with the latest git-checkout? are you using generic http or generic http advanced?

which version did you test?

[rvakkeren]

Yesterday, I cloned the version and made a build, using PlatformIO,

Build: 20000 Version: ESP Easy Mega

[thymjan]

Same behavior with FHEM. But it depends on the configured devices. Did you test it without any configured device?

[rvakkeren]

Yup... I can set thecontroller ánd/or device enabled. But as soon as I enable the controller at the device section, it´ll reboot as soon as it tries to connect.

[psy0rz]

then we might just broke stuff.. can you try again with the official dev7 release?

[rvakkeren]

will try that tonight, keep you posted.

On Thu, Apr 20, 2017 at 2:05 PM, DatuX notifications@github.com wrote:

then we might just broke stuff.. can you try again with the official dev7 release?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/letscontrolit/ESPEasy/issues/239#issuecomment-295708616, or mute the thread https://github.com/notifications/unsubscribe-auth/AP2BG0qF4JmWcOTKkm0egvZTHscmYTMoks5rx0oNgaJpZM4NCxb_ .

[thymjan]

I can confirm that interfacing with FHEM is working with the official dev7 release. With the actual (today) cloned version it does not (also tested with just one enabled system "load" device). ESPEasy crashes after enabling the transfer and loops with booting after receiving the first event. bootloop.txt

[rvakkeren]

Hmm, for some reason, Atom freezes when I try to compile the dev7 release...

On Thu, Apr 20, 2017 at 9:40 PM, Stefan Theurer notifications@github.com wrote:

I can confirm that interfacing with FHEM is working with the official dev7 release. With the actual (today) cloned version it does not (also tested with just one enabled system "load" device). ESPEasy crashes after enabling the transfer and loops with booting after receiving the first event. bootloop.txt https://github.com/letscontrolit/ESPEasy/files/945272/bootloop.txt

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/letscontrolit/ESPEasy/issues/239#issuecomment-295875138, or mute the thread https://github.com/notifications/unsubscribe-auth/AP2BG-skN_Dl9ccJL81Z3ZodmBN9QY0Gks5rx7SWgaJpZM4NCxb_ .

[thymjan]

You don't have to compile dev7 yourself, just get it compiled here: https://github.com/letscontrolit/ESPEasy/releases (you hopefully have a windows 10 machine?)

[rvakkeren]

That one doesn't have the NDIR CO2 sensor in it...

On Thu, Apr 20, 2017 at 11:11 PM, Stefan Theurer notifications@github.com wrote:

You don't have to compile dev7 yourself, just get it compiled here: https://github.com/letscontrolit/ESPEasy/releases (you hopefully have a windows 10 machine?)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/letscontrolit/ESPEasy/issues/239#issuecomment-295915399, or mute the thread https://github.com/notifications/unsubscribe-auth/AP2BGx0oeHbiq6NcJhQEFh5iTh2M1rLUks5rx8oUgaJpZM4NCxb_ .

[thymjan]

Just give it a try without the special sensor. Upload firmware dev7. Define a device like system uptime. Start your http controller. This should work. Then go back to the actual version, do the same. I'll expect the controller will not work with just this simple unique device. That's the thing to find out. If this should work, than try this with your special sensor.

[psy0rz]

fixed