TriLife

Hello @EVictory, Here is an example of what a Sonoff/Tasmota Temperature sensor publishes: 01:42:04.420 MQT: tele/ClrTemp/SENSOR = {"Time":"2025-08-11T01:42:04","DS18B20":{"Id":"3C01B55696F0","Temperature":20.50},"TempUnit":"C"} Let me know, if this helps. Cheers.

Hello @EVictory, I'm back in town! Were you able to fix address your issue? Cheers

Hi @evilpete, The MQTT plug-in was designed for Tasmota integrations. Tasmota doesn't send JSON packets, only individual data points. I think @sjenkins added one or two devices, which send JSON packets. He might be able to shed more light to see, if using his device-type will better match your needs.

Hello @EVictory, I'm away from my computer for a few days, so won't be able to respond in detail. From memory, please have a look at how you configure your .yaml. I seem to recall that for sensors it's not 'status_topic' but something like 'sensor_topic'. Like I said, from memory. You also might want to look at configuring it like an 'analog' device instead of 'Temp' which is very Tasmota/Sonoff..., also try 'temphumid' (look for correct spelling). I'll try to get back to you next week. Sorry again for the delay. Cheers.

Hi @EVictory; Glad you figured it out. Cheers.

Here you go @TomJ, https://github.com/Trilife/udi-mqtt-pg3x

Hi @TomJ There is a description of the other Tasmota devices (temp, humidity etc), which can be operated with the MQTT plug-in. I'm away from my computer right now, but from memory: From inside PG3 click on Details of MQTT plug-in, then click Configuration. If it doesn't come up right away above tue config parameters, there should be a button to display tye configuration Details. If for some reason they do not show up, please let me know and I'll point you towards the GitHub repository. Cheers.

@Geddy, I went hunting and did indeed find the ud*.state files in C:\Users\{username}\AppData\Local\Temp. Went ahead and deleted them too. Also increased java memory to 1024m. Thanks for that hint. @Techman, if Norton can delete them, can I not do so manually as well? The /temp folder is close to 6GB! I used to have System Mechanic, which did do clean-up chores like this, but didn't bother install it on my new rig. maybe I should install it again. Update: I used Windows Disk Cleanup, which includes deleting temporary files. All in all close to 8GB. Good riddance. And I enabled Windows Storage Sense, which will do this automatically in the future. Thanks to both of you again.

Thanks @paulbates, I guess I need to practice my patience some more. Unfortunately I have no Insteon at all. Only Tasmota and Zwave. Cheers

@Geddy, Wasn't there talk a few months ago that the Admin Console was being deprecated in favor of something more modern?

Thanks @Geddy, No ud*.state files anywhere, but after I added '-Xmx512m' in the runtime parameters in Java, AC started showing up. another case of little patience (so typical for me). Cheers!

Thanks @Techman. I found temp/ but didn't locate any ud*.state files in there. But late last night, after not touching the PC for a long while, the AC showed up, with a different color scheme. Go figure. I had added the runtime variable to speed up the script. This morning, after reboot, the AC showed up right away with the correct color scheme. Go figure. Case closed.

Hi @vandy, Glad you figured it out. I'd replace "cmd_topic": "cmnd/sensor/POWER"}, with "cmd_topic": "cmnd/sonoff01/POWER"}, for consistency's sake. In this particular case it doesn't matter, since the s31 type will never issue a cmd_topic.

Thanks @Techman, I went through the links, looking for differences. Can't seem to get it to work. Like I said, once I try to launch the AC LAN from within IoX Launcher, it thinks for a while and then the icon of the IoX Admin Console appears in the task bar. when I hover over it I see the name in the title bar and a white panel. There is a single line in that white panel, but it is too small to read. When I hover over the white area, all open windows on my screens disappear. This is normal behavior in Win11, except that the only the affected window should show... which makes me think that the program is running, but not displaying...

No changes to the PC other than regular Win11 updates. This setup was working properly before