Forum wide moderators
Oh boy. They even sent some invoices, as "courtesy previews". People are entertained in the old place...
If you need a way to quickly migrate from Vera to Home Assistant Zwave key, read here:
https://smarthome.community/topic/1590/how-to-migrate-from-vera-to-zwave-me-and-then-zwavejs-in-2024
I used Zwave.me as an intermediate step, but I think anything on Zwave series 500 should work.
It appears that Ezlo is going to new levels of paid subscription for cloud services supporting Vera hubs. I have to congratulate them. It will soon be 8 years since Ezlo acquired Vera, and despite their purported financial and "intellectual" capital, they have to date not produced a viable full replacement for Vera. Now they are going to charge extra for services for a platform that they stopped updating years ago.
If you know anyone who hasn't yet fully moved on from Captain Ahab's White Whale Chase, please remind them that my Decouple project is still up on Github to decouple a Vera Plus/Secure/Edge from Vera/Ezlo's cloud services. Veras have been said to misbehave when they can't reach the mother ship.
I have also written my first new Vera plugin in... six years? more?... the AlertPushover project will send Vera hub alerts to Pushover, so you can still get messages generated by your Vera hub without paying for Ezlo's cloud service. It's crude but functional (i.e. better than nothing/worth every penny paid).
These two projects won't replace the functionality of their cloud service and app for those who need those things. But any that don't, this may help bridge the gap. Hopefully these stragglers who have waited so long and been disappointed so often will get the idea that it's time to move on.
@CatmanV2 A subsequent (to the prior post) respin of build 26177 fixed multiple profiles as well, so you're good either way.
I came here as I was seeing the same Telegram behaviour. I only have one profile. so am happy that the fix will resolve it for me
C
That's a bug in Maker API... it's sending updates for a device that isn't enumerated for export. You can safely ignore those messages.
Users on bare-metal installs... a security fix in nodejs v24.17 inadvertently broke a dependency of Reactor. This version of nodejs is therefore not compatible with Reactor. If you are using it, please upgrade to v24.18.
@wmarcolin I'm still looking at your Telegram issue. Now that I know nodejs v24.17 is a problem, I will post a note for it. Apparently the same change that broke v24 was also made to v22, so I'm trying to identify/confirm that version as well.
Ha!
And... it's a known regression, with a specific fix applied to v24.18, so confirms all.
Onward!!!
OK. Here it is... I switched my nodejs to the same v24.17 you are using... and my system broke! Same behavior as yours.
Upgrade your nodejs to v24.18. Whatever was broken in 17 seems to have been fixed for 18.
