Unable to add POPP Smoke Detector with controllable Siren V1.2 (701486) to Homey Pro early 2023

[Basov]

Hello, I’m running into some issues while trying to add my POPP Smoke detectors. After performing the Z-Wave inclusion process I repeatedly keep getting the message “Something went wrong while communicating with the device. Please try again”.

I’d like to add a total of 4 detectors and so far, after many attempts, I’ve been able to add 1. The one that’s added works as expected and I’m able to control it via the Homey app. I’ll post screenshots below of the process and the messages I receive. Any help or tips to add the remaining 3 detectors would be greatly appreciated.

Components involved:

POPP Smoke detector (SKU: POPE701486) produced end of 2022.
Homey Pro early 2023 (received yesterday, latest batch with latest software).
POPP Homey app v3.2.8.

Kind regards,

Bas

[Caseda]

What’s the distance you are trying to include the sensor, anything more then 0,5 meter is probably the reason why it is failing.

[Basov]

I’ve tried adding them at longer distance (near their places at the ceiling) and I’ve walked over and placed right next to Homey Pro. In both situations I keep receiving the same message.

I wasn’t aware a small distance is a requirement while adding a device. That is good to know. Any future attempts I make will be right next to Homey Pro.

-edit-
Do I have to keep the already successfully added detector close as well? That one is 5m away in the kitchen.

[Caseda]

In theorie it should work on longer distances (if you have a very stable mesh), but it is just way more likely to fail with the amount of data Homey is requesting of the device.

5 Meter is on the farther range of Homey if you have no Routing devices (devices on mains power) which the smoke detectors aren’t if my memory serves me correct, but the already included devices don’t have to be nearby with adding another device to Homey.

So it all is depending on how good your mesh network is.

[Basov]

I’ll try it some more later today. I’ll come back here with my findings.

Thanks for the info so far

[Ranney]

Interesting. I can’t give any good advice here. But with some battery devices it helps here to pust the ‘connect’ button during the ‘connecting’ phase’ (On your picture shown as: ‘Please wait while your divide is being added…’) every few seconds to keep the device ‘alive’. Maybe something that is possible to try?

[Basov]

I’ve tried a couple of things, but no succes so far.

• Restart the POPP app on Homey Pro
• Reset the smoke detector to factory default before trying to add it
• Take out the battery and re-insert
• Have the 1 working detector close to Homey Pro while trying to add another one
• Repeatedly press the ‘include’ button to keep it awake during the process

An interesting note… the detectors do ‘talk’ to each other when the actual alarm turns on. That didn’t work before I had Homey Pro as the Z-wave hub. But they just don’t talk to Homey individually, so I can only find and control the 1 detector. (Or do I only get 1 button to control them all and not individually?)

Also, I’m new to Z-wave, so maybe I’m doing something wrong that seems basic to Z-wave users.

I’ll add some screenshots of the settings I can change for the 1 working detector

[Basov]

I’ve made a Z-wave log during an attempt to add a detector, maybe someone can see what is going wrong here. I’m also in contact with POPP support.

[2023-06-19T06:34:30.074Z] Command[1193] start: removeNode

[2023-06-19T06:34:30.093Z] Command[1193] status: removeNode, status: REMOVE_NODE_STATUS_LEARN_READY

[2023-06-19T06:34:39.412Z] Command[1193] status: removeNode, status: REMOVE_NODE_STATUS_NODE_FOUND

[2023-06-19T06:34:40.554Z] Command[1193] status: removeNode, status: REMOVE_NODE_STATUS_REMOVING_SLAVE

[2023-06-19T06:34:40.557Z] Command[1193] status: removeNode, status: REMOVE_NODE_STATUS_DONE

[2023-06-19T06:34:40.561Z] Command[1193] end: removeNode

[2023-06-19T06:34:40.566Z] Command[1194] start: addNode

[2023-06-19T06:34:40.579Z] Command[1194] status: addNode, status: ADD_NODE_STATUS_LEARN_READY

[2023-06-19T06:34:44.891Z] Command[1194] status: addNode, status: ADD_NODE_STATUS_NODE_FOUND

[2023-06-19T06:34:45.125Z] Command[1194] status: addNode, status: ADD_NODE_STATUS_ADDING_SLAVE

