New version 1.49.2 to test before final release
Re: New version 1.49.2 to test before final release
Hi chiccio,
I gave MQTT.LWT a try and sometimes it works and sometimes not.
The broker ist producing error messages...
Any ideas? My test code.
Ret = MQTT.SETUP("mqtt://192.168.178.38")
Ret = MQTT.CONNECT("", "")
pause 300
Ret = MQTT.PUBLISH("annex/88", DATE$ + "-" + TIME$)
Ret = MQTT.PUBLISH("annex/88/LWT", "Online")
Ret = MQTT.LWT("annex/88/LWT", "Offline", 1, 1)
Ret = MQTT.SUBSCRIBE("annex/88/cmnd")
wait
I gave MQTT.LWT a try and sometimes it works and sometimes not.
The broker ist producing error messages...
Any ideas? My test code.
Ret = MQTT.SETUP("mqtt://192.168.178.38")
Ret = MQTT.CONNECT("", "")
pause 300
Ret = MQTT.PUBLISH("annex/88", DATE$ + "-" + TIME$)
Ret = MQTT.PUBLISH("annex/88/LWT", "Online")
Ret = MQTT.LWT("annex/88/LWT", "Offline", 1, 1)
Ret = MQTT.SUBSCRIBE("annex/88/cmnd")
wait
Re: New version 1.49.2 to test before final release
sorry, forgot screenshot.
You do not have the required permissions to view the files attached to this post.
- cicciocb
- Site Admin
- Posts: 1996
- Joined: Mon Feb 03, 2020 1:15 pm
- Location: Toulouse
- Has thanked: 428 times
- Been thanked: 1336 times
- Contact:
Re: New version 1.49.2 to test before final release
try to put MQTT.LWT before MQTT.CONNECT because it is required before the connection is done (it is sent during the connection phase)[Local Link Removed for Guests] wrote: [Local Link Removed for Guests]Mon Feb 27, 2023 10:56 pm Hi chiccio,
I gave MQTT.LWT a try and sometimes it works and sometimes not.
The broker ist producing error messages...
Any ideas?
image.png
My test code.
Ret = MQTT.SETUP("mqtt://192.168.178.38")
Ret = MQTT.CONNECT("", "")
pause 300
Ret = MQTT.PUBLISH("annex/88", DATE$ + "-" + TIME$)
Ret = MQTT.PUBLISH("annex/88/LWT", "Online")
Ret = MQTT.LWT("annex/88/LWT", "Offline", 1, 1)
Ret = MQTT.SUBSCRIBE("annex/88/cmnd")
wait
ex.
Code: [Local Link Removed for Guests]
Ret = MQTT.SETUP("mqtt://192.168.178.38")
Ret = MQTT.LWT("annex/88/LWT", "Offline", 1, 1)
Ret = MQTT.CONNECT("", "")
pause 300
Ret = MQTT.PUBLISH("annex/88", DATE$ + "-" + TIME$)
Ret = MQTT.PUBLISH("annex/88/LWT", "Online")
Ret = MQTT.SUBSCRIBE("annex/88/cmnd")
wait
Re: New version 1.49.2 to test before final release
Thank you, this seems to work. By this I can easily check if a divice ist offline by checking the broker messages.
My broker is still sending wierd messages about differen annex-devices. Is there a way I get to know which device is ment by
annex_xxxxxxxxxx ?
this could probably solve Problems with mqtt communication. Does a device send an indentification number?
thanks
Erhard
My broker is still sending wierd messages about differen annex-devices. Is there a way I get to know which device is ment by
annex_xxxxxxxxxx ?
this could probably solve Problems with mqtt communication. Does a device send an indentification number?
thanks
Erhard
- cicciocb
- Site Admin
- Posts: 1996
- Joined: Mon Feb 03, 2020 1:15 pm
- Location: Toulouse
- Has thanked: 428 times
- Been thanked: 1336 times
- Contact:
Re: New version 1.49.2 to test before final release
You can use the 3rd optional parameter to define your ID
Code: [Local Link Removed for Guests]
Ret = MQTT.Connect(login$, pass$ [id$])
Connect to the server using the provided login and password.
Optionally id$ permit to define an arbitrary ID
Returns 0 if OK
Re: New version 1.49.2 to test before final release
Thank you for your help. There are still some errors on other units (8266) and I try to figure it out.
Come back to this.
greetings...
Come back to this.
greetings...
Re: New version 1.49.2 to test before final release
Gentlemen,
I found out that if you connect to the WebServer of Annex basic it all runs normally and only your Station Mode connection is visible on your Router.
If you have also made a serial connection, the Ap mode connection will also be visible and if nothing has been entered in Config for Ap mode, the mac address will be displayed without a lock!
So if you do not enter anything in Ap mode and have not entered Protected Access, your neighbor can watch.
So be careful with a serial connection and always use a Name and strong password with Ap mode and also apply secure access and of course also applies to Station Mode.
This only disappears again at your Router when you have closed all serial programs and restart the ESP module without opening a serial terminal connection.
Whether this is a mistake I don't know, but people have already been warned about it?
Jan
I found out that if you connect to the WebServer of Annex basic it all runs normally and only your Station Mode connection is visible on your Router.
If you have also made a serial connection, the Ap mode connection will also be visible and if nothing has been entered in Config for Ap mode, the mac address will be displayed without a lock!
So if you do not enter anything in Ap mode and have not entered Protected Access, your neighbor can watch.
So be careful with a serial connection and always use a Name and strong password with Ap mode and also apply secure access and of course also applies to Station Mode.
This only disappears again at your Router when you have closed all serial programs and restart the ESP module without opening a serial terminal connection.
Whether this is a mistake I don't know, but people have already been warned about it?
Jan
- cicciocb
- Site Admin
- Posts: 1996
- Joined: Mon Feb 03, 2020 1:15 pm
- Location: Toulouse
- Has thanked: 428 times
- Been thanked: 1336 times
- Contact:
Re: New version 1.49.2 to test before final release
Yes, I didn't published the version or the esp32-S3.[Local Link Removed for Guests] wrote: [Local Link Removed for Guests]Sat Mar 04, 2023 4:27 am Did I miss a .bin for the S3?
It looks that you are the only one interested
What is the module that you have? QIO / OPI / PSRAM ?
Re: New version 1.49.2 to test before final release
+1
I have this one on order ...
I have this one on order ...
You do not have the required permissions to view the files attached to this post.