Error compiling 1.9.0b2 - gulp related? #173
Comments
|
hi @higgers, it's been a while! The problem is you're building the |
|
I had the same Problem. |
|
guys, I explained it all in https://github.com/proddy/EMS-ESP/blob/dev/CHANGELOG.md. |
|
I'd installed nodejs but hadn't read the first line that states your have to build the debug build. I clearly can't read properly! Thanks for your patience, Proddy. I've successfully built the code, flashed it to the wemos but I don't see the EMS-AP access point. When I power up the board there's a brief single flash of the LED then nothing. I've tried holding down the reset pin and then applying power and when I let go of the pin I see the same brief flash and then nothing else. I vaguely remember there's a command to erase the SPIFFS and effectively start from scratch but I can't remember how to do it. I'll go back and check issue #23 because I think the command was mentioned in there. |
|
"pio run -t erase"? |
|
thats the one. Which version did you upgrade from? I did test going from 1.8.1 to 1.9.0 and it seemed to work. |
|
I upgraded from 1.8.3. I tried running "pio run -t erase" and then flashed the firmware via a USB cable. The flash process then seems to run fine, I can see the ASCII progress bars count up to 100% but I just can't see the EMS-AP access point. I've tried scanning for it on my laptop and my phone. Should the LED on the wemos be flashing constantly when it's in access point mode? Or should it do the single flash that I'm seeing? |
|
the LED will flash quickly on reboot and then either a slow pulse if serial is enabled or the EMS bus can't be reached or solid if it has a connection to the BUS. I noticed sometimes after a firmware the soft reset (RST) platformio does is not always enough to get it going. Try tapping the small reset button on the ESP and see if that helps. You should see an AP called ems-esp. If that doesn't work, go to platformio.ini and use |
|
Great advice, thanks, I can what's happening now. The board keeps restarting every 3 seconds. THis is the output in the monitor: |
|
This appears to be related to the watchdog reset. |
|
oh dear. Someone else reported this problem too. I'll see if I can reproduce it. Perhaps do another 'pio run -t erase' and try again. just to be sure... |
|
I've tried that a few times with the same result. I must be doing something wrong/differently to you. I've just unzipped the source to a new folder in order to start from scratch and I'm getting those compilation errors for the files in the webh directory again. I have node.js installed, and it's on the path. I've tested this by opening a command prompt and typing "node". I then navigated to the webfilesbuilder directory, ran "npm install --global gulp-cli" and "npm install gulp" which both ran successfully, though there 7 warnings from the "npm install gulp" command. I then run "gulp" and receive a "The app you're trying to install isn't a Microsoft-verified app" pop. I click on "Install anyway" and then get a Windows Script Host error popup saying there's a syntax error in gulp.js on line 7 character 16. Line 7 character 16 is a right angle bracket: There's also a very helpful error code: 899A03EA. Any ideas? |
|
Well, that worked: And look at that! 4 successful write requests!!! Is there any way to see which write requests were successful? That number doesn't seem to be increasing above 4. What commands would you recommend I run? I tried "autodetect deep" but it didn't seem to find anything. The boiler is a Worcester-Bosch Highflow 550CDi and I've also installed a Bosch Easy Connect CT 200 thermostat. |
|
BTW, that web frontend is absolutely brilliant, that's some good work! |
|
For building the web if node can't find the gulp module just type As for Tx not working, that sucks as I was hoping the new txmode2 code would work on all boiler types. Back with 1.8.3 which tx_mode setting where you using? |
|
What does ‚log j‘ show?
Sent by mobile device
… Am 18.08.2019 um 21:45 schrieb Paul ***@***.***>:
For building the web if node can't find the gulp module just type node .\node_modules\gulp\bin\gulp.js in the webfilesbuilder directory and it should be it. The errors you see when installing gulp is normal and because I've used an older version of the gulp syntax, but you can safely ignore them.
As for Tx not working, that sucks as I was hoping the new txmode2 code would work on all boiler types. Back with 1.8.3 which tx_mode setting where you using?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
an excerpt from log j from 1.9.0b2: Is that enough or would you like to see more? Will try 1.8.3 tx_mode shortly. |
|
An autodetect or some write command would be interresting to see whats going on...
Sent by mobile device
… Am 18.08.2019 um 22:10 schrieb higgers ***@***.***>:
an excerpt from log j from 1.9.0b2:
(01:01:10.285) ems_parseTelegram: 00 01: 10
(01:01:10.316) ems_parseTelegram: 00 01: 18
(01:01:10.321) ems_parseTelegram: 00 01: 98
(01:01:10.348) ems_parseTelegram: 00 01: 11
(01:01:10.379) ems_parseTelegram: 00 01: 12
(01:01:10.410) ems_parseTelegram: 00 01: 18
(01:01:10.415) ems_parseTelegram: 00 01: 98
(01:01:10.441) ems_parseTelegram: 00 01: 13
(01:01:10.479) ems_parseTelegram: 00 01: 18
(01:01:10.484) ems_parseTelegram: 00 01: 98
(01:01:10.503) ems_parseTelegram: 00 01: 14
(01:01:10.535) ems_parseTelegram: 00 01: 15
(01:01:10.566) ems_parseTelegram: 00 01: 18
(01:01:10.571) ems_parseTelegram: 00 01: 98
(01:01:10.597) ems_parseTelegram: 00 01: 16
(01:01:10.629) ems_parseTelegram: 00 01: 17
(01:01:10.659) ems_parseTelegram: 00 01: 18
(01:01:10.665) ems_parseTelegram: 00 01: 98
(01:01:10.691) ems_parseTelegram: 00 01: 20
(01:01:10.728) ems_parseTelegram: 00 01: 18
(01:01:10.734) ems_parseTelegram: 00 01: 98
(01:01:10.753) ems_parseTelegram: 00 01: 28
(01:01:10.785) ems_parseTelegram: 00 01: 30
(01:01:10.816) ems_parseTelegram: 00 01: 18
(01:01:10.821) ems_parseTelegram: 00 01: 98
(01:01:10.847) ems_parseTelegram: 00 01: 38
(01:01:10.878) ems_parseTelegram: 00 01: 40
(01:01:10.909) ems_parseTelegram: 00 01: 18
(01:01:10.915) ems_parseTelegram: 00 01: 98
(01:01:10.941) ems_parseTelegram: 00 01: 48
(01:01:10.979) ems_parseTelegram: 00 01: 50
(01:01:11.034) ems_parseTelegram: 00 01: 18
(01:01:11.040) ems_parseTelegram: 00 01: 98
(01:01:11.071) ems_parseTelegram: 00 01: 88 13 05 22 00 80
(01:01:11.072) 0x08 -> 0x13, type 0x05, telegram: 88 13 05 22 00 (CRC=80) #data=1
l(01:01:11.380) ems_parseTelegram: 00 01: 88 00 18 00 33 02 36 64 23 0A 31 65 40 01 FD 80 00 80 00 FF FF FF 00 00 00 00 2D 02 38 91
(01:01:11.381) 0x08 -> all, type 0x18, telegram: 88 00 18 00 33 02 36 64 23 0A 31 65 40 01 FD 80 00 80 00 FF FF FF 00 00 00 00 2D 02 38 (CRC=91) #data=25
og(01:01:11.620) ems_parseTelegram: 00 01: 88 00 34 00 33 01 FD 80 00 A8 00 00 01 2B 01 C5 3F 00 04 7D 00 2E
(01:01:11.621) 0x08 -> all, type 0x34, telegram: 88 00 34 00 33 01 FD 80 00 A8 00 00 01 2B 01 C5 3F 00 04 7D 00 (CRC=2E) #data=17
(01:01:11.815) ems_parseTelegram: 00 01: 58
(01:01:11.846) ems_parseTelegram: 00 01: 18
(01:01:11.852) ems_parseTelegram: 00 01: 98
n(01:01:11.877) ems_parseTelegram: 00 01: 60
(01:01:11.909) ems_parseTelegram: 00 01: 68
(01:01:11.939) ems_parseTelegram: 00 01: 18
(01:01:11.945) ems_parseTelegram: 00 01: 98
(01:01:11.978) ems_parseTelegram: 00 01: 0A
(01:01:12.034) ems_parseTelegram: 00 01: 0B
(01:01:12.064) ems_parseTelegram: 00 01: 18
(01:01:12.070) ems_parseTelegram: 00 01: 98
(01:01:12.096) ems_parseTelegram: 00 01: 0C
(01:01:12.127) ems_parseTelegram: 00 01: 18
(01:01:12.133) ems_parseTelegram: 00 01: 98
(01:01:12.158) ems_parseTelegram: 00 01: 0D
(01:01:12.190) ems_parseTelegram: 00 01: 0E
(01:01:12.227) ems_parseTelegram: 00 01: 18
(01:01:12.233) ems_parseTelegram: 00 01: 98
(01:01:12.252) ems_parseTelegram: 00 01: 0F
(01:01:12.283) ems_parseTelegram: 00 01: 10
(01:01:12.314) ems_parseTelegram: 00 01: 18
(01:01:12.320) ems_parseTelegram: 00 01: 98
(01:01:12.346) ems_parseTelegram: 00 01: 11
(01:01:12.377) ems_parseTelegram: 00 01: 12
(01:01:12.408) ems_parseTelegram: 00 01: 18
(01:01:12.413) ems_parseTelegram: 00 01: 98
(01:01:12.439) ems_parseTelegram: 00 01: 13
Is that enough or would you like to see more? Will try 1.8.3 tx_mode shortly.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
I wasn't sure exactly what sort of logging you want to see during the autodetect. I initially set log to raw and then set log to verbose. Let me know if you want me to run some more commands... |
|
don't think Tx is working. Looks like there are polls. Would be good if you could find out which tx_mode setting worked for you in 1.8.x |
|
Wow!!! I flashed 1.8.4 and as soon as I set the tx_mode to 2 it detected the thermostat: |
|
ok, that's good news. the new Tx code in 1.9.x is basically @susisstrolch's "tx_mode 2" implementation from 1.8.x but super charged. I'm surprised it doesn't work. Need to think more about it tomorrow. Thanks for testing though. |
|
No problem, just let me know if you want me to test anything else. I've been having a play around and have set up MQTT again and noticed that the thermostat temperature data on the info section of the telnet connection is wrong: The Version is correct, the version number I see on the Bosch Easy Connect app on the "Main firmware version" is 02.06.00. I can't see a ProductID field anywhere on the app. The current room temperature on the app is 24 degrees and the set point is 29 degrees but they're both 0.0C in the telnet info data. Here's a set of the requested data telegrams: Should the thermostat current temperature and setpoint be somewhere amongst those telegrams? |
|
Actually, now that I've recovered from the excitement of seeing tx_mode 2 working I've remembered that I don't need to write values to the thermostat. My goal is to be able to set the boiler flow temperature in order to achieve weather and load compensation. I.e., when it's very cold outside or there's a large load on the heating system I want to be able to set a high flow temperature to compensate for this. I have wireless thermostat radiator valve controllers on (nearly) all the radiators in the house that report the percentage open of the valves so my home automation system (openHAB) can track the load on the heating system. What I need to do now is being able to set the flow temperature. It would be nice to be able to read the return temperature too but that's not crucial, I could glue a temperature probe onto the return pipe to deal with that. So, in summary, and I realise I'm way off the original topic of this issue, do you know of anyone who has successfully set the flow temperature on a "Bosch Condens 2500/Junkers Heatronics3 (ProductID:95 Version:25.02)"? I've set up MQTT on my openHAB system to set the flow temp and I can see success messages in the MQTT log but I don't see the flow temperature being updated in the telnet session. I haven't had time to investigate whether the MQTT send is fire and forget or if the ESP sends a success/fail confirmation back to openHAB and I'm going away for a week now. Arrrrgh! :) |
|
MQTT is fire and forget. The set flow temp works for Buderus and it should be possible to make it work for Junkers too if someone wants to reverse engineer that other python HT3 project. There are a few people on the forum that understand this better than I do. Perhaps open a separate github issue and I'll connect with the right contributors. As for reading the temps from your Easy thermostat, we do a request to telegram 0x0A and the current temperatures is byte 8+9 of the data block and the setpoint are bytes 10+11. There are 2-byte short integers multiplied by 10. But in your case all the values are zero. No idea why I'm afraid. enjoy your holiday! |
|
One more thing
You need Tx working also for Read operations. When EMS-ESP boots up it sends out a few Tx commands to figure out what EMS devices are attached. |
|
What is this other python HT3 project? Sounds interesting. One of the features of the Bosch Easy Control is that as you turn up the room set point it raises the boiler flow temperature. Hopefully, if I spend some time changing the room set point on the Easy Control and capture the log I'll be able to see which telegram the thermostat sends to the boiler to change the flow temp. I'll open a feature request. Thanks for all your help again! :) |
|
And I recall now there were issues with the Bosch Easy. See #45. Perhaps we can pick-up off that topic and work on it together. |
|
@DarthMob sure, but the should be same right? If I look at PIO its the same eagle config. I'll add one to the Release page anyway. Remind me, what issues are you having again? |
|
ah ok haven't tried the binary yet - will do and report. i have the same issue as higgers (reboots on Tx enabled - since 1.8) |
|
I’m actually away for a while so wont be able to upload the firmware until
mid next week. unless you want to have a go and trying to build yourself?
…On Thu, 22 Aug 2019 at 22:43, DarthMob ***@***.***> wrote:
ah ok haven't tried the binary yet - will do and report.
i have the same issue as higgers (reboots on Tx enabled - since 1.8)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#173>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJMO6CHCG4W3EIJR76O7L3QF3255ANCNFSM4IMSTUTA>
.
|
|
no worries, last night i tested different builds and configurations. all other pre- or selfmade builds from 1.8 to 1.9.0b4 either go into reboot loop or with "listen mode on" do not recognize my thermostat and SM50 Module (also tried with the different tx_mode configurations). sorry i cannot narrow it down currently what seems to be the core problem... |
|
And if you take a prebuilt firmware of 1.9beta from the github releases page does it work ? That will rule out and environmental side effects. You could compare the sizes of the two .bin files. |
|
I testet also all the pre-built firmwares inkl. 1.9 beta (size is same as my own build) - no luck :( |
|
that is strange. Try:
|
|
@DarthMob : Which specific ESP module is on you board? Try out a different ESP/dev board to see if its not a hardware problem. |
|
Thats good advice @bbqkees - i actually used a Do-It.am board for the tests. will try on a different board and report back! |
|
So I tested 1.9.0 with a spare DO-IT.am module and although the upload is succesful, the web interface doesn't work at all or only extremely slow. And constant reboots. NOT OK: OK: |
|
would be interesting in comparing both with -DFORCE_SERIAL which disables
the UART
…On Fri, Sep 6, 2019 at 11:51 AM Kees ***@***.***> wrote:
So I tested 1.9.0 with a spare DO-IT.am module and although the upload is
succesful, the web interface doesn't work at all or only extremely slow.
And constant reboots.
The same build on the general Wemos clone with the Espressif logo on it
works fine.
NOT OK:
[image: DO-IT.AM]
<https://camo.githubusercontent.com/1fb2dc7fbeda76d9473c54e4d3a31e9343e00c14/687474703a2f2f686f74676f6f646965732e6e6c2f73686f702f656d732f77656d6f732d636f6d70617469626c65732f6261642d77656d6f732d636c6f6e652d646f2d69742d616d2e6a7067>
OK:
[image: espressif clone]
<https://camo.githubusercontent.com/a55368d0559e3da21b176b4f0cd39628f2373aa1/687474703a2f2f686f74676f6f646965732e6e6c2f73686f702f656d732f77656d6f732d636f6d70617469626c65732f676f6f642d77656d6f732d636c6f6e652d312e6a7067>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#173>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJMO6DX57QF3FGWM52QGB3QIIRZXANCNFSM4IMSTUTA>
.
|
|
Closing this issue as its related to compiling with gulp and resolved. A new issue will be created for those experiencing random crashes with 1.9.x |
|
@higgers can you make for me one log (raw) when central is in heating mode ? i want to see what CT200 send to boiler when heating is in progress ? Thanks in advance |
Hi again, it's higgers from issue #23 ;)
I've been following some of the issues around tx_mode2 and the revised code to read the EMS bus and have been hoping that the changes would allow telegrams to be sent to my Worcester-Bosch boiler. I've just been trying to compile 1.9.0b2 and after installing nodejs and running the commands listed in the compilation instructions have hit this compilation error:
Does anyone have any suggestions on how to resolve this?
The text was updated successfully, but these errors were encountered: