I hadn’t updated in a couple of months so went ahead this evening and updated to the latest. I’ve been putting off migrating my Z-Wave to the new Z-WaveJS figuring I’d let it mature a good deal. I wasn’t having any issues with the deprecated Z-Wave but now that has disappeared and my understanding you have to have the old one running to use the migration wizard.
What would be the best way to proceed given the state my RPI 4.
2 posts - 2 participants
I recently switched over to HA after Insteon shut down and all my devices showed up except for one - my Insteon 2477SA1 INSTEON Dual-Band 220V / 240V 30-AMP Load Controller Normally Open Relay. Before Insteon shutdown, I had an interesting failure condition where the relay would never turn off according to schedule but always turn on, even if I moved the hub right next to it (and was within feet of another switch which may have bee relaying the RF signal for it). What is strange is that the relay ALWAYS turns on in the morning, but after some time it was less and less reliable at turning off in the evening until it just stopped altogether one day. My schedule was always on in the morning and off in the evening - never changed it.
I downloaded Insteon-terminal to see if I could at least see the “pairing” messages from the unit (after holding down the setup button). Here is the output with logging level DEBUG after modem.startWatch():
15:33:23.540 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x6A|ACK/NACK:0x06|
modem got msg: IN:Cmd:0x6A|ACK/NACK:0x06|
15:33:23.553 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x57|RecordFlags:0xEB|ALLLinkGroup:0x00|LinkAddr:33.51.AD|LinkData1:0x01|LinkData2:0x07|LinkData3:0x4A|
modem got msg: IN:Cmd:0x57|RecordFlags:0xEB|ALLLinkGroup:0x00|LinkAddr:33.51.AD|LinkData1:0x01|LinkData2:0x07|LinkData3:0x4A|
15:33:23.556 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x6A|ACK/NACK:0x06|
modem got msg: IN:Cmd:0x6A|ACK/NACK:0x06|
15:33:23.557 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:33.51.AD|LinkData1:0x00|LinkData2:0x00|LinkData3:0x00|
modem got msg: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:33.51.AD|LinkData1:0x00|LinkData2:0x00|LinkData3:0x00|
15:33:23.560 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x6A|ACK/NACK:0x06|
modem got msg: IN:Cmd:0x6A|ACK/NACK:0x06|
15:33:23.562 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:39.4C.12|LinkData1:0x00|LinkData2:0x00|LinkData3:0x00|
modem got msg: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:39.4C.12|LinkData1:0x00|LinkData2:0x00|LinkData3:0x00|
15:33:23.563 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x6A|ACK/NACK:0x06|
modem got msg: IN:Cmd:0x6A|ACK/NACK:0x06|
15:33:23.564 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x00|LinkAddr:32.2E.59|LinkData1:0x01|LinkData2:0x38|LinkData3:0x43|
modem got msg: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x00|LinkAddr:32.2E.59|LinkData1:0x01|LinkData2:0x38|LinkData3:0x43|
15:33:23.564 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x6A|ACK/NACK:0x06|
modem got msg: IN:Cmd:0x6A|ACK/NACK:0x06|
15:33:23.565 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:32.2E.59|LinkData1:0x00|LinkData2:0x00|LinkData3:0x00|
modem got msg: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:32.2E.59|LinkData1:0x00|LinkData2:0x00|LinkData3:0x00|
15:33:23.565 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x6A|ACK/NACK:0x06|
modem got msg: IN:Cmd:0x6A|ACK/NACK:0x06|
15:33:23.565 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x00|LinkAddr:58.56.8F|LinkData1:0x01|LinkData2:0x2A|LinkData3:0x45|
modem got msg: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x00|LinkAddr:58.56.8F|LinkData1:0x01|LinkData2:0x2A|LinkData3:0x45|
15:33:23.565 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x6A|ACK/NACK:0x06|
modem got msg: IN:Cmd:0x6A|ACK/NACK:0x06|
15:33:23.566 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:58.56.8F|LinkData1:0x00|LinkData2:0x00|LinkData3:0x00|
modem got msg: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:58.56.8F|LinkData1:0x00|LinkData2:0x00|LinkData3:0x00|
15:33:23.566 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x6A|ACK/NACK:0x15|
modem got msg: IN:Cmd:0x6A|ACK/NACK:0x15|
15:33:23.566 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x7F|Command2:0x02|ACK/NACK:0x06|
modem got msg: IN:Cmd:0x7F|Command2:0x02|ACK/NACK:0x06|
Since I’ve already had to replace my hub once and since Insteon is out of business, I thought I would post here with this info before I starting changing anything in the hub configuration. Is there a low risk way to add this to HA (and also if anyone knows to test communication using Insteon-terminal) sop I can schedule it to turn off in the evening?
I also had a question regarding the schedules in the hub. Is there a way I can see it with either HA or Insteon-terminal? Also, can I modify it? I just have two things it controls and at this point if I can’t modify it I’m happy just to add a schedule in HA to turn off the relay (assuming I can control and actually turn it off).
Thanks in advance for any insight you all can provide.
1 post - 1 participant
I’ve been running HA for a couple years but yesterday it crashed. I’ve taken backups now and then and most recent backup is from a few days ago.
I have a raspberry pi 3. Now I do not remember if I used 32 or 64 bit OS before. I flashed and installed the 64 bit latest version as recommended in the getting started guide (my backups are also from using the latest HA version). The system boots up after a few minutes. Then I’ve uploaded my latest backup file and tried to restore it. I tried a couple times yesterday but could not get the system to get to boot up to its gui (it’s available on the network). I then decided to try restore everything except the HA (the option at the very top, not sure of the name). I let the backup restore keep going but still about 7 hours later it has restored some, but not the dashboards or automations or configuration.yaml and many more files, Also, the system keeps reporting lots of errors then that it find a backup file, takes some time, and reports errors and keep repeating.
I use a conbee stick and it was found. The conbee stick was found already before I started the restore of the backup.
I’ve read that a restore of a backup might take some 10 minutes but as stated this takes hours longer. I can open the backup file in my local computer with 7 zip and I see that it contains all my files.
Any suggestions on how to get it back running? I just flashed the 32 bit version and am trying to restore the whole backup.
2 posts - 1 participant
I just flashed an sd card and restored my latest backup after experiencing a crash.
I see these lines in red appearing time after time and I wonder what they mean and if I can do anything about them:
22-04-29 05:54:13 WARNING (MainThread) [supervisor.addons.options] Option ‘database_path’ does not exist in the schema for SQLite Web (a0d7b954_sqlite-web)
22-04-29 05:54:13 WARNING (MainThread) [supervisor.addons.options] Option ‘read_only’ does not exist in the schema for SQLite Web (a0d7b954_sqlite-web)
22-04-29 05:54:13 WARNING (MainThread) [supervisor.addons.options] Option ‘datasette’ does not exist in the schema for SQLite Web (a0d7b954_sqlite-web)
22-04-29 05:54:13 WARNING (MainThread) [supervisor.addons.options] Option ‘ssl’ does not exist in the schema for SQLite Web (a0d7b954_sqlite-web)
22-04-29 05:54:13 WARNING (MainThread) [supervisor.addons.options] Option ‘certfile’ does not exist in the schema for SQLite Web (a0d7b954_sqlite-web)
22-04-29 05:54:13 WARNING (MainThread) [supervisor.addons.options] Option ‘keyfile’ does not exist in the schema for SQLite Web (a0d7b954_sqlite-web)
22-04-29 05:54:13 WARNING (MainThread) [supervisor.addons.options] Option ‘vnc_password’ does not exist in the schema for deCONZ (core_deconz)
1 post - 1 participant
I’m running a raspberry pi 3 and I just experienced a crash. I believe I was running the 32 bit version of HA but per the start guide installed the recommended 64 bit version. I tried to restore my latest backup (a few days old) onto the newly flashed sd card but it didnt succeed, i stopped after many hours.
Question 1: I ordered a raspberry pi 4 and I wonder if it is possible to restore my current HA setup with all it’s configurations onto a freshly flashed sd card in the rpi4.
Do I need to flash the 32 bit version because that’s what I believe I was using previously (in my backup) and then do a restore of the backup? Or has someone succeded installing a 64 bit version and later restoring a 32 bit backup?
Question 2: Is a backup from a raspberry pi 3 system compatible with a rpi 4? That is, is it possible to restore a backup i made on my rpi3 onto the rpi 4?
Thank you so much in advance for caring to read this and answering!
1 post - 1 participant
I’m not a developer but having fun with learning HA and the great integrations I’ve added. One of them seems simple and I don’t know where to start and would appreciate some help?
I added the Jewish calendar to my config and see many sensor entities. How can I announce a sensor state with the play media action?
sensor.jewish_calendar_parshat_hashavua
Specifically for example I want to announce this sensor every Friday at 10am, what would I need to write and where?
8 posts - 2 participants
Hello!
I have spent the morning trying to find a way to monitor the volume_level+source of a media player (a universal media player, but I think that is immaterial), so that I might set the volume_level to the last used level for that source.
My AVR (Denon) for whatever reason plays HEOS/Spotify/streams at SUCH a loud volume compared to anything else. I have to have it at ~40% volume, but everything else at 65%.
I had this idea to use an input_text to store a JSON blob mapping source name to last-known volume level and combine it with an automation which triggered on the source of the media player changing.
Unfortunately, I’m having a hell of a time trying to construct JSON in a template. I suspect I could use Node-RED for this but I don’t yet have any experience with it and really would prefer to keep the definition for this automation in my media_centre.yaml package if possible.
What I’ve tried:
{% set volumes = iif(is_state('input_text.cached_volumes', 'unknown'), "{}", states('input_text.cached_volumes')) | from_json %}
{% set source = state_attr('media_player.living_room', 'source') %}
{% set level = state_attr('media_player.living_room', 'volume_level') %}
{# This raises a SecurityError #}
{% set _ = volumes.update({source: level}) %}
{# This allows me to _set_ keys but I can't turn it into JSON and I can't use dynamic key names #}
{% set volumes = namespace(volumes) %}
{% set volumes.foo = level %}
The closest I can get (which tbh may be workable) is to store a list of dictionaries as json, instead of single dictionary, but then the update logic will be quite more difficult to avoid duplicating entries:
{% set volumes = iif(is_state('input_text.cached_volumes', 'unknown'), "[]", states('input_text.cached_volumes')) | from_json %}
{% set source = state_attr('media_player.living_room', 'source') %}
{% set level = state_attr('media_player.living_room', 'volume_level') %}
{% set volumes = volumes + [{"source": "e.g. source", "volume_level": 0.3}] %}
{% set volumes = volumes + [{"source": source, "volume_level": level}] %}
{{ volumes | to_json }}
which outputs:
[{"source": "e.g. source", "volume_level": 0.3},
{"source": "HEOS Music", "volume_level": 0.5}]
Is this my best bet? Am I missing an obvious way to do this more easily (besides Node-RED, which I will definitely look into if I am not left with a superior option).
1 post - 1 participant
Hi, I want to have a device that I can use in my Sharptools dashboard that displays the state of the garage door e.g. open closing closed opening etc as well as being able to click it as a button.
I was thinking that a sensor would be the right option as I can set the states accordingly but I don’t think that is a device and it isn’t clickable (as far as I know). I also looked in the helpers for something to use but couldn’t see anything appropriate. It feels like I want a momentary switch that has a state attribute as well. Is there a way to create custom devices like this?
The end result would be a “thing” that could be added to my Sharptools dashboard that when clicked would show a status of opening until the garage opened and then show a status of open etc.
thanks in advance
1 post - 1 participant
Hi community!
I would like to have some more advanced automation for my roller shutters.
I already did something like this:
Open shutter1 on sunrise
Open shutter1 half an hour before sunrise
Open shutter1 on 7:00
…
But thats not really satisfying.
I want to open the shutters at around 7:00 in the morning. But when sunrise is later, I want to open them on sunrise.
Is there any way to get something like “Open shutter on sunrise, but not earlier than 7:00”?
Thank you!
1 post - 1 participant
I want to make a binary sensor group, but i also want to edit it in the frontend. So I need an unique id. What is the best way to do this?
The binary sensor group obviously isn’t.
1 post - 1 participant
Hi All,
I have setup an automation with sonoff zigbee temperature sensor and a sonof zigbee plug.
I am using Zigbee2Mqtt to connect my devices all software is up to date.
When the temperature is above a certain value it must turn on the plug that is connected to a fan.
The automation does not run automatically and if I run it manually then it turns on ignoring the temperature and condition.
I think I may be using the wrong states or something. I would really appreciate it if somebody could help,
Here is the code for my automation
- id: '1651212183531'
alias: Garage - Turn on the inverter fan
description: ''
trigger:
- platform: numeric_state
entity_id: sensor.garage_temperature_sensor_temperature
above: '19'
condition:
- condition: device
type: is_on
device_id: 386743aabbeffd64ba04b17e01a17895
entity_id: switch.garage_inverter_fan
domain: switch
action:
- type: turn_off
device_id: 386743aabbeffd64ba04b17e01a17895
entity_id: switch.garage_inverter_fan
domain: switch
mode: single
1 post - 1 participant
Hi!
I can access HA in two ways. Connect with OpenVPN and use local ip to connect, or use ddns service and connect with dns address.
Is there any security level differences or is it basically the same?
So, I have it setup like this:
My no-ip account is set in Asus router with Let’s Encrypt certificate.
Then I installed NGINX proxy add-on, copy certificates to /ssl folder that I generated in router.
Changed port in NGINX to something else and then make a port forward in router to HA ip and NGINX port.
Now I can connect with https://xxxx:xxx. It works great, but is there a preferred way?
Is this even considered safe?
HA is running in Proxmox vm.
Regards!
1 post - 1 participant
Hi
I copied the home url to another view tab by mistake (let’s call it new view).
(overview on side bar->edit dashboard->edit pen->setting)
Now the two views are showing the same view - home view.
If I’m deleting the new tab the home view is deleted as well.
If I’m hiding the new tab the home view is hided as well.
If I’m deleting the new tab’s URL the home view is changed as well.
Any ideas on how to resolve it?
Thanks
Ariel
2 posts - 2 participants
Hi,
Reading this topic: Lovelace Custom Fan Card Example
I tried to get a specific FAN card to work, I do see them in my Lovelace screen, but the buttons doesn’t seem to respons on changed FAN state as well when I click them. I have 2 entitites, one represents the actual state, the other is the control entity.
How can I connect these entities to my FAN card:
My card:
The javascript that needs to be edited:
class CustomFanCard extends Polymer.Element {
static get template() {
return Polymer.html`
<style>
.flex-container {
display: flex;
justify-content: center;
align-items: center;
}
@keyframes mdc-ripple-fg-radius-in{from{animation-timing-function:cubic-bezier(0.4, 0, 0.2, 1);transform:translate(var(--mdc-ripple-fg-translate-start, 0)) scale(1)}to{transform:translate(var(--mdc-ripple-fg-translate-end, 0)) scale(var(--mdc-ripple-fg-scale, 1))}}@keyframes mdc-ripple-fg-opacity-in{from{animation-timing-function:linear;opacity:0}to{opacity:var(--mdc-ripple-fg-opacity, 0)}}@keyframes mdc-ripple-fg-opacity-out{from{animation-timing-function:linear;opacity:var(--mdc-ripple-fg-opacity, 0)}to{opacity:0}}.mdc-ripple-surface--test-edge-var-bug{--mdc-ripple-surface-test-edge-var: 1px solid #000;visibility:hidden}.mdc-ripple-surface--test-edge-var-bug::before{border:var(--mdc-ripple-surface-test-edge-var)}.mdc-button{font-family:Roboto,sans-serif;-moz-osx-font-smoothing:grayscale;-webkit-font-smoothing:antialiased;font-size:.875rem;line-height:2.25rem;font-weight:500;letter-spacing:.0892857143em;text-decoration:none;text-transform:uppercase;--mdc-ripple-fg-size: 0;--mdc-ripple-left: 0;--mdc-ripple-top: 0;--mdc-ripple-fg-scale: 1;--mdc-ripple-fg-translate-end: 0;--mdc-ripple-fg-translate-start: 0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity;padding:0 8px 0 8px;display:inline-flex;position:relative;align-items:center;justify-content:center;box-sizing:border-box;min-width:64px;height:36px;border:none;outline:none;line-height:inherit;user-select:none;-webkit-appearance:none;overflow:hidden;vertical-align:middle;border-radius:4px}.mdc-button::before,.mdc-button::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.mdc-button::before{transition:opacity 15ms linear,background-color 15ms linear;z-index:1}.mdc-button.mdc-ripple-upgraded::before{transform:scale(var(--mdc-ripple-fg-scale, 1))}.mdc-button.mdc-ripple-upgraded::after{top:0;left:0;transform:scale(0);transform-origin:center center}.mdc-button.mdc-ripple-upgraded--unbounded::after{top:var(--mdc-ripple-top, 0);left:var(--mdc-ripple-left, 0)}.mdc-button.mdc-ripple-upgraded--foreground-activation::after{animation:225ms mdc-ripple-fg-radius-in forwards,75ms mdc-ripple-fg-opacity-in forwards}.mdc-button.mdc-ripple-upgraded--foreground-deactivation::after{animation:150ms mdc-ripple-fg-opacity-out;transform:translate(var(--mdc-ripple-fg-translate-end, 0)) scale(var(--mdc-ripple-fg-scale, 1))}.mdc-button::before,.mdc-button::after{top:calc(50% - 100%);left:calc(50% - 100%);width:200%;height:200%}.mdc-button.mdc-ripple-upgraded::after{width:var(--mdc-ripple-fg-size, 100%);height:var(--mdc-ripple-fg-size, 100%)}.mdc-button::-moz-focus-inner{padding:0;border:0}.mdc-button:active{outline:none}.mdc-button:hover{cursor:pointer}.mdc-button:disabled{background-color:transparent;color:rgba(0,0,0,.37);cursor:default;pointer-events:none}.mdc-button.mdc-button--dense{border-radius:4px}.mdc-button:not(:disabled){background-color:transparent}.mdc-button:not(:disabled){color:#6200ee;color:var(--mdc-theme-primary, #6200ee)}.mdc-button::before,.mdc-button::after{background-color:#6200ee}@supports not (-ms-ime-align: auto){.mdc-button::before,.mdc-button::after{background-color:var(--mdc-theme-primary, #6200ee)}}.mdc-button:hover::before{opacity:.04}.mdc-button:not(.mdc-ripple-upgraded):focus::before,.mdc-button.mdc-ripple-upgraded--background-focused::before{transition-duration:75ms;opacity:.12}.mdc-button:not(.mdc-ripple-upgraded)::after{transition:opacity 150ms linear}.mdc-button:not(.mdc-ripple-upgraded):active::after{transition-duration:75ms;opacity:.16}.mdc-button.mdc-ripple-upgraded{--mdc-ripple-fg-opacity: 0.16}.mdc-button .mdc-button__icon{margin-left:0;margin-right:8px;display:inline-block;width:18px;height:18px;font-size:18px;vertical-align:top}[dir=rtl] .mdc-button .mdc-button__icon,.mdc-button .mdc-button__icon[dir=rtl]{margin-left:8px;margin-right:0}.mdc-button svg.mdc-button__icon{fill:currentColor}.mdc-button--raised .mdc-button__icon,.mdc-button--unelevated .mdc-button__icon,.mdc-button--outlined .mdc-button__icon{margin-left:-4px;margin-right:8px}[dir=rtl] .mdc-button--raised .mdc-button__icon,.mdc-button--raised .mdc-button__icon[dir=rtl],[dir=rtl] .mdc-button--unelevated .mdc-button__icon,.mdc-button--unelevated .mdc-button__icon[dir=rtl],[dir=rtl] .mdc-button--outlined .mdc-button__icon,.mdc-button--outlined .mdc-button__icon[dir=rtl]{margin-left:8px;margin-right:-4px}.mdc-button--raised,.mdc-button--unelevated{padding:0 16px 0 16px}.mdc-button--raised:disabled,.mdc-button--unelevated:disabled{background-color:rgba(0,0,0,.12);color:rgba(0,0,0,.37)}.mdc-button--raised:not(:disabled),.mdc-button--unelevated:not(:disabled){background-color:#6200ee}@supports not (-ms-ime-align: auto){.mdc-button--raised:not(:disabled),.mdc-button--unelevated:not(:disabled){background-color:var(--mdc-theme-primary, #6200ee)}}.mdc-button--raised:not(:disabled),.mdc-button--unelevated:not(:disabled){color:#fff;color:var(--mdc-theme-on-primary, #fff)}.mdc-button--raised::before,.mdc-button--raised::after,.mdc-button--unelevated::before,.mdc-button--unelevated::after{background-color:#fff}@supports not (-ms-ime-align: auto){.mdc-button--raised::before,.mdc-button--raised::after,.mdc-button--unelevated::before,.mdc-button--unelevated::after{background-color:var(--mdc-theme-on-primary, #fff)}}.mdc-button--raised:hover::before,.mdc-button--unelevated:hover::before{opacity:.08}.mdc-button--raised:not(.mdc-ripple-upgraded):focus::before,.mdc-button--raised.mdc-ripple-upgraded--background-focused::before,.mdc-button--unelevated:not(.mdc-ripple-upgraded):focus::before,.mdc-button--unelevated.mdc-ripple-upgraded--background-focused::before{transition-duration:75ms;opacity:.24}.mdc-button--raised:not(.mdc-ripple-upgraded)::after,.mdc-button--unelevated:not(.mdc-ripple-upgraded)::after{transition:opacity 150ms linear}.mdc-button--raised:not(.mdc-ripple-upgraded):active::after,.mdc-button--unelevated:not(.mdc-ripple-upgraded):active::after{transition-duration:75ms;opacity:.32}.mdc-button--raised.mdc-ripple-upgraded,.mdc-button--unelevated.mdc-ripple-upgraded{--mdc-ripple-fg-opacity: 0.32}.mdc-button--raised{box-shadow:0px 3px 1px -2px rgba(0, 0, 0, 0.2),0px 2px 2px 0px rgba(0, 0, 0, 0.14),0px 1px 5px 0px rgba(0,0,0,.12);transition:box-shadow 280ms cubic-bezier(0.4, 0, 0.2, 1)}.mdc-button--raised:hover,.mdc-button--raised:focus{box-shadow:0px 2px 4px -1px rgba(0, 0, 0, 0.2),0px 4px 5px 0px rgba(0, 0, 0, 0.14),0px 1px 10px 0px rgba(0,0,0,.12)}.mdc-button--raised:active{box-shadow:0px 5px 5px -3px rgba(0, 0, 0, 0.2),0px 8px 10px 1px rgba(0, 0, 0, 0.14),0px 3px 14px 2px rgba(0,0,0,.12)}.mdc-button--raised:disabled{box-shadow:0px 0px 0px 0px rgba(0, 0, 0, 0.2),0px 0px 0px 0px rgba(0, 0, 0, 0.14),0px 0px 0px 0px rgba(0,0,0,.12)}.mdc-button--outlined{border-style:solid;padding:0 14px 0 14px;border-width:2px}.mdc-button--outlined:disabled{border-color:rgba(0,0,0,.37)}.mdc-button--outlined:not(:disabled){border-color:#6200ee;border-color:var(--mdc-theme-primary, #6200ee)}.mdc-button--dense{height:32px;font-size:.8125rem}.material-icons{font-family:var(--mdc-icon-font, "Material Icons");font-weight:normal;font-style:normal;font-size:var(--mdc-icon-size, 24px);line-height:1;letter-spacing:normal;text-transform:none;display:inline-block;white-space:nowrap;word-wrap:normal;direction:ltr;-webkit-font-feature-settings:"liga";-webkit-font-smoothing:antialiased}:host{display:inline-flex;outline:none}.mdc-button{flex:1}
:host {
display: inherit;
}
.speeds button:host {
display: inline-flex;
outline: none;
}
.speeds button {
min-width: 34px !important;
width: 34px;
font-size: 11px !important;
}
</style>
<hui-generic-entity-row hass="[[hass]]" config="[[_config]]">
<div class='flex-container' on-click="stopPropagation">
<div class='speeds'>
<button
class='mdc-button mdc-button--raised mdc-ripple-upgraded'
toggles name="off"
on-tap='setSpeed'
disabled='[[_isOff]]'>
<span class="mdc-button__label">O</span>
</button>
<button
class='mdc-button mdc-button--raised mdc-ripple-upgraded'
toggles name="1"
on-tap='setSpeed'
disabled='[[_isOneSpeed]]'>
<span class="mdc-button__label">1</span>
</button>
<button
class='mdc-button mdc-button--raised mdc-ripple-upgraded'
toggles name="2"
on-tap='setSpeed'
disabled='[[_isTwoSpeed]]'>
<span class="mdc-button__label">2</span>
</button>
<button
class='mdc-button mdc-button--raised mdc-ripple-upgraded'
toggles name="3"
on-tap='setSpeed'
disabled='[[_isThreeSpeed]]'>
<span class="mdc-button__label">3</span>
</button>
<button
class='mdc-button mdc-button--raised mdc-ripple-upgraded'
toggles name="4"
on-tap='setSpeed'
disabled='[[_isFourSpeed]]'>
<span class="mdc-button__label">4</span>
</button>
<button
class='mdc-button mdc-button--raised mdc-ripple-upgraded'
toggles name="5"
on-tap='setSpeed'
disabled='[[_isFiveSpeed]]'>
<span class="mdc-button__label">5</span>
</button>
<button
class='mdc-button mdc-button--raised mdc-ripple-upgraded'
toggles name="6"
on-tap='setSpeed'
disabled='[[_isSixSpeed]]'>
<span class="mdc-button__label">6</span>
</button>
</div>
</div>
</hui-generic-entity-row>
`;
}
static get properties() {
return {
hass: {
type: Object,
observer: 'hassChanged'
},
_config: Object,
_stateObj: Object,
_isOff: Boolean,
_isOneSpeed: Boolean,
_isTwoSpeed: Boolean,
_isThreeSpeed: Boolean,
_isFourSpeed: Boolean,
_isFiveSpeed: Boolean,
_isSixSpeed: Boolean
}
}
setConfig(config) {
this._config = config;
}
hassChanged(hass) {
const config = this._config;
const stateObj = hass.states[config.entity];
let speed;
if (stateObj && stateObj.attributes) {
speed = stateObj.attributes.speed || 'off';
}
this.setProperties({
_stateObj: stateObj,
_isOff: stateObj.state === 'off',
_isOneSpeed: speed === '1' && stateObj.state === 'on',
_isTwoSpeed: speed === '2' && stateObj.state === 'on',
_isThreeSpeed: speed === '3' && stateObj.state === 'on',
_isFourSpeed: speed === '4' && stateObj.state === 'on',
_isFiveSpeed: speed === '5' && stateObj.state === 'on',
_isSixSpeed: speed === '6' && stateObj.state === 'on',
});
}
stopPropagation(e) {
e.stopPropagation();
}
setSpeed(e) {
const speed = e.currentTarget.getAttribute('name');
this.hass.callService('fan', 'set_speed', {
entity_id: this._config.entity, speed: speed
});
}
}
customElements.define('custom-fan-card', CustomFanCard);
1 post - 1 participant
Hello,
i think i found a Bug, i use the integration to control my Firetv Plex Client, when i now start a for example a Episode on Plex it works well the state of the media_player changes to playing.
BUT when i now use the Plex Skill and make the same, easy say "“Alexa, play tvshow simpsons” he starts playing on the firetv but the state of the entity is still idle.
this happens everytime when i start a Movie or Episode over the Skill.
I dont know where the problem comes from, the integration or the Plex Skill?
edit
on the plex dashboard i see the same Problem. i am playing a episode over the skill, but he says nothing is playing, but in the diagram its traffic
1 post - 1 participant
Hey community,
I’ve installed zigbee2mqtt together with mosquitto today on my Raspberry Pi in a docker container. After having many issues I was able to start both containers without erros in the logs. But unfortunately, the frontend of the zigbee2mqtt is not showing up.
Here are some more information:
Mosquitto
command: "mosquitto -c /mosquitto-no-auth.conf"
/ # mosquitto_passwd -b -c passwd mqtt myMQTTPassword
/ # cat passwd
port 1883
listener 9001
protocol websockets
persistence true
persistence_location /mosquitto/data
allow_anonymous false
password_file /mosquitto/config/passwd
zigbee2mqtt
homeassistant: true
permit_join: true
# MQTT settings
mqtt:
# MQTT base topic for zigbee2mqtt MQTT messages
base_topic: zigbee2mqtt
# MQTT server URL
server: 'mqtt://192.168.178.51:1883'
# MQTT server authentication, uncomment if required:
user: mqtt
password: myMQTTPassword
serial:
port: /dev/ttyUSB0
adapter: deconz
# Enable the Zigbee2MQTT frontend
frontend:
port: 8080
advanced:
network_key:
- MY
- NETWORK
- KEY
Using '/app/data' as data directory
Zigbee2MQTT:info 2022-04-29 09:36:13: Logging to console and directory: '/app/data/log/2022-04-29.09-36-06' filename: log.txt
Zigbee2MQTT:info 2022-04-29 09:36:13: Starting Zigbee2MQTT version 1.25.0 (commit #6f1460e)
Zigbee2MQTT:info 2022-04-29 09:36:13: Starting zigbee-herdsman (0.14.20)
CREATED DECONZ ADAPTER
Zigbee2MQTT:info 2022-04-29 09:36:15: zigbee-herdsman started (resumed)
Zigbee2MQTT:info 2022-04-29 09:36:15: Coordinator firmware version: '{"meta":{"maintrel":0,"majorrel":38,"minorrel":88,"product":0,"revision":"0x26580700","transportrev":0},"type":"ConBee2/RaspBee2"}'
Zigbee2MQTT:info 2022-04-29 09:36:15: Currently 0 devices are joined:
Zigbee2MQTT:warn 2022-04-29 09:36:15: `permit_join` set to `true` in configuration.yaml.
Zigbee2MQTT:warn 2022-04-29 09:36:15: Allowing new devices to join.
Zigbee2MQTT:warn 2022-04-29 09:36:15: Set `permit_join` to `false` once you joined all devices.
Zigbee2MQTT:info 2022-04-29 09:36:15: Zigbee: allowing new devices to join.
Zigbee2MQTT:info 2022-04-29 09:36:16: Connecting to MQTT server at mqtt://192.168.178.51:1883
Zigbee2MQTT:info 2022-04-29 09:36:16: Connected to MQTT server
Zigbee2MQTT:info 2022-04-29 09:36:16: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
Zigbee2MQTT:info 2022-04-29 09:36:17: Started frontend on port 0.0.0.0:8080
Zigbee2MQTT:info 2022-04-29 09:36:17: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"commit":"6f1460e","coordinator":{"meta":{"maintrel":0,"majorrel":38,"minorrel":88,"product":0,"revision":"0x26580700","transportrev":0},"type":"ConBee2/RaspBee2"},"log_level":"info","network":{"channel":11,"extendedPanID":"0xdddddddddddddddd","panID":6754},"permit_join":true,"version":"1.25.0"}'
Does anyone have an idea on how to resolve that issue?
I’m also using zwavejs2mqtt container on the same portainer, that one works well.
Best regards,
Mark
3 posts - 2 participants
I have had the Homekit integration in use for some time and it seems to work well and as I expect…without any real issues…at least with functionality. However, I always seem to have an issue on a restart I get a total of 25 notifications about all 25 of my Homekit pairings needing to be set, as per the screenshot below. I can’t imagine this is supposed to be the case…so wondering if it is a glitch…although I had a search and couldn’t find another mention of it, or is there a setting somewhere that I need to change that I didn’t know about…or read up about properly…
Of course, I can just dismiss all of the notifications each time with the dismiss all button…but it would be nice to turn them off altogether as they are all working as expected
TIA
1 post - 1 participant
Hello everyone, I purchased and configured a zigbee sonoff 3.0 key using HZA and coupled a set of xiaomi mija sensors (2 movement, 2 magnetic and a button). All the devices have been seen correctly but one of them has the status with the value “not available). I tried to restart HA (home assistant os installed on raspberry) and now I have 3 devices with” not available "status.
I tried to wait a few hours and change the status (let me detect or open and close the magnetic sensor) and now I see the status of 3 devices. When I randomly reboot some device ends up unavailable.
Why this behavior?
This is my zigbee device:
This is one device unavailable:
1 post - 1 participant
hi, I have a simple automation, but the second part is never triggering 
I want it to start heating and then wait for the temp to be over a number. It seems to check just once. What I am missing?
alias: Keep the spabad warm
description: ''
trigger:
- type: temperature
platform: device
device_id: 3fb3918d8b9b24301c38a489273363
entity_id: sensor.layzspa_temperature
domain: sensor
below: 30
condition: []
action:
- type: turn_on
device_id: 3fb3918d8b9b24301c38a489273363
entity_id: switch.layzspa_heat_regulation
domain: switch
- service: notify.mobile_app_m2101k6g
data:
message: Start heating the spabad
- wait_for_trigger:
- type: temperature
platform: device
device_id: 3fb3918d8b9b24301c38a489273363
entity_id: sensor.layzspa_temperature
domain: sensor
above: 33
continue_on_timeout: false
- type: turn_off
device_id: 3fb3918d8b9b24301c38a489273363
entity_id: switch.layzspa_pump
domain: switch
- service: notify.mobile_app_m2101k6g
data:
message: Finish heating the spabad
mode: single
This is the debug:
2 posts - 2 participants