[2023-06-19T06:34:45.746Z] Command[1194] status: addNode, status: ADD_NODE_STATUS_PROTOCOL_DONE

[2023-06-19T06:34:45.759Z] Command[1194] status: addNode, status: ADD_NODE_STATUS_DONE

[2023-06-19T06:34:45.887Z] Command[1194] status: addNode, status: INTERVIEW_CC

[2023-06-19T06:34:45.893Z] Command[1195] start: sendData

[2023-06-19T06:34:45.894Z] [ProcessSendData]: To node: 51 with data: 0x86135e and txOptions: TRANSMIT_OPTION_ACK,TRANSMIT_OPTION_AUTO_ROUTE,TRANSMIT_OPTION_EXPLORE

[2023-06-19T06:34:45.927Z] Command[1195] end: sendData

[2023-06-19T06:34:45.934Z] Command[1194] status: addNode, status: INTERVIEW_CC_1_OF_15

[2023-06-19T06:34:45.936Z] Command[1196] start: sendData

[2023-06-19T06:34:45.937Z] [ProcessSendData]: To node: 51 with data: 0x861320 and txOptions: TRANSMIT_OPTION_ACK,TRANSMIT_OPTION_AUTO_ROUTE,TRANSMIT_OPTION_EXPLORE

[2023-06-19T06:34:45.994Z] Command[1196] end: sendData

[2023-06-19T06:34:45.995Z] Command[1194] status: addNode, status: INTERVIEW_CC_2_OF_15

[2023-06-19T06:34:45.997Z] Command[1197] start: sendData

[2023-06-19T06:34:45.998Z] [ProcessSendData]: To node: 51 with data: 0x861325 and txOptions: TRANSMIT_OPTION_ACK,TRANSMIT_OPTION_AUTO_ROUTE,TRANSMIT_OPTION_EXPLORE

[2023-06-19T06:34:46.037Z] Command[1197] end: sendData

[2023-06-19T06:34:46.044Z] Command[1194] status: addNode, status: INTERVIEW_CC_3_OF_15

[2023-06-19T06:34:46.046Z] Command[1198] start: sendData

[2023-06-19T06:34:46.046Z] [ProcessSendData]: To node: 51 with data: 0x861330 and txOptions: TRANSMIT_OPTION_ACK,TRANSMIT_OPTION_AUTO_ROUTE,TRANSMIT_OPTION_EXPLORE

[2023-06-19T06:34:46.087Z] Command[1198] end: sendData

[2023-06-19T06:34:46.094Z] Command[1194] status: addNode, status: INTERVIEW_CC_4_OF_15

[2023-06-19T06:34:46.095Z] Command[1199] start: sendData

[2023-06-19T06:34:46.096Z] [ProcessSendData]: To node: 51 with data: 0x861371 and txOptions: TRANSMIT_OPTION_ACK,TRANSMIT_OPTION_AUTO_ROUTE,TRANSMIT_OPTION_EXPLORE

[2023-06-19T06:34:46.127Z] Command[1199] end: sendData

[2023-06-19T06:34:46.134Z] Command[1194] status: addNode, status: INTERVIEW_CC_5_OF_15

[2023-06-19T06:34:46.135Z] Command[1200] start: sendData

[2023-06-19T06:34:46.136Z] [ProcessSendData]: To node: 51 with data: 0x861370 and txOptions: TRANSMIT_OPTION_ACK,TRANSMIT_OPTION_AUTO_ROUTE,TRANSMIT_OPTION_EXPLORE

[2023-06-19T06:34:46.167Z] Command[1200] end: sendData

[2023-06-19T06:34:46.174Z] Command[1194] status: addNode, status: INTERVIEW_CC_6_OF_15

[2023-06-19T06:34:46.175Z] Command[1201] start: sendData

[2023-06-19T06:34:46.176Z] [ProcessSendData]: To node: 51 with data: 0x861385 and txOptions: TRANSMIT_OPTION_ACK,TRANSMIT_OPTION_AUTO_ROUTE,TRANSMIT_OPTION_EXPLORE

[2023-06-19T06:34:46.217Z] Command[1201] end: sendData

[2023-06-19T06:34:46.223Z] Command[1194] status: addNode, status: INTERVIEW_CC_7_OF_15

