Javi

Not related, but at the same time difficult to diagnose if running a beta version that has been replaced. Check if they still exist in Admin Console, if they do then there is a connection or some other issue.

Not a bug, this is the new implementation. For i3 the load and the buttons can be detached or attached to any other button. so Load + Buttons + flags. delete and re-add the others to split the load out of A

I don't think so, only the basic firmware upgrade is needed everything else is set from eisy. Thank, odd that it was not default

Fix is live in staging

Firmware test completed Pull ID: /universaldevices/udi/pull/24

Replicated added issue: "Variable UOM Selection shows UOM ID instead of UOM Name". ID: /eisy-ui/issues/135

Oh, yes. This was accidentally removed when Right Click > Configuration was split into two pages. It will be Right Click > Node Info. Already fixed but not yet pushed to staging. e.g. still missing in Node Info

I can't replicate, is this the latest frimware?

How is this done in the Admin Console?

This topic is specifically for The notification API. All support tickets are referred to the Notification Plugin. Network Resources are included in eisy-ui but are, and have always been, self managed. The issue with the notification API and the deprecated concern, is that our wiki shows the method as deprecated only to be used with 994, as 994 doesn't support plugins. This is only in the context of the notification API

on our list

If there are no issues I would ignore, this is a warning not an error. This will likely be changed to be the same as the admin console, no heads up notification, just a badge next to the node.

Yes, it is on our list.

I still recommend Jim's Plugin, unless you just want to own your own creation. Before AI, I estimated it would take me 1-2 weeks to create the same with all of the redundancy (retires/loops/group lookups/non-indexed group stabilization) . With AI, it would likely take a day maybe 2 when accounting for bug fixes plus ~$30 in credits. Much more expensive in both time and money than the ready made solution.

Thanks, I think the dialog will need to be changed to match that timeout parameter. I could not replicate on my side as I have no test cases. Added issue to synchronize the user specified timeout with the dialog timeout. Z-wave inclusion dialog needs to match Z-Wave Timeout. ID /eisy-ui/issues/134