forum

I have a Fibaro door sensor FGK-10x, included securely, to monitor a garage door. Every couple of weeks or even months, the sensor acts up and remains stuck in "open" mode. Upon closing it briefly hits "closed", then quickly (1 s) falls back to "open". It is independent...

I think the network key might be stored as "networkKey" in this file: /opt/z-way-server/config/zddx/YOURHOMEID-DevicesData.xml You can see YOURHOMEID at http://IP:8083/expert/#/network/controller It would be nice to get a confirmation on this, and also if other keys in this file are crucia...

Am I free to put additional variables into "self"?
Anything to watch for when doing this?
Any other way to have instance variables across trigger invocations?

Edit: removed some banter.

Thanks again for hinting to MxInfo, it help me identify a whole bunch of zombie devices in the config db. It seems most of them came from past partial-then-failed inclusions, but also a number of dummy devices and condition switches from old automation setups of mine. Not really sure how they kept l...

Thanks for all the replies - I was on the road so I couldn't keep up here. No it's not a big issue and in fact I had already hidden that device so it only appears in the low-level device table. It's more a house-keeping thing - databases should be clean and only contain relevant data I suppose.

I had found it already in this list, but what to do with this information? The entry is indeed lacking the creatorId key, and the id is ZWayVDev_zway_Remote_29-0-0-B.

I have a device which I think was previously created as a dummy device instance. It is assigned to a room. When I click the little gear icon on the room's dashboard, the devices config pages is shown. But in "Generated by App:" there is only the gear icon, and when I click it I get the &qu...

During my first attempts with this I also say multiple notifications (but not as many as you) - ultimately the problem must be looked for in your rules, which for some reason or the other probably gets triggered repeatedly. You can check the log to verify that the notification app has been triggered...

As a quick follow up: great suggestion, after re-interviewing that device the error hasn't popped up again. Before that I showed up reliably every 20 minutes. Once more, thanks!

Thanks, I'll try that!