[2023-06-19T06:34:46.225Z] Command[1202] start: sendData

[2023-06-19T06:34:46.225Z] [ProcessSendData]: To node: 51 with data: 0x861380 and txOptions: TRANSMIT_OPTION_ACK,TRANSMIT_OPTION_AUTO_ROUTE,TRANSMIT_OPTION_EXPLORE

[2023-06-19T06:34:46.258Z] Command[1202] end: sendData

[2023-06-19T06:34:46.265Z] Command[1194] status: addNode, status: INTERVIEW_CC_8_OF_15

[2023-06-19T06:34:46.266Z] Command[1203] start: sendData

[2023-06-19T06:34:46.266Z] [ProcessSendData]: To node: 51 with data: 0x86135a and txOptions: TRANSMIT_OPTION_ACK,TRANSMIT_OPTION_AUTO_ROUTE,TRANSMIT_OPTION_EXPLORE

[2023-06-19T06:34:46.297Z] Command[1203] end: sendData

[2023-06-19T06:34:46.304Z] Command[1194] status: addNode, status: INTERVIEW_CC_9_OF_15

[2023-06-19T06:34:46.309Z] Command[1204] start: sendData

[2023-06-19T06:34:46.310Z] [ProcessSendData]: To node: 51 with data: 0x861359 and txOptions: TRANSMIT_OPTION_ACK,TRANSMIT_OPTION_AUTO_ROUTE,TRANSMIT_OPTION_EXPLORE

[2023-06-19T06:34:46.349Z] Command[1204] end: sendData

[2023-06-19T06:34:46.356Z] Command[1194] status: addNode, status: INTERVIEW_CC_10_OF_15

[2023-06-19T06:34:46.357Z] Command[1205] start: sendData

[2023-06-19T06:34:46.357Z] [ProcessSendData]: To node: 51 with data: 0x861373 and txOptions: TRANSMIT_OPTION_ACK,TRANSMIT_OPTION_AUTO_ROUTE,TRANSMIT_OPTION_EXPLORE

[2023-06-19T06:34:46.388Z] Command[1205] end: sendData

[2023-06-19T06:34:46.395Z] Command[1194] status: addNode, status: INTERVIEW_CC_11_OF_15

[2023-06-19T06:34:46.396Z] Command[1206] start: sendData

[2023-06-19T06:34:46.397Z] [ProcessSendData]: To node: 51 with data: 0x861398 and txOptions: TRANSMIT_OPTION_ACK,TRANSMIT_OPTION_AUTO_ROUTE,TRANSMIT_OPTION_EXPLORE

[2023-06-19T06:34:46.428Z] Command[1206] end: sendData

[2023-06-19T06:34:46.435Z] Command[1194] status: addNode, status: INTERVIEW_CC_12_OF_15

[2023-06-19T06:34:46.436Z] Command[1207] start: sendData

[2023-06-19T06:34:46.437Z] [ProcessSendData]: To node: 51 with data: 0x861386 and txOptions: TRANSMIT_OPTION_ACK,TRANSMIT_OPTION_AUTO_ROUTE,TRANSMIT_OPTION_EXPLORE

[2023-06-19T06:34:46.468Z] Command[1207] end: sendData

[2023-06-19T06:34:46.475Z] Command[1194] status: addNode, status: INTERVIEW_CC_13_OF_15

[2023-06-19T06:34:46.476Z] Command[1208] start: sendData

[2023-06-19T06:34:46.477Z] [ProcessSendData]: To node: 51 with data: 0x861372 and txOptions: TRANSMIT_OPTION_ACK,TRANSMIT_OPTION_AUTO_ROUTE,TRANSMIT_OPTION_EXPLORE

[2023-06-19T06:34:46.508Z] Command[1208] end: sendData

[2023-06-19T06:34:46.515Z] Command[1194] status: addNode, status: INTERVIEW_CC_14_OF_15

[2023-06-19T06:34:46.516Z] Command[1209] start: sendData

[2023-06-19T06:34:46.517Z] [ProcessSendData]: To node: 51 with data: 0x861320 and txOptions: TRANSMIT_OPTION_ACK,TRANSMIT_OPTION_AUTO_ROUTE,TRANSMIT_OPTION_EXPLORE

