![]() You can still access entity details by clicking on the station icon (yup, that's not very obvious. ![]() You can hide the 3 vertical dots that appear to the right of station controls using hide_dots, which should further remove some sources of accidents.Popup_line_height: small # Spacing between entities (sensors, stations, programs) listed in the popup timer_line_height: medium # Spacing between progress bars (running stations) in the card card_line_height: small # Spacing between extra_entities (entities in the card) The slider or box input will appear in the popup, and if you are using the extra_entities option, in the card as well. To extend the length they run for, make an input_number entity then link it to the card via the input_number option. Stations also default to a runtime of 1 minute. You can also add programs or even any entity type ( switches, lights, etc). If you'd like to have a few stations controls always accessible from the dashboard, you can add them to the bottom of the card with the extra_entities option. The id of the rain delay stop time sensor ends with _rain_delay_stop_timeīy default, the only way to control stations is to first click on the 3 dots in the top-right corner of the card.The id of the rain delay active binary sensor ends with _rain_delay_active.The ids of program & station enabled switches end with _enabled.The id of the OpenSprinkler controller enabled switch ends with _enabled.The ids of program running binary sensors end with _running.The ids of station status sensors end with _status.If you haven't changed these, you have nothing to worry about. This card locates your OpenSprinkler entities by using their entity ids. You can also set popup_line_height, timer_line_height, and card_line_height to control the spacing of entities. See the default config for an example.įinding device ids is tricky, so I recommend using the dropdown in the visual card editor to set device rather than YAML. If true, hide disabled stations and programs in the popup If true, hide the 3 dots appearing next to entities Options Nameĭevice id of the OpenSprinkler in Home AssistantĬonfiguration for run-duration-choosing entity If you don't have HACS installed, follow the manual installation instructions. OpenSprinkler Card is available from HACS (search for "opensprinkler card"). You will need the OpenSprinkler integration installed. ![]() Then re-power and see what happens.Collect OpenSprinkler status into a card for Home Assistant. As soon as they go dark, pull the plug (or the system will restart on its own–not what you want). I would approach this carefully by using ssh to get in and typing poweroff and then watching for all of the system lights to go out (except power). My first stop would be a hard reset of the box: power off for 60 seconds, then back on. I don’t think I’ve ever seen that one before. ![]() It’s always hard to know what’s going on under the hood with Vera, we just don’t know, but that doesn’t seem good.Ġ1Đ7/25/19 11:38:34.573 ZWaveJobHandler::ConnectionIsValid failed first time -627861324 Ī lot of these are coming in series during the initialization of Z-Wave, right at the start. ![]() Wait 1 second before continuing to let it try to recover. Two of the stops in the log have this message:Ġ1Đ7/25/19 11:33:55.389 ZWave::SetRFReceiveMode failed (nil) Reactor is logging messages showing it is waiting for Z-Wave to come ready, so it’s taking a long time for the Z-wave network to initialize, apparently, and in some cases, it never does. The system runs for several seconds after that, and if you look through the whole log file, you can see that the restarts happen at various times. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |