SJK

Doing some forum searxihng about orphaned zigbee devices I found an acknowledgment in 2023 that this was a bug and would be fixed within the week, followed by a user stating still not fixed a few months later. Other threads were all closed without any replies or that upgrading firmware fixed it. Perhaps a regression? I'm starting to think that if the controller still thinks the device is there, it's not going to re-pair. But if I cannot delete it, I'm stuck. I'll put in a ticket to ask.

I did factory reset them multiple times - screw/unscrew method. They were successfully reset. Turn off the bulb for 5 seconds Turn on for 8 seconds Turn off for 2 seconds Turn on for 8 seconds I have another one of these bulbs planned for another room when I install the pendant- I just tried to link it to the eISY in place of one of the nonresponding bulbs and it instantly paired, confirming it's not a radio interference issue, etc. When I use the Xray function to see the devices in the ZB network- I have 16. I only have 10 devices on this network. There's devices there I don't have and the ones that don't respond and have been removed from the eISY. None function- I get errors if I try to interact with or query them. I have removed them from the zigbee network before removing them from eISY, but they still persist in the all devices table, and if you do a synchronize new and delted with interview they come back. How do I permanently remove them from the network? Not sure this has any actual bearing on the actual problem, but seems odd I cannot remove anything ever.

I use some Tuyo clone things for window candles- the ones that you splice into the power cord. Something like those old Sonoff Zigbee basics. Also a couple of Sonoff USB on/off switches for the Lectrofans. All of those items are working just fine as well. I use no hub or nodeserver for the hue devices- they are linked directly to the eISY using the ZMatter dongle. Same for the other devices mentioned above.

I have a handful of Hue bulbs (and some other Zigbee devices) on my eISY. Within the past week 2 of the hub bulbs stopped working. These are the fancy lightguide glass bulbs. First the one in the master bedroom pendant stopped responding, then a day or so later, the one in my daughter's bedroom pendant. I factory reset them but they will not re-add to the eISY. First I tried an update/interview, then the reset with removal from the eISY, but again, will not re-pair. The lights work with bluetooth on my phone. (They aren't dead). I set up the hue app to verify that they still function. They are only maybe 2 months old? I doubt the zigbee radio is dead- they failed nearly simultaneously. No power failures or surges etc- I use whole house surge suppression and we have relatively "clean" (stable) power here. The only interim change is upgrading to 3.9.1 and turning on Matter support. I have no matter devices, and I did try turning it back off without any luck. But this issue didn't temporally appear- I updated to 3.9.1 a week or two after it came out, and this issue started a week ago. My zigbee network is fine- other devices work, including the other hue bulbs in the house. The regular 60 and 75w A type bulbs are still doing their thing- including those in the same rooms. This isn't a range or interference issue- nothing else has changed and again, everything else just works. (Side note- have the Polisy running a separate Zigbee network on a separate channel for exterior/window devices- completely separate radio frequency, should not have any issues there- have been happily co-existing since the fall). Any thoughts? I have no idea what to troubleshoot next.

not enough info in the post to troubleshoot, but here's a few starting points: 1) You have the towel bar 2 hour off program currently running while towel bar AM is also true- check out why (if it's a simple logic of if towel bar on, wait 2 hours then off, that would explain it.) 2) Check the date/time/timezone at the top of the AC to ensure it is still set correctly 3) Are the devices themselves responding? Turn it on/off at the device and see if it works manually and that it's status is reporting correctly in the AC Reply back with that stuff first (Is it plugged in, etc)

