Announcement

Collapse
No announcement yet.

Control and Status change after a reboot??

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Control and Status change after a reboot??

    w.vuyk
    How can I stop the plugin from changing my control/status text and graphics ?
    I added a blinds control to Alexa.
    Alexa sees it as a light.
    Now after a reboot, the text and graphics are changed to a lights text and graphics.
    Happened twice so far.

    This is it before a reboot:

    Click image for larger version

Name:	status correct.png
Views:	146
Size:	68.7 KB
ID:	1590923


    And now after rebooting:

    Click image for larger version

Name:	blind.png
Views:	111
Size:	67.2 KB
ID:	1590924


    I've rebooted plenty before adding it to Alexa and it never changed, now it does.
    How do I stop this?

    #2
    Make sure this is not set?

    Click image for larger version

Name:	image.png
Views:	122
Size:	107.5 KB
ID:	1590928

    Comment


      #3
      That's off in the plugin and off in the devices.

      Comment


        #4
        I think there is a differnt issue going on here. The plugin does not recognize the blind as being a blind and approaches it as a light.
        Could you post the JSON on the properties of the device in the JowiHue tab? Just copy the JSON text, no need for an image?

        Will need to check on that here.

        Wim
        -- Wim

        Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData

        1210 devices/features ---- 392 events ----- 40 scripts

        Comment


          #5
          Originally posted by w.vuyk View Post
          I think there is a differnt issue going on here. The plugin does not recognize the blind as being a blind and approaches it as a light.
          Wim
          I agree, but this only happened when I added it to Alexa, which only sees it as a light.
          Before that, it was seen as a "Window Covering Device" in the plugin.


          **************************** Object info *****************************
          {
          "capabilities": {
          "alerts": [
          "none",
          "select",
          "lselect"
          ]
          },
          "config": {
          "groups": [
          "1"
          ]
          },
          "etag": "447d4dba78ebfd67e4da6dfcb63dd0f0",
          "hascolor": false,
          "lastannounced": "2023-02-07T07:41:35Z",
          "lastseen": "2023-02-07T21:46Z",
          "manufacturername": "LUMI",
          "modelid": "lumi.curtain.acn002",
          "name": "Window covering device 5",
          "state": {
          "alert": "none",
          "bri": 0,
          "lift": 0,
          "on": false,
          "open": true,
          "reachable": true,
          "speed": 2
          },
          "swversion": "0.0.0_0030",
          "type": "Window covering device",
          "uniqueid": "54:ef:44:10:00:4a:4e:e4-01"
          }
          ************************* End Object info ***************************​

          Comment


            #6
            I will check in the plugin, initially I would expect the plugin to recognize this correct. Will be back on this
            -- Wim

            Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData

            1210 devices/features ---- 392 events ----- 40 scripts

            Comment


              #7
              Any update on this?

              Along with these also actually:

              https://forums.homeseer.com/forum/hs...82#post1588782

              https://forums.homeseer.com/forum/hs...40#post1589540

              Comment

              Working...
              X