duepi_evo: Error on device update!
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 360, in _async_add_entity
await entity.async_device_update(warning=False)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 465, in async_device_update
await task
File "/config/custom_components/duepi_evo/climate.py", line 174, in async_update
data = await self.get_data(self)
File "/config/custom_components/duepi_evo/climate.py", line 129, in get_data
current_state = int(dataFromServer, 16)
ValueError: invalid literal for int() with base 16: 'HELLO*'
Owā¦hold onā¦I think I rememberā¦
The āHelloā is the welcome message the module gives during startupā¦
It should be save to ignore itā¦
(or start up HA after you started up the wifi moduleā¦)
(and you could still leave the telnet running for testing :P)
After the initial ā HELLOā does it show any other signs of communication?
@Whatsek Its communicating at @Marcel_de_Jong in Localā¦
the unit is reporting itself with āHELLOā during start up, which is not recognized by my integration, as it anticipates an esp-link (and not the original wifi module).
But besides that error, it should still pick up communications again after that welcome messageā¦(at least, it does for meš)
Yes, I know that he has a workin local connection, I am figuring out why it does not work with me. So I wanted to know if he also uses the cloud connection, as I do. I emailed Duepi, but no response yetā¦
@Whatsek They will respond (as they did with me)ā¦i asked them 2 questions, the pin layout of the connector (which i got) and an overview of the serial commands (which they refused, as it was company proprietary )
Well it used to work both remote and local, but a few months ago I connected the device to my IOT wlan and it doesnāt work remote anymore. Have not tried to fix it yet.
It looks like my unit reports that during every new session, at least it does when using telnet.
The integration doesnāt do anything after the error message (or I am looking in the wrong place)
Iāve been trying to test again once, but still lack the time to do it.
So much to do, so little time
And the USB2Wifi module I put to sale, so once I receive an offer, I do not have the possibility anymore to check.
What I did manage to observe is that the unit communicates very frequently when connected.
Have you tried to set the scan interval way lower (1 or 2 seconds)? scan_interval: 1
having an issue with your intergration, i am trying to collect locally but its giving me this error in logs,pretty sure i am using the correct ip because i got an notification from my deco saying a new device connected to the network
The ESPLink uses port 23 by default, but basically it is a telnet port (meaning you can monitor it using any telnet programš
Should look something like this:
I donāt think thatāll workā¦ This user also tried, and I never had the time to investigate it.
In the meanwhile, I sold the wifi moduleā¦so I canāt do any further testsā¦
I can only recommend to replace it with an ESP01 moduleā¦
I have provided some info in the first topic on what is needed for that
The costs for the ESP01, voltage adaptor and programmer is around ā¬8,- so that is not too much
could it also work by using the ESP programmer as a voltage regulator instead of the esp01-s adapter module? so from the programmer (with the esp01s connected) with a usb-female to the pellet stove pinout (gnd,5v,rx,rx)?
Hi, I have the same problem as you, the port is closed (I was trying to set it up from the beginning of this thread) I cantacted Duepi, and they told me that all the new delivered modules, (since 1 year maybe?) do not have a local port open anymore. Really bad news. They also didnt have an alternative. So we have to build our own board. Unfortunately I not really good with soldering, but I will try to make some time this winter to try to make one. But for the people that cant get an a local connection, this is sadly the bad newsā¦