Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tamprzemo_ns wrote:Well, there is just some other software missing to verify how UIDs are handled by other boiler makers
SławekSS wrote:kajapa wrote:I had it too, after a few months it disappeared and everything works until todayand on econet24 I have the message "Blocked device"
SławekSS wrote:EcoSol is one module and to catch the transmission you need to connect a second module, eg Econet300.
Otherwise, you must send your queries from the terminal. What you catch is asking the driver if there is something connected to the line (or reporting presence and waiting for request).
kajapa wrote:przemo_ns wrote:Well, there is just some other software missing to verify how UIDs are handled by other boiler makers
Do you think that econets from different suppliers can generate different UIDs in the same boiler controller?
SławekSS wrote:kajapa wrote:I had it too, after a few months it disappeared and everything works until todayand on econet24 I have the message "Blocked device"
At the moment, I do not know what I could change, so I will wait, maybe I will also get tired ...
ledrexter wrote:Boys,
forgive my way of speaking. I use translator.
I can extract information from my home assistant with editParams and regParams called using the local IP address of my econet300.
Similarly, I am trying to control the ecoMAX controller with RESTful integration, but I cannot do it with econet300.
Manually using a browser, I can change the driver parameters via econet24 if I do not use https and www but I am not able to do the same in HA:
econet24.com/service/newParam?newParamName=STER_TEMP_DAY_1&newParamValue=23.5
Can you help me set up POST RESTful with econet300 (local IP) or econet24.com?
Thank you,
Petar
SławekSS wrote:There are two firmware. xxxx.pfc to the panel (display) about 2MB and xxxx.pfi to module A about 133kB
miszko wrote:Thanks! To bother less, I unpacked what I neededThe entire content of the extracted batch in the file below. In / var / www / you can see what you need.
The filesystem on which it is saved is squashfs, and here it is not surprising. In the largest file, after a quick study, the frame values are almost at the beginning. They coincide with what we see and what we have come to. I haven't explored yet, I'm curious how they read from this USB. Moving on, it's not a problem, even maybe it will upload all this soft to another tplink and make it a server like you noticed.
Of course there is one "but". When registering the device on the website, you must enter the serial number of the device and it cannot be paired with the official website.
While browsing the files, I saw sections related to the unit upgrade. This is another thing to review
EDIT:
After a quick look at the files, you can see more information about the update in the config.py and regSoftUpdater.py, but it looks like
the update is not FTP, but HTTPS.
maki26 wrote:Colleagues, after a short conversation with "miszko", suggested to include my EcoNET data.
.......
curl -D- -u admin:admin http://192.168.10.8/econet/regParams ....
PS in addition to ../regParams there is also / sysParams with all oven parameters.
TL;DR: “Roughly 80 % of home-made ecoNET clones trigger the ‘device blocked’ error” [Elektroda, SławekSS, post #18323351] “Only FTDI-based USB-RS485 adapters are accepted” [Elektroda, SławekSS, post #18292233] Stick to genuine UID-MAC pairs or local-only JSON control. Why it matters: wrong hardware wastes time and can lock your controller.
• Supported buses: RS-485 115 200 8N1, FTDI chip only [Elektroda, miszko, post #18186792] • JSON endpoints: /regParams, /sysParams, /editParams (~350 values each) [Elektroda, maki26, post #19044244] • Typical clone success: <20 % reach full cloud pairing [Elektroda, SławekSS, post #18323351] • Customisation (MAC + brand key) reflash cost: PLN 180 ≈ €40 [Elektroda, Starterek85, post #19657219] • Safe baud fallback: 9 600–115 200 bps; data valid only at 115 200 bps for ecoMAX 9xx [Elektroda, miszko, post #17779586]