[2023-06-19T06:34:46.548Z] Command[1209] end: sendData

[2023-06-19T06:34:46.555Z] Command[1194] status: addNode, status: INTERVIEW_CC_15_OF_15

[2023-06-19T06:34:46.556Z] Command[1194] status: addNode, status: INTERVIEW_MANUFACTURER_SPECIFIC

[2023-06-19T06:34:46.559Z] Command[1210] start: sendData

[2023-06-19T06:34:46.559Z] [ProcessSendData]: To node: 51 with data: 0x7204 and txOptions: TRANSMIT_OPTION_ACK,TRANSMIT_OPTION_AUTO_ROUTE,TRANSMIT_OPTION_EXPLORE

[2023-06-19T06:34:46.598Z] Command[1210] end: sendData

[2023-06-19T06:34:46.610Z] Command[1194] status: addNode, status: INTERVIEW_FIRMWARE_INFORMATION

[2023-06-19T06:34:46.611Z] Command[1211] start: sendData

[2023-06-19T06:34:46.612Z] [ProcessSendData]: To node: 51 with data: 0x8611 and txOptions: TRANSMIT_OPTION_ACK,TRANSMIT_OPTION_AUTO_ROUTE,TRANSMIT_OPTION_EXPLORE

[2023-06-19T06:34:46.651Z] Command[1211] end: sendData

[2023-06-19T06:34:46.660Z] Command[1194] status: addNode, status: INTERVIEW_ASSOCIATION

[2023-06-19T06:34:46.661Z] Command[1212] start: sendData

[2023-06-19T06:34:46.661Z] [ProcessSendData]: To node: 51 with data: 0x8505 and txOptions: TRANSMIT_OPTION_ACK,TRANSMIT_OPTION_AUTO_ROUTE,TRANSMIT_OPTION_EXPLORE

[2023-06-19T06:34:46.701Z] Command[1212] end: sendData

[2023-06-19T06:34:51.802Z] Command[1213] start: sendData

[2023-06-19T06:34:51.802Z] [ProcessSendData]: To node: 51 with data: 0x8505 and txOptions: TRANSMIT_OPTION_ACK,TRANSMIT_OPTION_AUTO_ROUTE,TRANSMIT_OPTION_EXPLORE

[2023-06-19T06:34:51.843Z] Command[1213] end: sendData

[2023-06-19T06:34:56.944Z] Command[1214] start: sendData

[2023-06-19T06:34:56.945Z] [ProcessSendData]: To node: 51 with data: 0x8505 and txOptions: TRANSMIT_OPTION_ACK,TRANSMIT_OPTION_AUTO_ROUTE,TRANSMIT_OPTION_EXPLORE

[2023-06-19T06:34:56.984Z] Command[1214] end: sendData

[2023-06-19T06:35:01.985Z] Command[1194] end: addNode

[2023-06-19T06:35:04.008Z] Command[1215] start: removeNodeAbort

[2023-06-19T06:35:04.010Z] Command[1216] start: addNodeAbort

[2023-06-19T06:35:04.011Z] Command[1215] end: removeNodeAbort

[2023-06-19T06:35:04.012Z] Command[1216] end: addNodeAbort

[2023-06-19T06:35:26.303Z] Command[1217] start: getNetworkTopology

[2023-06-19T06:35:26.420Z] Command[1217] end: getNetworkTopology

[2023-06-19T06:35:26.465Z] Command[1218] start: getFailedNodes

[2023-06-19T06:35:26.466Z] Command[1219] start: isFailedNode

[2023-06-19T06:35:26.482Z] Command[1219] end: isFailedNode

[2023-06-19T06:35:26.484Z] Command[1218] end: getFailedNodes

[Undertaker]

Have you checked Homey Developer Tools to see if you have any ghost devices?

• Homey Developer Tools
• Zwave
• Look in the column on the right to see if you have an unknown device.
• If so, go to the right of the line and click on the 3 dots.
• Click on Test and wait until the error message appears.
• Click on the 3 dots again and click remove

The ghost device should now be deleted. Restart Homey and try to register your devices again.

[Basov]

I will try that @Undertaker. Meanwhile I’ve got a response (really quick) from POPP support:

