Closed stefanbbb closed 4 years ago
Done, now I get a lot of hex dumps:
Checksum and header received ok! Total reads : 84.000000 and total good reads : 82.000000 (97.62 %) Fail to publish, not Connectedread ma status true map[gpio-0:lo gpio-1:lo gpio-10:hi gpio-11:lo gpio-13:hi gpio-15:hi gpio-16:hi gpio-2:hi gpio-3:lo] map[gpio-0:lo gpio-1:lo gpio-10:hi gpio-11:lo gpio-13:hi gpio-15:hi gpio-16:hi gpio-2:hi gpio-3:lo] Fail to connect broker, network Error : dial tcp 127.0.0.1:1883: connect: connection refusedsent bytes: 110 with checksum: 18 71 6C 01 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Received 203 bytes data
71 C8 01 10 55 95 53 49 00 55 00 00 00 00 00 00 00 00 00 00 19 15 11 55 15 9D 55 05 0A 00 00 00 00 00 00 00 00 00 99 8D A3 8A B4 71 71 5D 99 00 00 00 00 00 00 00 00 00 00 00 80 85 15 8A 85 85 D0 7B 78 1F 7E 1F 1F 79 79 8D 8D 99 A3 7B 8F A3 A3 7B 8F 98 85 80 8D 8A 94 9E 8A 8A 94 9E 81 8B 8A 11 3D 78 C1 0B 00 00 00 00 00 00 00 00 55 55 55 21 73 15 55 05 22 12 69 00 00 00 00 00 00 00 00 E2 CF 0B 15 33 42 D1 0B 18 33 93 00 00 93 93 93 32 32 8D 8A 32 32 32 99 99 93 92 95 93 93 61 94 61 97 42 01 01 01 00 00 22 00 01 01 01 01 79 79 01 01 9C 00 00 B6 01 00 01 00 00 01 00 00 0A 01 01 01 01 01 01 01 00 00 00 E3 Checksum and header received ok! Total reads : 85.000000 and total good reads : 83.000000 (97.65 %) Fail to publish, not Connectedread ma status true ^C
"Fail to connect broker, network Error : dial tcp 127.0.0.1:1883: connect: connection refused" please insert a pendrive with config , and wait when config upload. When it will happen probably you have to kill GoHeishaMon_MIPSUPX (first ctrl+z , and then by killall comand like in above post ,and start it)
The pendrive with the config file named"GoHeishaMonConfig.new" was in all the time
Ok , strange. Anyway remove this pendrive ,ctrl-z ,and killall -9 GoHeishaMon_MIPSUPX. And if you know how to use vi editor , you can edit config file "vi /etc/gh/config"( or i.e. remontly edit this file via WinSCP) and apply your settings ,and then run /usr/bin/GoHeishaMon_MIPSUPX again , to see why it is not connecting to mqtt.
You can also do a "fwupdate sw" ,and reboot , to change the side to SmartCloud ,and install the newest 1.1.150 GoHeishaMon from scratch ( and following new readme.md)
Great, done! The config file was just filled with standard values, not with the values from the pen. I changed it manually and mqtt is running now.
Thank you very much for your great support!!:-)
Now it would be just nice to know, how to set the wlan settings. And why the config file gets not updated. During startup, the LED of the pendrive was blinking. So, access to the file should be ok. Maybe some problem with the pen drive?
First , please update it to the newest 1.1.150 . I'm not sure why config file could not be updated , but it is modified on newer version , so this knowleadge will be useless anyway. So go back to SmartCloud ( hope 3 buttons are working also ) , and install new one.
Update is done, but now we have the same story again: no mqtt, no ssh. Are you sure that the config file has the right filename? (GoHeishaMonConfig.new)
Can you provide a bin-file where the ssh is already activated?
BTW: I edit the config file on a windows pc. I know that this sometimes leads to problems on Linux-based systems. Could that be the rootcause that the config file get not copied?
After some reboots it's working now. mqtt is there, but when I try to activate ssh, I get an error in OSCommand out: "umount: can't umount /overlay: Invalid argument
Looks like you performed command umount /overlay already and you trying to do it second time. Umount is posible only once :) To be sure /overlay is unmounted , type command mount , if in answer there is line "/dev/mtdblock3 on /overlay type jffs2 (rw,noatime)" it is still mounted , if not , it is already umounted.
But since you performed firstboot on your CZ-TAW1 already ,there is a chance that ssh will be already without doing it. Please wait 5-10min to build the ssh rsa2 key and try to connect.
Ok, well done! SSH is running. I'm just trying to config wlan with openwrt doc, but I'm struggling a little bit. Can you give me the right parameters?
This is how orginally CZ-TAW1 is doing it:
uci set network.wlan=interface uci set network.wlan.proto=dhcp uci set wireless.radio0.channel=auto uci set wireless.radio0.disabled=0 uci set wireless.@wifi-iface[0].network=wlan uci set wireless.@wifi-iface[0].mode=sta uci set wireless.@wifi-iface[0].encryption=psk2 uci set wireless.@wifi-iface[0].key=yourpassword uci set wireless.@wifi-iface[0].ssid=yourSSID uci commit wifi
In this whay you will receive additional IP for WIFI ,so booth connections will be possible.
Ooops, this sounds dangerous. My cable is not there anymore, and the soldering was a little bit fiddly.So, I want to be 100% sure that it works. On openwrt.org I've read something like option mode 'sta' and option wds '1' (https://openwrt.org/docs/guide-user/network/wifi/atheroswds). Do we need that here, too?
Sta should be already set ( you can see current settings via uci show , or specyfy uci show wireless), but i added to above post this command. WDS is not a case ,you are not making a wireless bridge or reapeter,only client. Also WDS needs some implementation in drivers , i'm not sure if openwrt realese with CZ-TAW1 uses, have it.
Edited post above , checked ,and worked for me.
Another question: would it be possible to implement some kind of uboot boot script or similar in further versions? That would make handling with ssh and network settings much more easier, I think. And we could avoid the fiddly handling during soldering these small cables. What do you think? Is that a possible improvement? It would help some stupid beginners like me a lot in setting up and administration. And if I make an error, I just would have to change the boot script.
For beginners only thing with is needed , to have always possibility to go back to SmartCloud , and have posiblility to upload the config file. First posibility now is "upgrated". Previously was , that GoHeishaMon procces took care about the handling of three buttons and it was a risk ,that if this proces stops ,also buttons will be not supported anymore. Now it is independent , and it is pretty sure ,that buttons will be always availble. Second possiblility was always , but now is updated , that when the config is uploaded ,restart is performed and config is inplemented.
SSH and luci is not needed for beginners.
Wifi setup will be , if it was on SmartCloud side.
guys i think this issue was closed and we can move on :)
OK, last comment: This means, if ethernet connection is killed, I can now press the 3 buttons, configure wlan in original firmware and install GoHeishaMoon new by pressing the 3 buttons again, right?
Yes ! For now it’s prefered Solution
Just to let you know: wlan and lan are running with the new configuration!!! Great! Thanks for supporting me so much!!
Hi, The CZ-TAW1 was running like a charme directly after installation, but after two days of shutting down the power, it will not restart. Just the green power LED and nothing else. Sometimes also the white one, but not the third, and no connection at all. No reaction to HW-Reset (3buttons simultanously) Who can help?