The new 5.9.1 release and the instruction/admonition to ensure you have good backups before proceeding got me thinking. Do I understand the complete backup strategy? I didn't find the complete answer here so thought I'd ask. Obviously there's the "backup IoX" menu item. Used to take a long time- now it's incredibly fast and makes a small zip file- too small... Makes me wonder what's not included. What does the backup IoX file include? All programs? All configuration tab items? Per the migration guide it seems like an all-in-one backup. But IIRC my migrations in the past were not smooth (but there were version and hardware differences- was not a straight like for like restore) requiring a fair amount of re-work. Topology file? (Good to have, not a restorable item but contains some very valuable information) PLM links table? I've found a few of those files lying around my backup folder and cannot figure out how to do that again if needed. As above- do I backup my programs separately? (Even if included in the main file)- a good idea in case a partial restore is needed due to a programming misadventure? If I export the root folder of my programs- are all included or just that root folder? File size seems really small given the amount of programs I've built. Variable definitions? Main file I'd expect? Z-wave- don't use it but see there's a separate procedure to backup a Z-wave network. What about ZigBee? Matter? Polyglot- has it's own backup system. Any caveats there? UDMobile is relatively straightforward, obviously a separate step. I have multiple production devices- no spare equivalent test devices- not interested in blowing up my controllers to f-around and find out on my own if my backup is complete at this stage. What does everyone do?

More sonoff devices- Water leak sensor is recognized as a water leak sensor class device by IoX with multiple parameters but water leak detection events are not received. https://sonoff.tech/product/gateway-and-sensors/snzb-05p/

Agree - I started with this 20 years ago now with Insteon V1 and and Elk integration using the X10 commands and some dedicated hardware interface between the two. Now 2 homes and 2 businesses later I'm on my 5th and final buildout with my preferred kit. So as I said- dipped toes into water with HomeKit (or spent the time in HA rabbit holes)- can keep it, but not any killer feature to layer on top of a polished IoX setup. It's just hard to follow with all the Matter this and Thread that hype- sounds great for interoperability in simple setups, but IoX already is integrating and translating between vendors and protocols just fine.

General question: What's the advantage of integrating HomeKit (Apple) to IoX? I'm not sure what I'm missing out on by not doing this and interested in the killer functionality this provides given all the talk re: Matter, etc. With the pending January update just announced, I'm thinking the advantage is even less. I'd understand if someone started with a HomeKit environment and fell into IoX, but not the other way around. I have an Insteon-heavy environment, so IoX is ideal there. I have branched out into Zigbee 3.0 (Hue bulbs, Sonoff switches, GLEDOPTO devices for LED strips and architectural lighting) but also use Polyglot for UniFi, Venstar, Elk, and CAO/Wireless Tags integrations. An eISY and a Polisy running IoX and Polyglot are my only hubs. The admin console programming setup is very flexible- things often require multiple small programs making sort of a web of interactions (vs a HomeAssistant script for example) but it's intuitive. Any limitations I've run into when trying to accomplish something is more often hardware-based, rather than IoX capabilities itself- with a few exceptions of trying out some cheap "unsupported" devices. Perhaps that's it? People using a mishmash of cheap consumer devices of the week that are supported in HK or HA and may not have made it into IoX yet? I'm not currently using ZWave at this house but am in commercial settings. So what's the advantage? A prettier UI from Apple instead of UDMobile? Even there, UDMobile is awesome- I've built a massive interface for my iPhone allowing me to control multiple IoX systems at multiple in one place. And I try to automate most actions so I don't need to fiddle around in the app to live my life- my home just does it's thing and responds to presence, motion, climate/weather/luminance, etc. I use Insteon keypads for most manual interaction and am installing a wall-mounted iPad to run UDMobile and a web browser for other home services (calendar/shopping list, etc). I'd rather not have to whip out my iPhone as I walk around my house to trigger events. I interact with Elk directly for security when home, which IoX monitors to trigger some routines, and UDMobile if I need to interact with or monitor the security system when away from the premises. I'm using UniFi protect for cameras (and access at commercial settings) but they have their own apps and I don't really need them to integrate with IoX. and then I could integrate an RSTP camera stream to UDMobile if desired (not sure of that other than quick access to a key feed or two in case of an alarm event rather than switching apps- maybe). Sonos and Roku aren't well integrated into IoX via Polyglot- always ran into issues with them (some self-inflicted based upon enforced network segmentation)- but then Sonos has an app if I want to interact with it, and I can use the IoX network module if I want to program a specific action such as pressing an Insteon key to turn on the radio while cooking, etc. What are people doing with HomeKit and HomeAssistant if they've got a mature IoX setup?

