-
Posts
169 -
Joined
-
Last visited
Everything posted by jkosharek
-
Is that supposed to be port 1884?
-
Mixed results, but most of the time a query all would update all the outlets watts data. I have the UD Mobile button setup that way so I could see the current usage of all the outlets on a strip.
-
@Jimbo.Automates I have Kasa Smart Wi-Fi Power Strips (HS300) and the individual outlet 'Current Power' doesn't update on the 'longPoll' and also doesn't update on a query all. It updates if I go into the individual outlet and select query.
-
@Jimbo.Automates Do the dev packages still need to also be installed/updated or is that some Michel magic moving packages to the main update?
-
I did the same and am impressed with it so far with some of the things I am playing with. The downside is that it's not a straight local control/connection and I won't put a ton of effort in cloud or hybrid-cloud products without an established open API. Ratgdo is what I will be using once mine arrives
-
Released 3.1.2 seems to be ok. @Jimbo.Automates Can you clarify how the 'Current Power' should behave? Should it be updating on some regular short refresh period, or in almost real-time, or does it have to be queried to get an update from the device?
-
'Load Profile' from the Node server side did the trick! UDM configurations and AC Programs did also survived the node delete/re-install. Polling usage/wattage seems to be working in almost real time without the need to query. NICE WORK 🍻
-
@Jimbo.Automates Support had me install the dev packages from the admin Console | Configuration tab | click on Install Dev Packages. Once done, remove Kasa and then reinstall it again. Ignore all timeout errors as it might take up to 15 minutes. After 15min it shows as connected now and my 52 devices are added in the node and in the Admin console but they are fubar, even after an Admin Console restart and even after a EISY reboot: I tried deleting a couple from the node server that I don't have configured in programs and in UD Mobile to see if that changes anything, after restarts of the AC and EISY still fubar. None of the new nodes match up to the previous devices in programs or configured in UD mobile. Once this Node is fixed am I going to have to configure 100's of devices throughout the AC and UD Mobile?
-
https://www.universal-devices.com/my-tickets/
-
Mine does as well. It thinks it is running too 'Plugin Start: Already running.' Also after the last update/reboot the node can't get to the logs when I try to download logs: PG3x Version 3.2.16 Status: Connected Frontend Version: 3.2.16 IoX Version: 5.7.1 Connected Uptime: 7 Hour(s) 57 Minute(s) 1 Second(s) (c) 2023 UDI Getting Started File not found: /var/polyglot/pg3/ns/0021b9025fc4_2/logs/debug.log
-
I am on IoX 5.7.1, PG3x Version 3.2.16, and Kasa 3.1.1. I updated, rebooted, reinstalled and get the same error ModuleNotFoundError: No module named 'kasa' I put in a ticket.
-
Also moving the sync functionality back to the home page or at least to the Parent node.
-
From home, I select my EISY, then a lot of times I have to select more to get to the variables, programs and what not. I recent change that is kind of a pain. I would think that could all be on 1 sub page, it could also be a span of 3 wide. And when browsing the EISY, I don't see a difference between "Devices" and "Devices and Scenes".
-
@Javi 1.1.38 resolved the issue I had with tiles spans in this thread. 🔥👍🏻
-
1.1.37 resolved the scenes live updates. THANK YOU
-
No, it was OK after a reboot you suggested. I was just looking for info on what to expect. I don't have a local connection configured because I thought it was causing trouble with this. It might be hard to troubleshoot because this screen does not work and says the portal is offline. Is there a IoX URL that displays these connections, something I can get to outside of the app and when the app thinks UD cloud is offline? I am playing with a MQTT node from the non-prod store and have a MQTT explorer running wonder if that causing the issue.
-
@JaviMy not expired connections currently looks like this, would the non-portal connection be PG3x? I don't currently have any Admin Consoles open, would an MQTT Explorer count?
-
Like EISY and IoX 5.7.0?
-
Is there a troubleshooting procedure for that? Don’t use home bridge and I haven’t had to look at that since the direct connections from MobiLinc mobile app days. Great work on the mobile app
-
-
@Javi there still seems to be updating issues with scenes too. If I press a button to turn on a light that is a scene, I have to go out of the page and back in to see the status change. Just rebooted and Getting this error also:
-
1.1.36 fixed the variables! Thank you for such a quick turn around. Text is slightly larger as well:
-
I ended up settling on these rules, I would rather have them only send data on a change but this is giving me real time data from the sensors. Rule1 on tele-DS18B20#Temperature do publish Stat/GenMonitor/Temp {"Time":"%TIMESTAMP%","DS18B20":{"Id":"DS18B20-1","Temperature":%value%},"TempUnit":"F"} endon Rule2 on ANALOG#RANGE do publish Stat/GenMonitor/Batt {"Time":"%TIMESTAMP%","ANALOG": {"Range": %value%} } endon
-
@Goose66 I am toying with an ESP8266 board running Tasmota and sending data to the MQTT node for battery voltage on a backup generator and wanted to also know when the generator is running by monitoring a 12v contactor coil voltage. Tasmota doesn't seem to be able to send sensor values to MQTT on a value change so I am looking at doing a publish with Tasmota Rules. Here is an example that I have working: Rule1 on tele-DS18B20#Temperature do var1 %value% endon on DS18B20#Temperature>%var1% do backlog var1 %value%; publish Stat/GenMonitor/Temp {"Time":"%TIME%","DS18B20":{"Id":"DS18B20-1","Temperature":%value%},"TempUnit":"F"}; var2 %value%; endon on DS18B20#Temperature<%var2% do backlog var2 %value%; publish Stat/GenMonitor/Temp {"Time":"%TIME%","DS18B20":{"Id":"DS18B20-1","Temperature":%value%},"TempUnit":"F"}; var1 %value%; endon That produces this, just don't understand the %time% output: {"Time":"1288","DS18B20":{"Id":"DS18B20-1","Temperature":79.59},"TempUnit":"F"} The one for the analog input doesn't seem to work at all, I have tried A0, ADC0, Analog: Rule2 on tele-ADC0#Range do var3 %value% endon on ADC0#Range>%var3% do backlog var3 %value%; publish Stat/GenMonitor/Batt {"Time":"%TIME","ANALOG":{"Range":%value%}}; var4 %value%; endon on ADC0#Range<%var4% do backlog var4 %value%; publish Stat/GenMonitor/Batt {"Time":"%TIME","ANALOG":{"Range":%value%}}; var3 %value%; endon Do you know of a better way to get more of a real time status from Tasmota to MQTT and in to IoX?
-
The text is about 1/2 the size it was before the update and on an iPhone 15 Pro Max it's now way to small, I couldn't image being able to read this on smaller phones. Here is an example of C30 Longer titles being smaller text and c10 shorter titles being taller (I would expect this): Here is an example of everything being too small. Based on what you said above the title size, these are all short and I would expect them to be larger. The titles and values are all short and I would expect them to be larger. Is the global text size being settable going to be an option? You mentioned a future setting for the titles size, will that also be true for the values text size? What is the time line for 1.1.36 to be released?