Have you tried deleting the entire app and recreating it?
See the PM I sent you.
1 Like
I stopped digging when going back fixed most the issues. Ill check my Pm
All legacy rules are blocked from editing. 2.2.9 is garbage! I can no longer access my Pico remotes and .140 broke all my dashboards! It is a nightmare !
I went from 2.2.8 to 2.2.9 and lots of things are broken now. No editing of old rules, the dashboards no longer load and my Pico remotes no longer work. The mobile app is also now broken as well.
If you can stick with one thread to discuss the issues you’re having, particularly one in which staff have already asked for follow up info, you might be able to get a quicker resolution to your problem.
2 Likes
There was a general 2.2.9 but I am having problems finding it.
See the link in my last post.
1 Like
Not true.
Far as I am aware, they made no changes to Lutron stuff. Mine is working fine here, and there are no other reports of this that I can see.
Again, there are no other reports of this, and mine is working fine here.
There is something unique to your setup that is causing your problems.
2 Likes
You keep making sort of inflamed statements about things being broken, but without anything to support them. From what I can tell, all rules are still editable. Could you perhaps show us a screenshot of what you are talking about? Could you show a screenshot of the device page for your pico remote? Is it possible the IP address of your Lutron system changed? Had you assigned a static IP for it? Lutron Smart Bridges are known to change IP address unless a static IP is assigned. If that happens, then nothing Lutron will work in Hubitat.
6 Likes
Have you seen what happens if you roll back to 2.2.8? Go to hub-ip:8081, then Restore Previous Version. Does everything then work as you expect?
2 Likes
That WHY I am posting this. 2.2.9.140 introduced MAJOR bugs. Rolling back to 2.2.9.130 fixed at least 3 of them.
2.2.9.140 disabled the mobile app from finding the hub and it also ruined the dashboards so they would not load. Not cure if editing is still disabled fro Legacy Apps... ... Yep, rolling back to 2.2.9.130 fixed that too. I can now edit them again. That is three major bugs you have created. Not sure of it fixes not being able to access my Pico Remotes. I may have to roll back even further. I few device s seem to need pairing again but at least the system is working again. Only 2 new items to add, I am glad I have not installed more yet.
2.2.9.130 fixed most, I have not have not tested the Picos, only the mobile app, dashboards and I can now edit legacy rules again. 3 big problems fix by going back to 2.2.9.130 !!!
2.2.9.130 fix a lot, it was worth having to re-pair three of newly added Z-wave devices.
A rollback fixed it so I can no longer do so.
It may take a little bit of patience on your part to get this sorted out. 2.2.9 is not broken for most users, so we need to figure out what is going on with your hub. Would you please do these steps:
- Download a backup of your hub from Settings / Backup and Restore.
- Update to 2.2.9.142.
Report back as to what issues remain after you do that.
1 Like
I will check on the Lutron bridge ... ... Hmmm, I am not seeing it on the network map but ... ... It seems that during a recent power outage the Lutron Bridge Ethernet plug may have been jarred just enough to have the connection fail ... ... yep, it now appears. I still needed to roll back to 2.2.9.130 to fix the other three problems. Confirmed, all Lutron devices now work as before. It was a separate issue created by my needing to shut power off to install on of the three devices (the GE motion sensor switch for hall lights) I added and will now have to do again since they were probably installed after 2.2.9.130.
2.2.9.130 fixed everything
If you didn't restore an old DB, they are still there. Rolling back a build does not change your DB.
I think that if you do the 2 steps I gave above, you will find that everything is working. If not, there is one more step that might be needed.