vielen Dank,

We have looked at this again and can confirm the problem.

Unfortunately, we have no insight into the inclusion process. Therefore, I ask you to create a Homey error report and send it to Homey.

Maybe they can see where the problem is.

We will investigate the problem further, but I suspect it is still the existing problem from the older versions. We know that there was a problem in RC 105, but this should have been fixed with RC 110.

It seems it’s a known error en requires a fix from Athom. I’ll have a look and figure out how to produce an ‘error report’.

[Basov]

@Undertaker No ‘ghost’ or unknown devices, so I guess I’ll have to wait for Athom to fix it.

[Ranney]

Just curious, I have 6 ‘ghost devices’ but not deleted them because they are ‘responsive’. When testing, they respond immediately.
I thought it is not a problem because everything is working fine. Is it a problem to keep them or should I find out what these devices are and remove/re-add them ?

[Undertaker]

Normally, unknown devices are devices where something went wrong during inclusion. Often there is the problem that these devices cannot be re-registered as long as the device is still entered in the Zwave table.
Please try a “Heal” on the devices when you press the 3 dots.

[Ranney]

Interesting! I’ve tried the heal function. The test function is working. The Heal function is returning an error. Any Idea what is wrong? Interesting is that they all are working and responding.

[Undertaker]

It is not easy to identify the unknown devices. Under Devices, you can search for the defective nodes. These devices definitely have a problem, otherwise Homey would display them with the assigned name. Under Driver, you may be able to assign them.

Otherwise, your only option is to delete a device and then search for the device that has disappeared in the Homey app. You can also see when a flow is marked as defective.

A good tip is:
If a device causes problems when you include it, check immediately in Developers to see if there is an unknown device.
I can’t say why your devices still work. But it is certain that they have a problem.

[Ranney]

Thanks for your time and help! I was searching for them but I cannot identify what devices have the problem. All Z-Wave devices are working fine. In de Device field, they all have a name. Only in the Z-Wave screen there are unknown devices. Any idea how to match them?

They are also reported as ‘Unreachable’ in the overview script. But… Every device is working and reporting

Ps. just counted ALL my Z-wave devices. There are 52 Z-Wave devices and… all unresponsive devices are responding when I do a test… and… 23 Router, 28 Battery, 7 Unreachable, 9 Unknown is more that 52…

----------------- Devices -------------------

8 Virtual devices

0 Infrared (database) devices

51 Z-Wave devices (46 Unsecure, 5 Secure (S0), 0 Secure (S2 Authenticated), 0 Secure (S2 Unauthenticated), 23 Router, 28 Battery, 7 Unreachable, 9 Unknown)

35 Zigbee devices (16 Router, 19 End device)

209 Other devices

303 Total devices

[Undertaker]

Unfortunately, this is where my knowledge ends. Perhaps someone else will come forward who can explain this phenomenon.

[Basov]

Interesting stuff @Ranney & @Undertaker. I’m learning more and more about Z-wave.

I’ve asked for a bit more detail than ‘we can confirm the problem’ and I’ve received the following from POPP support. (Once again really fast reply, kudos for their support)

”Hi Bas

Yes, inclusion is currently not possible [editorial: on Homey Pro 2023]. However, it works in the Bridge and Homey Pro 2019 without any problems, so we do not assume a driver problem here. We had already contacted Mt Homey about this in previous RC versions, but unfortunately no permanent solution seems to have been found yet.

Best regards”

So anyone else with POPP Smoke detectors and Homey Pro 2023… just wait for now. Nothing we can do except for getting a support ticket at Athom.

I do think it’s weird I was able to add one though…

[Caseda]

Unreachable and unkown nodes are not part of the count (51 in your case).
A router or battery device can be unreachable, it is just an extra flag that Homey adds if it didn’t receive a signal back (in time) for 3 tries, so would be weird to count those.
Unkown nodes are also not part of that count as they are 99.9% of the time just a lingering register on the Z-Wave chip, but not actually a device.

[Ranney]

Good to know and thanks for the info! Any idea why these device are ‘working’ (/responding to an test on the developer page)?
I’m not missing any devices and if I count all my z-wave devices, then it is the sum of the routers and battery devices. Not more than that