Failed connect sonoff touch


#1

Sonoff T1 2CH Modul
Tasmota Version 6.4.1(sonoff)
Build-Datum & -Uhrzeit 2018.12.24 14:55:04
Core-/SDK-Version 2_4_2/2.2.1(cfd48f3)

Error Message:
Feb 14 20:02:18 nymea nymead[652]: I | JsonRpc: Invoking method “Devices” AddConfiguredDevice
Feb 14 20:02:18 nymea nymead[652]: I | Mqtt: Suitable MQTT server for “192.168.2.150” found at “192.168.2.123” on port 1883
Feb 14 20:02:18 nymea nymead[652]: I | Mqtt: Policy for client “c96635f0a4e9474f9e633dca583c8d49” added.
Feb 14 20:02:18 nymea nymead[652]: I | Tasmota: Sonoff device setup call failed: QNetworkReply::NetworkError(UnknownNetworkError) “Network unreachable” “”
Feb 14 20:02:18 nymea nymead[652]: I | Mqtt: Policy for client “c96635f0a4e9474f9e633dca583c8d49” removed
Feb 14 20:02:18 nymea nymead[652]: I | Mqtt: Released MQTT channel for client ID “c96635f0a4e9474f9e633dca583c8d49”
Feb 14 20:02:18 nymea nymead[652]: #033[33m W | DeviceManager: “Error in device setup. Device sonoff_dual ({c96635f0-a4e9-474f-9e63-3dca583c8d49}) will not be added to the configured devices.”#033[0m
Feb 14 20:02:18 nymea nymead[652]: I | JsonRpc: Got a device setup finished “sonoff_dual” QUuid("{c96635f0-a4e9-474f-9e63-3dca583c8d49}")

Can anybody help me?


#2

Hi chris!

Using your log I’ve read through the code and I’ve found a bug in the code which explains your issue. Thanks a lot for reporting this.

The Tasmota support is still new in nymea. I appreciate your efforts in reporting this. I have fixed the issue and it is currently in review and being built by the CI system. The next release will have the fix included.

If you want, you can can upgrade your nymea installation to the pre-release from the CI system and give it a test:

sudo apt-add-repository "deb http://ci-repo.nymea.io/landing-silo stretch main"
sudo apt-get update && apt-get upgrade

Note: Replace “strech” with xenial or bionic, depending on what Debian/Ubuntu you are running the core. If you installed from the snap package, you can switch to the edge channel to get the pre-release.

Please report back if this fixes your issue.

Best regards,
Michael


#3

Same issue. Same Log

0.11.1+201902112353~105e2ae~stretch


#4

Seems you didn’t get the update. There is a timestamp in the version number. Should be at least:

nymead:
0.11.1+201902151525~e7d0e34~stretch

nymea-plugin-tasmota:
0.10.3+201902151533~4266594~stretch

Perhaps you need to sudo apt-get dist-upgrade

You can check available versions with apt-cache policy nymea and apt-cache policy nymea-plugin-tasmota

For example:

nymea@nymea:~$ apt-cache policy nymead
nymead:
  Installed: 0.11.1+201902151525~e7d0e34~stretch
  Candidate: 0.11.1+201902151525~e7d0e34~stretch
  Version table:
 *** 0.11.1+201902151525~e7d0e34~stretch 500
        500 http://ci-repo.nymea.io/landing-silo stretch/main armhf Packages
        100 /var/lib/dpkg/status
     0.11.0+201901171613~a49a1e6~stretch 500
        500 http://repository.nymea.io stretch/main armhf Packages
     0.9.38+201811051604~bdbc11c~stretch 500
        500 http://ci-repo.nymea.io/fix-networkdetector-scan stretch/main armhf Packages

Make sure you added the “landing-silo” correctly.


#5
W | DeviceManager: "Error in device setup. Device sonoff_dual ({d0388d50-afd9-4489-be92-027edff42c88}) will not be added to the configured devices."
 W | DeviceManager: "Error in device setup. Device Test ({c51eda2a-4ec1-48e3-b7c6-2902cc2df81a}) will not be added to the configured devices."