Sonoff ZBMINIR2 on/off switch. Currently able to be added as a Zigbee device, on/off works, but no ability to configure/mange device settings such as detached mode, inching mode, trigger mode, power reset state. My use case is to sense a local switch for Hue bulbs to toggle on/off state without powering off bulb entirely (originally wired it as a local failsafe switch/if we ever sell the house and revert to "dumb" wiring). A whole lot cheaper than another insteon switch with a disconnected load. https://www.zigbee2mqtt.io/devices/ZBMINIR2.html https://sonoff.tech/product/diy-smart-switches/zbminir2/

I currently have zero Z-wave devices at this location so could live with that. Too many scenes with each devices a member of multiple scenes to accommodate on insteon PLM. Attached article not too helpful- one network manager per network- but I'm looking at making multiple independent networks - or at least that would be fine as I see no need to make both see each other. It does mention "start network and join/leave network" so presumably each controller should set up their own independent network - otherwise how would interference between neighbors be prevented? Found this: https://www.rfwireless-world.com/Tutorials/Zigbee_tutorial.html which mentions each controller starts its own personal area network- so I can see on my eISY this in X-ray of the network: Integer DATA controller.data.defaultPanId = 27238 (0x00006a66) I would assume that if I bought another ZMatter dongle it would create a different network ID- either randomly or upon detecting a collision with an existing network but that is a something one of the UD developers would have to confirm.

As an aside- just received my first actual Philips Hue bulbs and tried one out. Amazing that I can set commands directly with scenes included alongside Insteon switches- so I can use the regular wallswitch button to turn the light on AND reset the temp back to a "normal" bulb rather than the last on. Well done native implementation! Kudos!

I don't have a large zigbee network, I have a large Insteon network. The Zigbee devices will be in locations covered by each of the IoX controllers (max nodes/scenes/devices per PLM) and cannot be reconfigured to condense the Zigbee network to one IoX controller.

I have a corner-case question here regarding Zigbee (and possibly ZWave). I have an eisy and a polisy both running in the same home as my Insteon network is too large for one to contain all nodes. The polisy handles exterior and basement, the eisy handles floors 1-3 in the main home and the entire HVAC system. Polisy handles polyglot and external intgrations and the eisy references polisy for polyglot. I'm now adding Zigbee to my home- currently for Hue-style lighting using the GLEDOPTO 5 in 1 LED drivers and their exterior wall wash and garden lighting (integrated Zigbee 3.0). Problem is I'll have some inside the home, where it will be important for them to integrate with the interior scenes and programs on eisy, and also the garden/wall wash exterior ones which should be integrated with the exterior scenes- on polisy. Since z-matter works without a hub I don't have one so I don't need or want to use polyglot/nodeservers. That would make this easier as both could "see" the nodes (like I do with Elk). I have no problem getting a second ZMatter dongle for the Polisy. But then I have two controllers. Can they be on the same network? Should I just change the frequency of one of them (no idea how to change the frequency of the listening devices or if they even support that)? I don't have any way I can reconfigure which IoX controls what given the HVAC is all on eisy and I've previously run out of Insteon nodes/scenes and my final insteon network plan has gotten substantially bigger since then. Thoughts?

On the device dashboard for a variable the top 3 pickers are under the properties header- value precision and startup value. Value is where is get that error- tried with variable dashboards of status commmand and default types. Below that under a command header is a blue button for value which will accept an arbitrary value. Since the property picker is first (and there and accepts a value) it’s what I always click on.