Figured it out, my mistake was in the websocket on my mosquito server running on a sinology NAS.... Websocket wasn't properly configured!
Thanks On Monday, August 21, 2023 at 10:27:44 PM UTC-4 vince wrote: > In the absence of any information about your os and revision level, which > broker you're running, or anything related to your broker configuration or > weewx MQTT configuration, can't help you. Sorry. > > You might google for "Client <unknown> disconnected due to malformed > packet." and look at the top hits, which might help you figure it out. > > > > On Monday, August 21, 2023 at 6:20:17 PM UTC-7 Lorin Tremblay wrote: > >> Anyone ever come across this issue >> >> >> 1692666712: New client connected from 10.36.50.120:56807 as >> weewx_51a9e36a (p2, c1, k60, u'oscar'). >> >> 1692666718: New connection from 129.222.204.46:62214 on port 1883. >> >> 1692666718: Client <unknown> disconnected due to malformed packet. >> >> 1692666718: New connection from 129.222.204.46:45385 on port 1883. >> >> 1692666718: Client <unknown> disconnected due to malformed packet. >> >> 1692666718: New connection from 129.222.204.46:41207 on port 1883. >> >> 1692666718: Client <unknown> disconnected due to malformed packet. >> >> >> Weewx connects fine, but not the skin belchertown. >> >> >> check the mqtt config in the skin about 20 times, can't figured it ou. >> >> >> Thanks for any help! >> > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/06d7d6b5-e08c-466c-a229-00e04d449a46n%40googlegroups.com.
