aasmundbo
commented
3 years ago Hi, the Namron app @fiLLLip started (this repo) is no longer in active development.
Namron actually took over the app a year or more ago. Their code is closed and I’m not sure where bugs should be filed (off the top of my head).
It’s unfortunate that Namron took over the Homey app if they are not maintaining it properly.
@fiLLLip, is your Namron app still visible from Homey’s “App Store”? Maybe removing it is a good idea to avoid confusion ..?
fiLLLip
Hello, Since May 2020 I have had an operational homey pro setup with namron z-wave dimmers (and other equipment) delivered from you. During the period I have experienced both software and firmware upgrades on both namron and homey devices. Virtually every time you upgrade software on either homey or namron devices, a dimmer fails. But it does not have to be associated with software updates, this happens completely out of the blue without any change in the network (wifi / mesh / power grid). Most of the time it is sufficient to reset the dimmer and then put it back in the homey, but sometimes (on 3 occasions) this has not worked either, then I have found faults on dimmers and replaced these on warranty. This is all well and good, but it cannot be the case that one is dependent on an electrician or "special competence" to get light in the bulbs; for example, if I am traveling and the lights do not come on, then neither the children nor the wife with the system can do anything to start the lights again. If the dimmer must be replaced, we need an electrician. This simply does not work. in addition, all flows (automation) must be recreated every time a dimmer fails, this is very frustrating and cannot be like that. Now, I have spent a lot of time online/ on forums to troubleshoot this, it seems to be associated with congestion on the mesh network caused by namron z-wave in secure mode. I chose to go for z-wave according to Elektroimportøren’s recommendation, this was perhaps premature I see now in retrospect (but I did not have enough knowledge about the technology in the summer of 2020 and therefore listened to professional advice from Elektroimportøren). I see that several have had all their z-wave units changed to zigbee from namron, this under warranty from Elektroimportøren. This can certainly be a solution for me as well, but this also involves a lot of work and effort to achieve. Homey pro is on the latest version, 7.1.3 - Namron is in v 2.2.9 (updated 4 days ago, at the same time as the update several zwave dimmers fell out and it is not possible to reset and then pair again). The same thing happened with the previous namron update, the previous namron version was additionally updated with a hotfix beta due to namron switches becoming unreachable with the previous version. In addition, there is a message on some namron devices that these will probably not be supported in the future (homey message)
homey.app is missing 1 node as I do not have reserves and have not paired up the last node / dimmer again as it can not be paired. It can turn lights on and off by pressing reset, but does not respond to pair commands. Common to zwave namron nodes that fail and become unreachable is that the route goes via a node that does not exist (For example a case where the node that fails goes via node 4 as the last known route ... 4 does not exist and has never done it in homey layout. Possibly this is reserved node id?) Here are several who experience the same problem, these are just some of the many threads I have trawled over the past year. The conclusion seemed to point to Namron flooding the zwave network (possibly this is caused by the code job in namron, who knows ...) https://www.hjemmeautomasjon.no/forums/topic/7073-mye-tr%C3%B8bbel-med-homey-namron-z-wave/ https://community.athom.com/t/add-z-wave-device-non-secure/12406/43 https://community.home-assistant.io/t/why-the-heck-are-my-z-wave-devices-sometimes-unavailable-after-startup/219925/5
The more I read on forums, the more things suggest that it is flooding from the zwave devices in secure mode that is the cause. Those who report similar issues get rid of the problem in unsecure mode ("hack" json config) or by using other zwave nodes. A bad mesh network at the end user must then be based on other noise on the band (868mhz) or heavy constructions that stop the waves, possibly large distances. Nodes and homey are located only on the same floor, wall constructions are exclusively 4-inch three-pillar walls with conventional chip construction; that is, not constructions that should have a significant effect on the wavelength for zwave mesh. Of apps on homey, it is quite "pure" - that is, relatively few and well-known apps. Looking forward to a response regarding these issues and hope this can be resolved soon.
Best regards.