nymea-plugin-tasmota:
Installed: 0.10.3+201902151859~8112c9d~stretch
Candidate: 0.10.3+201902151859~8112c9d~stretch

nymea:
Installed: 0.11.1+201902151854~ff61548~stretch
Candidate: 0.11.1+201902151854~ff61548~stretch

I | Tasmota: Sonoff device setup call failed: QNetworkReply::NetworkError(ContentNotFoundError) “Error transferring http://192.168.2.150/sv?w=2%2C1&mh=192.168.2.245&ml=1883&mc=29d394a0bae0463fa195512cee85a8c2&mu=79a01ba6fca44d53bc3e92c605462698&mp=52fc003bbfb94e8da5e750d172660ad8&mt=sonoff&mf=29d394a0bae0463fa195512cee85a8c2/%topic%/ - server replied: Not Found” “Datei nicht gefunden\n\nURI: /sv\nMethod: GET\nArguments: 8\n w: 2,1\n mh: 192.168.2.245\n ml: 1883\n mc: 29d394a0bae0463fa195512cee85a8c2\n mu: 79a01ba6fca44d53bc3e92c605462698\n mp: 52fc003bbfb94e8da5e750d172660ad8\n mt: sonoff\n mf: 29d394a0bae0463fa195512cee85a8c2/%topic%/\n”

W | DeviceManager: “Error in device setup. Device Rollo ({29d394a0-bae0-463f-a195-512cee85a8c2}) will not be added to the configured devices.”

Datei nicht gefunden

URI: /sv
Method: GET
Arguments: 8
w: 2,1
mh: 192.168.2.245
ml: 1883
mc: 29d394a0bae0463fa195512cee85a8c2
mu: 79a01ba6fca44d53bc3e92c605462698
mp: 52fc003bbfb94e8da5e750d172660ad8
mt: sonoff
mf: 29d394a0bae0463fa195512cee85a8c2/%topic%/


#6

http://sonoff/sv?

URI sv not found?


#7

Hey, Maybe this is the mistake?

File Not Found

URI: /sv
Method: GET
Arguments: 8
** w: 2,1**
** mh: 192.168.100.147**
** ml: 1883**
** mc: bc216beffee94c1ba8ec701eba8c9449**
** mu: 5f9a81567383446baeb47e12cd5db318**
** mp: 8a10a66a654e4f3cbae5fcbf1eb444d4**
** mt: sonoff**
** mf: bc216beffee94c1ba8ec701eba8c9449/%topic%/**

mh = mqtt host
ml = mqtt port
mc = mqtt client
mu = mqtt user
mp = mqtt password
mt = mqtt topic
mf = mqtt topic

but all these parameters are not in the “sv” page, but in the http://192.168.100.191/mq?


#8

Hi chris,

I’m sorry it took so long to reply. I was on holidays for a week and then on a conference.

Thanks a lot for the feedback, I will investigate and come back to you. It seems you’re on the right track with what you’ve found out.


#9

Hi again. I’ve looked at this now but it seems /sv is correct, at least for my case. /mq would only retrieve the mqtt configuration but /sv is used to set the configuration.

Could you please go to http://192.168.2-150/mq with your browser (The MQTT configuration page of your Tasmota device), then open the developer tools and go to the “Network” tab. Then click the Save button and see where it posts the configuration to?

Also, what Tasmota firmware version do you use?

Thanks a lot,
Michael


#10

https://pastebin.com/QT8fHBfe

https://pastebin.com/hrWwUqzh


#11

Hey chris,

I believe I have fixed the issue. The fix has been released by now. Thanks a lot for your support.

Also, in your logs I have seen that you have connected a Roller shutter to it. Because of that I added the ability to configure 2 channel tasmota devices to have roller shutters connected.

Please let me know how it goes.
Thanks again