Yesterday, my virtual switches quit responding. I tried rebooting the hub, with no improvement. I reverted to 1.0.9.117 and it fixed the problem temporarily and they quit responding. I re-updated the hub to 1.0.9.118 and they quit working. I re-reverted to 1.09.117 and they worked briefly and then stopped. The virtual switches are not logging any information and their status does not change. I tried changing the device type around to see if that would fix it without luck. I also restored a backup from prior to this glitch starting in case I changed something that created a conflict.
Any suggestions? It's strange that this just started to happen.
I have them tied to picos and use them on dashboards with rule machine to change the state of all the lights in the room for instance. They are no longer working on the dashboards. If I try to change the state directly on the HA UI, the state remains static.
can you try something?
take one of your Picos, then create a button controller in the button controller app to control your virtual switch, button 1, virtual switch on, button 5 (or whatever depending on the pico you're using) virtual switch off.
Don't attach any automations to this switch right now.
Put this switch in your dashboard, lets just play with this virtual switch and make sure it's working as expected first.
Interesting.... actually, I had some of the picos set up to control some lights directly and not just through virtual switches and those are not working either. I did try to set up a pico from scratch with button controller and I could not get it to trigger either a virtual switch or a physical device, with the exception of my Lutron dimmers (of course - Lutron blows me away) However, the pico does appear to be logging properly.
It looks like the none of the device states are updating on the Hubitat UI. I can change turn on/off bulbs, change colors, but the device state does not actually change on the device page.
Ok, let's start with the Hubitat picos, go to the details page for one of them, push a few buttons, does the current state for pushed update correctly?
What log would that be?, can you post a screen shot?
Also open your lutron telnet driver and hit initialize, you should see a log entry that says "Telnet connection to Lutron Smart Bridge established"
how many lutron telnet devices are in your system?, there should only be one for each bridge, and I see 8 separate telnet devices in the logs responding to that one pico.
I see where I have messed this up. I have 17 Lutron devices on Hubitat. Very early on in the game, to add a Lutron device, I would use the create a new Caseta integration in the parent app instead of using the child app. I see now where that was incorrect. Once Hubitat upgraded to add the ability to add Lutron devices via a list, I added all new devices to the list. So that would explain the 8 telenet instances on my log .
I will fix my Lutron setup and see if that improves things. I'm also going to investigate @SmartHomePrimer post about deleting devices without removing from the app. The tricky part with troubleshooting @SmartHomePrimer's observations is figuring out which is the problem device/app when you have many devices/integrations and you like to tweak things all of the time. I guess that's why a few folks get a second hub.
You can safely remove all of them without figuring out which is which. Then simply open the Lutron Integration app and hit Done. It will recreate the Lutron Telnet device.
.
