Ring doorbell

Hey Angelo, see my post above, try that sequence!

Here is follow-up on ring-mqtt message board: https://github.com/tsightler/ring-mqtt/issues/240#issuecomment-905974725. In short, discovery in the current configuration does not work reliably


I’ve noticed that my things go and stay offline or various not online states when I restart OpenHAB until I then restart ring-mqtt but they all seem to work anyway. I bet that’s part of the same problem too, but I think fixable with a rule on startup

1 Like

What would the rule do, terminate ring-mqtt instance and create a new one?

According to the GitHub issue you linked, all we need to do is publish offline and online messages to the homeassistant/status topic to have it re send the config messages so that’s all we should need to do if I understand properly

edit:
Here’s the rule I put together that does just that. Running it manually forces ring-mqtt to re-send all the config topics as well

triggers:
  - id: "1"
    configuration:
      startlevel: 100
    type: core.SystemStartlevelTrigger
conditions: []
actions:
  - inputs: {}
    id: "2"
    configuration:
      type: application/python
      script: |-
        mqttActions = actions.get("mqtt","mqtt:broker:mqttBroker")
        mqttActions.publishMQTT("homeassistant/status", "online")
    type: script.ScriptAction

Also, while the ring-mqtt doesn’t appear to listen for “offline” on the homeassistant/status topic, I configured my mqtt broker to send it anyway out of caution
HASSOffline

1 Like

Now if I could only get my auto configured ring locks to stop throwing this in the log that would be great

[ab.binding.mqtt.generic.ChannelState] - Command 'LOCKED' not supported by type 'OnOffValue': No enum constant org.openhab.core.library.types.OnOffType.LOCKED

Setting a map on the channel or not having the channel linked at all doesn’t seem to make a difference and it still reports anyway

Not only locks, I am getting a very similar message from window/door sensors:

[WARN ] [t.generic.ChannelStateTransformation] - Executing the JINJA-transformation failed: An error occurred while transformation. Argument named 'default_value' is required but missing for filter default
[WARN ] [ab.binding.mqtt.generic.ChannelState] - Command ' OFF ' not supported by type 'OnOffValue': No enum constant org.openhab.core.library.types.OnOffType. OFF

Any thoughts?

How is that channel configured ?

Somehow you get an OFF command with leading space which cannot be transformed


Given that channels and maps are fully auto-discovered, it implies that it’s either (a) issue with OpenHab discovery process of HomeAssistant elements, or (b) ring-mqtt does not provide the right specification for it’s channels


This is perfect!

I’ve tried the following:

  • Not having the channel linked to anything at all
  • Having the channel linked to a string item
  • Having the channel linked to a switch item / default profile
  • Having the channel linked to a switch item / map profile (map file contains LOCKED=ON UNLOCKED=OFF)

They all throw the “Command ‘LOCKED’ not supported by type ‘OnOffValue’: No enum constant org.openhab.core.library.types.OnOffType.LOCKED” into the log periodically

The channel itself is auto configured like this:
ChannelConfig1
The full text that runs off the side for the bottom is this (UIDs partially redacted)

{"name":"Front Door Lock","unique_id":"xxxxxxxx-db591e2a5fcc","availability_topic":"ring/xxxxx/alarm/xxxxx-9bc9-db591e2a5fcc/status","payload_available":"online","payload_not_available":"offline","state_topic":"ring/xxxxx/alarm/xxxxxb591e2a5fcc/lock/state","command_topic":"ring/xxxxx/alarm/xxxxx9-db591e2a5fcc/lock/command","device":{"ids":["xxxxxc9-db591e2a5fcc"],"name":"Front Door Lock","mf":"Kwikset","mdl":"Lock"}}

Just to give an update: since 4.8.0 The docker container version also supports live streams via rtsp. Works quite well, if you are running on decent hardware (e.g. a Synology with enough memory)

Hey cool, thanks for the update! Are you integrating the stream somehow into the OH UI?

@Lars_Deutsch ever since I upgraded to 4.8.1, I get tons of these messages in my logs. Are you having the same thing?

2021-09-13 08:55:56.365 [WARN ] [ab.binding.mqtt.generic.ChannelState] - Command ' OFF ' not supported by type 'OnOffValue': No enum constant org.openhab.core.library.types.OnOffType. OFF 
2021-09-13 08:55:56.367 [WARN ] [t.generic.ChannelStateTransformation] - Executing the JINJA-transformation failed: An error occurred while transformation. Argument named 'default_value' is required but missing for filter default
2021-09-13 08:55:56.371 [WARN ] [t.generic.ChannelStateTransformation] - Executing the JINJA-transformation failed: An error occurred while transformation. Argument named 'default_value' is required but missing for filter default
2021-09-13 08:56:05.519 [WARN ] [ab.binding.mqtt.generic.ChannelState] - Command ' OFF ' not supported by type 'OnOffValue': No enum constant org.openhab.core.library.types.OnOffType. OFF 
2021-09-13 08:56:05.519 [WARN ] [t.generic.ChannelStateTransformation] - Executing the JINJA-transformation failed: An error occurred while transformation. Argument named 'default_value' is required but missing for filter default
2021-09-13 08:56:05.524 [WARN ] [t.generic.ChannelStateTransformation] - Executing the JINJA-transformation failed: An error occurred while transformation. Argument named 'default_value' is required but missing for filter default

Same warning messages here.

Maybe worth opening an issue on their Github? I want to upgrade as well to implement the chime but with so many warning messages I don’t know :grimacing:
I try to run my OH with a clean as possible log


-edit-
I have just spotted that version 4.7 also supports the chime in which case that would be good enough for me. Did any of you guys above had version 4.7.0 - 4.7.2 installed with the same issues? Otherwise I just use one of those.

Anyone updated to 4.8.3 and still get the errors?

Just updated, warning messages are still there.

I updated as well. Same errors. I opened an issue on GitHub. Due to this discussion I found a fix for now. In short, create your own MQTT-Things and configure the channels and do not use the auto discovered mqtt:homeassistant-based Thing.