You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Its more a question than an issue: when I run two of them, one of them stop sending mqtt messages. In the mqtt explorer I can see that for a short time they ran in parallel, but after some updates, one stop working. They have different IP addresses and different names. Would it be possible, that they block each other somehow ?
Thanks a lot for this great software !
Peter
The text was updated successfully, but these errors were encountered:
There's probably a bug here, I've only been playing with one so far so i've not come across this myself. best guess is the chip id is not somewhere it should be or, less likely, there is a collision and happen to be the same (it's the 3 least-significant bytes of the mac address).
If you happen to find the issue feel free to raise a PR :)
from looking at the code, and with no equipment to reproduce and test, the unique_id it sends should be unique (assuming no collisions). I wonder if the node name needs to be unique also.
You can try setting the 'device name' in the WiFi-config/settings page to see if that fixes your problem.
Its more a question than an issue: when I run two of them, one of them stop sending mqtt messages. In the mqtt explorer I can see that for a short time they ran in parallel, but after some updates, one stop working. They have different IP addresses and different names. Would it be possible, that they block each other somehow ?
Thanks a lot for this great software !
Peter
The text was updated successfully, but these errors were encountered: