Skip to content
  • Announcements regarding our smart home community

    9 10
    9 Topics
    10 Posts
    A
    Mios dashboard isn't displaying anything. Anyone know what is going on?
  • A place to talk about whatever you want

    182 2k
    182 Topics
    2k Posts
    therealdbT
    Oh boy. They even sent some invoices, as "courtesy previews". People are entertained in the old place... If you need a way to quickly migrate from Vera to Home Assistant Zwave key, read here: https://smarthome.community/topic/1590/how-to-migrate-from-vera-to-zwave-me-and-then-zwavejs-in-2024 I used Zwave.me as an intermediate step, but I think anything on Zwave series 500 should work.
  • A place to put some How-To documentations

    24 67
    24 Topics
    67 Posts
    therealdbT
    yep, I costantly use GitHub Copilot to help dealing with MSR logic. To be honest, I wanted to ask @toggledbits for a full MCP server for Reactor, since it could be easily useful to automate some kind of tasks regarding rules etc. I built one for my own use, but it's not that useful for the public, because right now we don't have endpoints to manage rules. but, nonetheless, having a true grasp of all my entities helps a lot.
  • Share and discuss your lua creations here

    39 230
    39 Topics
    230 Posts
    akbooerA
    Why use any individual scene code at all? Per the reference docs you cited, if you define a scene_prolog global (presumably with the exact same code as your existing executeSceneNumber) that should work directly.
  • Hardware related - Small board computer to IP Camera and technologies like Zigbee or Zwave!

    194 2k
    194 Topics
    2k Posts
    A
    Bought some Crucial PCIe Gen4 NVMe M.2 SSD for $46 USD late last November and now in mid Feb, they are now $74. About a 60% increase in three months. And they have dropped a little in price of late. Seems a case of AI computing is vacuuming them all up, plus some players have stopped manufacturing.
  • 999 Topics
    9k Posts
    tunnusT
    @toggledbits in my case this problem is related to how Synology handles network routing (see the earlier thread). Now by using bypass_blocking statement, I can't lock myself out, but seems that public IPs are not blocked either. See below: (public IP partly redacted) [latest-26318]2026-11-20T18:55:13.334Z <wsapi:INFO> wsapi: connection from "85.*.*.* via proxy ::ffff:172.18.0.1 [latest-26318]2026-11-20T18:55:13.381Z <wsapi:INFO> wsapi#1 client "85.*.*.*#54" authorized [latest-26318]2026-11-20T18:55:17.771Z <httpapi:INFO> httpapi#1 API request from ::ffff:172.18.0.1: GET /api/v1/systime [latest-26318]2026-11-20T18:55:17.771Z <httpapi:null> httpapi#1 checking ACLs for /api/v1/systime user anonymous authorization none [latest-26318]2026-11-20T18:55:17.771Z <httpapi:null> httpapi#1 checking /api/v1/systime against /api/v1/systime ACL { "url": "/api/v1/systime", "allow": true, "index": 6 } [latest-26318]2026-11-20T18:55:17.771Z <httpapi:INFO> httpapi#1 request for /api/v1/systime from ::ffff:172.18.0.1 user anonymous auth none matches /api/v1/systime ACL (#6): { "url": "/api/v1/systime", "allow": true, "index": 6 } [latest-26318]2026-11-20T18:55:22.114Z <httpapi:INFO> httpapi#1 redirecting /reactor/login.html to /reactor/en-US/login.html [latest-26318]2026-11-20T18:55:22.774Z <httpapi:INFO> httpapi#1 API request from ::ffff:172.18.0.1: GET /api/v1/lang [latest-26318]2026-11-20T18:55:22.774Z <httpapi:null> httpapi#1 checking ACLs for /api/v1/lang user anonymous authorization none [latest-26318]2026-11-20T18:55:22.775Z <httpapi:null> httpapi#1 checking /api/v1/lang against /api/v1/lang ACL { "url": "/api/v1/lang", "allow": true, "index": 8 } [latest-26318]2026-11-20T18:55:22.775Z <httpapi:INFO> httpapi#1 request for /api/v1/lang from ::ffff:172.18.0.1 user anonymous auth none matches /api/v1/lang ACL (#8): { "url": "/api/v1/lang", "allow": true, "index": 8 } [latest-26318]2026-11-20T18:55:22.876Z <httpapi:INFO> httpapi#1 API request from ::ffff:172.18.0.1: GET /api/v1/deauthorize [latest-26318]2026-11-20T18:55:22.876Z <httpapi:null> httpapi#1 checking ACLs for /api/v1/deauthorize user admin authorization auth [latest-26318]2026-11-20T18:55:22.877Z <httpapi:null> httpapi#1 checking /api/v1/deauthorize against /api/v1/deauthorize ACL { "url": "/api/v1/deauthorize", "allow": true, "index": 5 } [latest-26318]2026-11-20T18:55:22.877Z <httpapi:INFO> httpapi#1 request for /api/v1/deauthorize from ::ffff:172.18.0.1 user admin auth auth matches /api/v1/deauthorize ACL (#5): { "url": "/api/v1/deauthorize", "allow": true, "index": 5 } [latest-26318]2026-11-20T18:55:22.878Z <httpapi:NOTICE> httpapi#1 deauthorized ::ffff:172.18.0.1 [latest-26318]2026-11-20T18:55:22.878Z <wsapi:NOTICE> wsapi: client "85.*.*.*#54" lost authorization (expired or deleted) [latest-26318]2026-11-20T18:55:22.878Z <wsapi:NOTICE> wsapi: closing "85.*.*.*#54" (1000 lost authorization) [latest-26318]2026-11-20T18:55:22.939Z <wsapi:INFO> wsapi: client-initiated close "85.*.*.*#54" [latest-26318]2026-11-20T18:55:29.617Z <httpapi:INFO> httpapi#1 API request from ::ffff:172.18.0.1: POST /api/v1/authorize [latest-26318]2026-11-20T18:55:29.618Z <httpapi:null> httpapi#1 checking ACLs for /api/v1/authorize user anonymous authorization none [latest-26318]2026-11-20T18:55:29.618Z <httpapi:null> httpapi#1 checking /api/v1/authorize against /api/v1/authorize ACL { "url": "/api/v1/authorize", "allow": true, "index": 4 } [latest-26318]2026-11-20T18:55:29.618Z <httpapi:INFO> httpapi#1 request for /api/v1/authorize from ::ffff:172.18.0.1 user anonymous auth none matches /api/v1/authorize ACL (#4): { "url": "/api/v1/authorize", "allow": true, "index": 4 } [latest-26318]2026-11-20T18:55:29.619Z <httpapi:WARN> httpapi#1 authorize admin from ::ffff:172.18.0.1 failed [latest-26318]2026-11-20T18:55:32.372Z <httpapi:INFO> httpapi#1 API request from ::ffff:172.18.0.1: POST /api/v1/authorize [latest-26318]2026-11-20T18:55:32.372Z <httpapi:null> httpapi#1 checking ACLs for /api/v1/authorize user anonymous authorization none [latest-26318]2026-11-20T18:55:32.373Z <httpapi:null> httpapi#1 checking /api/v1/authorize against /api/v1/authorize ACL { "url": "/api/v1/authorize", "allow": true, "index": 4 } [latest-26318]2026-11-20T18:55:37.386Z <httpapi:INFO> httpapi#1 request for /api/v1/authorize from ::ffff:172.18.0.1 user anonymous auth none matches /api/v1/authorize ACL (#4): { "url": "/api/v1/authorize", "allow": true, "index": 4 } [latest-26318]2026-11-20T18:55:37.386Z <httpapi:WARN> httpapi#1 authorize admin from ::ffff:172.18.0.1 failed [latest-26318]2026-11-20T18:55:40.937Z <httpapi:INFO> httpapi#1 API request from ::ffff:172.18.0.1: POST /api/v1/authorize [latest-26318]2026-11-20T18:55:40.937Z <httpapi:null> httpapi#1 checking ACLs for /api/v1/authorize user anonymous authorization none [latest-26318]2026-11-20T18:55:40.937Z <httpapi:null> httpapi#1 checking /api/v1/authorize against /api/v1/authorize ACL { "url": "/api/v1/authorize", "allow": true, "index": 4 } [latest-26318]2026-11-20T18:55:40.938Z <httpapi:INFO> httpapi#1 request for /api/v1/authorize from ::ffff:172.18.0.1 user anonymous auth none matches /api/v1/authorize ACL (#4): { "url": "/api/v1/authorize", "allow": true, "index": 4 } [latest-26318]2026-11-20T18:55:40.938Z <httpapi:WARN> httpapi#1 authorize admin from ::ffff:172.18.0.1 failed [latest-26318]2026-11-20T18:55:44.779Z <httpapi:INFO> httpapi#1 API request from ::ffff:172.18.0.1: POST /api/v1/authorize [latest-26318]2026-11-20T18:55:44.780Z <httpapi:null> httpapi#1 checking ACLs for /api/v1/authorize user anonymous authorization none [latest-26318]2026-11-20T18:55:44.780Z <httpapi:null> httpapi#1 checking /api/v1/authorize against /api/v1/authorize ACL { "url": "/api/v1/authorize", "allow": true, "index": 4 } [latest-26318]2026-11-20T18:55:44.780Z <httpapi:INFO> httpapi#1 request for /api/v1/authorize from ::ffff:172.18.0.1 user anonymous auth none matches /api/v1/authorize ACL (#4): { "url": "/api/v1/authorize", "allow": true, "index": 4 } [latest-26318]2026-11-20T18:55:44.780Z <httpapi:WARN> httpapi#1 authorize admin from ::ffff:172.18.0.1 failed [latest-26318]2026-11-20T18:55:47.512Z <httpapi:INFO> httpapi#1 API request from ::ffff:172.18.0.1: POST /api/v1/authorize [latest-26318]2026-11-20T18:55:47.512Z <httpapi:null> httpapi#1 checking ACLs for /api/v1/authorize user anonymous authorization none [latest-26318]2026-11-20T18:55:47.512Z <httpapi:null> httpapi#1 checking /api/v1/authorize against /api/v1/authorize ACL { "url": "/api/v1/authorize", "allow": true, "index": 4 } [latest-26318]2026-11-20T18:55:47.512Z <httpapi:INFO> httpapi#1 request for /api/v1/authorize from ::ffff:172.18.0.1 user anonymous auth none matches /api/v1/authorize ACL (#4): { "url": "/api/v1/authorize", "allow": true, "index": 4 } [latest-26318]2026-11-20T18:55:47.512Z <httpapi:WARN> httpapi#1 authorize admin from ::ffff:172.18.0.1 failed [latest-26318]2026-11-20T18:56:00.625Z <httpapi:INFO> httpapi#1 API request from ::ffff:172.18.0.1: POST /api/v1/authorize [latest-26318]2026-11-20T18:56:00.625Z <httpapi:null> httpapi#1 checking ACLs for /api/v1/authorize user anonymous authorization none [latest-26318]2026-11-20T18:56:00.625Z <httpapi:null> httpapi#1 checking /api/v1/authorize against /api/v1/authorize ACL { "url": "/api/v1/authorize", "allow": true, "index": 4 } [latest-26318]2026-11-20T18:56:00.625Z <httpapi:INFO> httpapi#1 request for /api/v1/authorize from ::ffff:172.18.0.1 user anonymous auth none matches /api/v1/authorize ACL (#4): { "url": "/api/v1/authorize", "allow": true, "index": 4 } [latest-26318]2026-11-20T18:56:00.627Z <httpapi:NOTICE> httpapi#1 authorize admin from ::ffff:172.18.0.1 succeeded; applications true [latest-26318]2026-11-20T18:56:00.786Z <httpapi:INFO> httpapi#1 redirecting /reactor to /reactor/en-US/ [latest-26318]2026-11-20T18:56:01.486Z <httpapi:INFO> httpapi#1 API request from ::ffff:172.18.0.1: GET /api/v1/lang [latest-26318]2026-11-20T18:56:01.486Z <httpapi:null> httpapi#1 checking ACLs for /api/v1/lang user anonymous authorization none [latest-26318]2026-11-20T18:56:01.486Z <httpapi:null> httpapi#1 checking /api/v1/lang against /api/v1/lang ACL { "url": "/api/v1/lang", "allow": true, "index": 8 } [latest-26318]2026-11-20T18:56:01.486Z <httpapi:INFO> httpapi#1 request for /api/v1/lang from ::ffff:172.18.0.1 user anonymous auth none matches /api/v1/lang ACL (#8): { "url": "/api/v1/lang", "allow": true, "index": 8 } [latest-26318]2026-11-20T18:56:01.743Z <wsapi:INFO> wsapi: connection from "85.*.*.*" via proxy ::ffff:172.18.0.1 [latest-26318]2026-11-20T18:56:01.785Z <wsapi:INFO> wsapi#1 client "85.*.*.*#55" authorized Deliberately failed login multiple times (enough to satisfy max_attempts), and then used a correct password at a point where IP should have been blocked. But as said, Synology is the culprit here.
  • The goodness of vera without the bad. Discuss installation problems and improvements.

    187 3k
    187 Topics
    3k Posts
    A
    OK - for those interested: I accidentally deleted the L_openLuup.lua file, which is listed immediately above the L_ShellyBridge.lua, which was the file I intended to delete. Amazing that everything else all still worked perfectly.
  • Got a question, a comment about the community or the forum? Ask away!

    14 146
    14 Topics
    146 Posts
    toggledbitsT
    When I'm working on my laptop, this section on the right takes up about 25% of my screen width, and I never look at it or touch anything in it. Is there a way to turn it off? I've been tinkering in the settings but not finding anything effective so far. [image: 1764095136947-3720b582-eae4-4731-b0fd-8ac167b24f01-image.png]
  • Blog posts from individual members. Feel free to talk about your project, your smart home setup!

    12 280
    12 Topics
    280 Posts
    G
    The locksmith is trying to persuade me to purchase the BE-TECH K35 touchscreen lock with both Wi-Fi and Bluetooth, claiming it's better than the Yale Assure Lock 2. What are your thoughts on this? Which one would you recommend? Here is the link to the Chinese brand BE-TECH: BE-TECH Smart Deadbolt K3S. The other smart lock I am considering is the Schlage Encode Plus. Thank you!

Recent Topics