(Last Updated: October 5, 2020)

Recreate Zway device in Openluup



  • If a zway device have been manually deleted in openluup, What would be the right way to recreate it, or re-sync with the z-way-server?



  • Luup restart?



  • Currently it does not resync with a luup restart.



  • I'm surprised. What's in the logs?



  • Oh, no wait. I misunderstood, perhaps. You mean that you have deleted the Zway plugin?



  • When I finished creating the new z-way-server setup. I went back to openluup and deleted an old ZWay device (not the ZWay plugin itself) that was there from the old z-way-server setup and re-login the ZWay plugin into the z-way-server, everything got transfer over except that one device.

    This happened in another openluup setup. If I manually delete a ZWay device from openluup and then reload the luup engine or getting the ZWay plugin to login to a new z-way-server, z-way-server devices that matches the device id of the device that was deleted in openluup won't get created.



  • The device isn’t just in Room 101?



  • no. not in there either.



  • Which version of openLuup and the ZWay plugin?



  • Openluup 2020.04.03
    Z-Way 20.7.14



  • Why are you deleting devices?



  • I had an old device from an old z-way-server and I didn't want to start a brand new user_data. I even try to connect the openluup zway plugin with the new z-way-server without deleting the device but the old device remained as the old device type and did not update to what the new z-way-server had under that id. so then I tried deleting it to never see it again... It has happen on two different setup I'm currently migrating.



  • I am unable to reproduce this.

    I have deleted a ZWay child device, and restarted. During the ZWay plugin initialization, it notices the missing device, recreates it (with the same numbering) and requests another reload, after which the device is there again, as it should be.

    How are you viewing your devices? AltUI? Have you done a browser refresh??

    Here's the log of the ZWay plugin starting up and making a new device (#20050)

    2020-10-03 11:13:33.324 openLuup.scheduler:: [23] ZWay device startup
    2020-10-03 11:13:33.324 luup_log:23: ZWay: v20.7.14
    2020-10-03 11:13:33.382 luup_log:23: ZWay: HomeId: c5d860ea
    2020-10-03 11:13:33.382 luup.variable_set:: 23.urn:upnp-org:serviceId:altui1.DisplayLine1 was: 52 vDevs, 24 zNodes now: #hooks:0
    2020-10-03 11:13:33.382 luup.register_handler:: global_function_name=HTTP_Z-Way_23, request=z23
    2020-10-03 11:13:33.421 luup.set_failure:: status = 0
    2020-10-03 11:13:33.421 luup.variable_set:: 23.urn:micasaverde-com:serviceId:HaDevice1.CommFailure was: 0 now: 0 #hooks:0
    2020-10-03 11:13:33.421 luup.variable_set:: 23.urn:micasaverde-com:serviceId:HaDevice1.CommFailureTime was: 0 now: 0 #hooks:0
    2020-10-03 11:13:33.481 luup.variable_get:: No such device/serviceId/name 20050.urn:akbooer-com:serviceId:ZWay1.Children
    2020-10-03 11:13:33.482 luup.create_device:: [20050] D_MotionSensor1.xml / / D_MotionSensor1.json (urn:schemas-micasaverde-com:device:MotionSensor:1)
    2020-10-03 11:13:33.482 luup.variable_set:: 20200.urn:upnp-org:serviceId:altui1.DisplayLine1 was: Humidity:1 Light:1 Motion:1 Temperature:1 now: Humidity:1 Light:1 Motion:1 Temperature:1 #hooks:0
    2020-10-03 11:13:33.482 luup_log:23: creating device numbers: [20170,20084,20080,20213,20040,20180,20140,20182,20100,20020,20050,20200,25001,25002,25003,25004,20085,20215,20214,20083,20212,20211,20210,20081,20190,20110,20181,20082]
    2020-10-03 11:13:33.482 luup_log:23: ZWay: Room 101: [20002] Everspring Dimmer (2.0)
    2020-10-03 11:13:33.482 luup_log:23: ZWay: Room 101: [20019] TKB Home Switch (#19)
    2020-10-03 11:13:33.482 luup_log:23: ZWay: Room 101: [20004] node #4
    2020-10-03 11:13:33.482 luup_log:23: ZWay: Room 101: [21001] Aeon Labs Temperature (9.0.49.1)
    2020-10-03 11:13:33.482 luup_log:23: ZWay: Room 101: [20005] node #5
    2020-10-03 11:13:33.482 luup_log:23: ZWay: Room 101: [21002] Aeon Labs Luminiscence (9.0.49.3)
    2020-10-03 11:13:33.482 luup_log:23: ZWay: Room 101: [21003] Aeon Labs Humidity (9.0.49.5)
    2020-10-03 11:13:33.482 luup_log:23: ZWay: Room 101: [21004] Everspring Humidity (10.0.49.5)
    2020-10-03 11:13:33.482 luup_log:23: ZWay: Room 101: [20008] node #8
    2020-10-03 11:13:33.482 luup_log:23: ZWay: Room 101: [21005] Chromatic Technologies General purpose (5.0.48.1)
    2020-10-03 11:13:33.482 luup_log:23: ZWay: Room 101: [20009] node #9
    2020-10-03 11:13:33.482 luup_log:23: ZWay: Room 101: [21006] Fibar Group General purpose (18.0.48.1)
    2020-10-03 11:13:33.482 luup_log:23: ZWay: Room 101: [20010] node #10
    2020-10-03 11:13:33.482 luup_log:23: ZWay: Room 101: [21007] Aeon Labs General purpose (9.0.48.1)
    2020-10-03 11:13:33.482 luup_log:23: ZWay: Room 101: [20011] Fibar Group (11.0.0) Button
    2020-10-03 11:13:33.482 luup_log:23: ZWay: Room 101: [20014] Switch (14.0)
    2020-10-03 11:13:33.482 luup_log:23: ZWay: Room 101: [20018] node #18
    2020-10-03 11:13:33.482 luup_log:23: ZWay: Room 101: [20017] Switch (17.0)
    2020-10-03 11:13:33.482 openLuup.luup:: device 23 'ZWay' requesting reload



  • I can second AK in saying I can't reproduce this. Deleting the device on openluup + luup reload has actually been the mechanism we used to reset configuration of errant devices because it recreates it.



  • I'm reinstalling everything again. I'll report back in a few.


Log in to reply