@reneboer, thanks for comparing notes. Your log looks similar to what I am seeing but with a different root cause. I believe the firmware maps product attributes to a device-shim script and from your logs, it seems that the firmware doesn’t know about your device or have the mapping. Sounds like the team is on it so time will tell. Maybe your idea of re-including is a good one? (edited, looks like you posted positive results while I was typing)
Did that as soon as it hit the wild and before reporting that the issue still exists.
Section: eZLO Innovation
Description: Just firmware-common-git_version package
Absolutely. The only barrier is that in the most recent Vera Plus legacy firmware update lost a device that I need to recover/resurrect before messing with my network fabric. I’ll try to knock this off in the next day or so.
Sure - here is a region bug that I reported and still exists in 1.0.16.
And here is the one that we are discussing,