skunkiechris

Probably too soon for any subjective feedback, but wondering how much of the performance of IoX is disk based, vs processor & RAM. As in, @Michel Kohanim, is the upgrade worth it just for running IoX, or is this more of an upgrade that is useful for running other tasks (VM's, etc) on eisy? Thanks!

Haven't had the client stopped error a single time since the change....seems to be working!!! Thanks again!!

@DavidV I went through this exactly same thing a few months ago. Opened a ticket, and the suggestion was to migrate from zooz to zmatter. (I had zmatter, just wasn't using it due to migration issues the previous time I attempted it.) I did eventually migrate to zmatter, but one of the releases prior to that (5.7 maybe) seemed to completely solve it for me. It was very mysterious, in the end not entirely sure what exactly fixed it. But like I said, it was exactly the same symptoms!

First reboot, then power cycle after reboot, both resulted in being stuck on Initializing subscription.

Same as above, Vista 21IP, EnvisaLink4. And, same in terms of used to use the IP module for Total Connect, got rid of that part some time ago as well. The only shortcoming that I have hit is that the Vista panels stop reporting sensor activity when the alarm is armed in any state. So, night, stay, away...you won't get motion, door/window, etc activity reported to IoX. Not a deal breaker for me....the couple of spots that I needed that info I've just used insteon or z-wave modules to supplement.

A unplug/plug followed by IoX restart usually works as well.

Just curious as to the reasons behind that suggestion? (I'm not disputing it lol, just curious.)

Hmmm....I hadn't actually grabbed the log yet when it started working yesterday. I just went to look now and I only see a log from today in the logs directory. I guess logs are deleted on a daily basis?

Okay, so, I did absolutely nothing whatsoever. When I left it the main device in eisy was borked, and all my programs had not specified, no nodes in polyglot. Went away, made dinner, turned on the TV, and everything reacted correctly. Looked at eisy/polyglot, and things are normal. So, I guess disregard the above!

@Jimbo.Automates Hmmmm, it doesn't seem to work after the update. My hubs.json is still in the config director, I changed nothing....but it doesn't see the Harmony at all. 2023-12-19 15:35:26,909 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-12-19 15:35:26,909 MainThread udi_interface INFO __init__:<module>: UDI interface initializing 2023-12-19 15:35:26,909 MainThread udi_interface INFO __init__:<module>: User=0021b9026524_14 2023-12-19 15:35:26,910 MainThread udi_interface INFO __init__:<module>: Home=/var/polyglot/pg3/ns/0021b9026524_14 2023-12-19 15:35:26,910 MainThread udi_interface INFO __init__:<module>: Node Server Path=/var/polyglot/pg3/ns/0021b9026524_14 2023-12-19 15:35:26,910 MainThread udi_interface INFO __init__:<module>: PG3INIT=<redacted> 2023-12-19 15:35:26,910 MainThread udi_interface INFO __init__:<module>: Loading interface module 2023-12-19 15:35:26,955 MainThread udi_interface INFO interface:<module>: Loading MQTT module 2023-12-19 15:35:27,483 MainThread udi_interface INFO interface:<module>: MQTT module loaded 2023-12-19 15:35:27,712 MainThread udi_interface INFO __init__:<module>: Loading udi_interface module 2023-12-19 15:35:27,713 MainThread udi_interface INFO __init__:<module>: Loading node module 2023-12-19 15:35:27,713 MainThread udi_interface INFO __init__:<module>: Loading custom module 2023-12-19 15:35:27,713 MainThread udi_interface INFO __init__:<module>: Loading isy module 2023-12-19 15:35:27,713 MainThread udi_interface INFO __init__:<module>: UDI interface initialized 2023-12-19 15:35:27,714 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.2.6 Starting... 2023-12-19 15:35:27,771 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.2.16 [ISY: 5.7.1, Slot: 14] 2023-12-19 15:35:27,771 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '172.26.18.3', 'netmask': '255.255.255.0', 'broadcast': '172.26.18.255'} 2023-12-19 15:35:27,772 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2023-12-19 15:35:27,772 MainThread udi_interface.interface INFO interface:updateProfile: Sending Install Profile command to Polyglot. 2023-12-19 15:35:27,772 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL cert: 0021b9026524_14.cert key: 0021b9026524_14.key ca: /usr/local/etc/ssl/certs/ud.ca.cert 2023-12-19 15:35:27,773 MainThread udi_interface INFO Controller:__init__: HarmonyController: Initializing 2023-12-19 15:35:27,773 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: harmonyctrl not found in database. 2023-12-19 15:35:27,773 MainThread udi_interface.interface INFO interface:addNode: Adding node HarmonyHub Controller(harmonyctrl) [None] 2023-12-19 15:35:27,773 MainThread udi_interface.interface INFO interface:setController: Using node "harmonyctrl", driver "ST" for connection status. 2023-12-19 15:35:27,819 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-12-19 15:35:27,820 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:65:24_14 - MID: 2 Result: 0 2023-12-19 15:35:27,861 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2023-12-19 15:35:27,943 MQTT udi_interface.interface INFO interface:_message: custom data response {'customparamsdoc': ''} 2023-12-19 15:35:27,943 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customparamsdoc 2023-12-19 15:35:28,115 Thread-5 udi_interface.interface WARNING interface:checkProfile: check_profile: Force is enabled. Seems like maybe that warning line is something? Thanks...

Awesome, I've updated, will let you know, thank you so much!!!

With the move to ZMatter, my motion sensors have two motion nodes now, 155 Motion Sensor, which is what they've always had, plus 380 Binary Motion Sensor. They seem to activate exactly the same. Is there any difference between the two? Thanks!

Thirdreality multifunction motion sensor, illumination sensor, and multicolor nightlight. Currently works as multicolor light with on/off, no motion or illumination sensing. Model: 3RSNL02043Z Amazon: https://www.amazon.com/dp/B0C9LNXYLL

He, I guess I forgot to say that this behavior coincided with the migration from Zooz to ZMatter. But today it seems to be normal, so, who knows.

I have multiple Kwikset 620 Zwave 700 deadbolts. Most work perfectly fine, but one does not operate the vast majority of the time when sent commands, but there is also no failure showing in the log, nor does it ever say can't communicate. In the L3 log these are all the transactions I see, and the lock does absolutely nothing: Tue 12/12/2023 01:57:30 PM : [ZW-TX-A 00127 54.0 ] [ZY054_1] Door Lock Set mode=0 Tue 12/12/2023 01:57:31 PM : [ZW-DONE 00127 54.0 ] [ZY054_1] Door Lock Set mode=0 I've attached the ZWAY log file for the operation, I don't know how to interpret all of that. All the nodes are present on the lock, and I have rewritten links and updated neighbors, there are no communication issues at all. (It's also about....20 feet from the zmatter dongle. Any help would be appreciated!! Thanks! zy log.txt