Discussion Forum to share and further the development of home control and automation, independent of platforms.

    SmartHome Community

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Unsolved
    1. Home
    2. ArcherS
    • Setting Aeotec Siren 6 volume and duration not working

      Snowman

      Having trouble setting the Aeotec Siren 6 volume and the duration for a specific siren (alarm).

      Reactor version: latest-23010-7dd2c9e9

      Setting the tone value works fine. On the other end, what ever value I put under volume_level and duration has no effect.

      As usual, I am doing something wrong but can't figure out what.

      aca1fe53-792d-4da0-9ea9-8ad62cbff3ce-image.png

      Thanks in advance.

      Software
    • MSR controller status panel

      R

      Running latest version of MSR in Docker on Bullseye/Raspberry Pi CM4. Every time I "restart" MSR it returns to the default set of status panels. I add "Controller Status", but it disappears on every restart. Is this the planned behavior or do I have an issue somewhere?

      Multi-System Reactor
    • Super newbie here. Need help with lots of stuff

      A

      Hello guys. I'm currently building my own home and i want it to be kind of high tech and cool but i have actually never owned a smart device other than a smartphone and an old smart TV so i don't even know what exactly am i looking for. I will explain my idea and i am looking forward to somebody shining some light.

      Sooo - i was thinking about getting a WiFi controlled AC, TV, Washing machine, Dryer and smart switches for the lights. I suppose i need some kind of a assistant that connects to the wifi and can control all of these. Also i want an audio system - for the TV in the living room aaaand i also want to have 2 speakers in the bathroom which i have no idea where i would connect. I guees i need some kind of a receiver and amplifier for them to work correctly. But i also want that reciever to be hidden somewhere so it ahould be small and it also should be able to connect to the wifi i guess.
      So wgat exactly do i need so far. Would any wifi device connect to any assistant? Or am i lookng for particullar stuff... Will i be able for example to turn on my AC from outside the household for example when im at work? And can i also connect an alarm system of some type?

      How-To
    • Short survey

      P

      Hi,
      I am a student and recently i am working on smart home project and writing a seminar paper about the way users handle and manage IoT devices. I you have 3 min, please fill below survey. Its really short.
      Thank you in advance, I really appreciate everyone's help.

      General Discussion
    • Home Assistant add-on

      M

      I've done a bit of repackaging of MSR to make it work as an add-on under Home Assistant mostly for my own purposes but hopefully it makes it a bit easier to install and get going.

      GitHub - mrw298/hassio-reactor-addon GitHub - mrw298/hassio-reactor-addon

      Contribute to mrw298/hassio-reactor-addon development by creating an account on GitHub.

      Multi-System Reactor
    • Way to copy or export Alerts?

      cw-kid

      Hi

      Is there a way to copy text from an Alert or export them?

      I wanted to copy a device ID number that MSR says no longer exists on my Ezlo Plus controller.

      Thanks

      e7f39b4c-c283-4d47-a73a-e77974c0b2ae-image.png

      Multi-System Reactor
    • Alexa TTS volume does not update as expected

      CatmanV2

      Hardly a big deal, and likely user error. Bare metal install on Debian Bullseye

      Observed behaviour:
      TTS announcements are made with the correct volume. So a message to group 'Everywhere' with Volume 40 is announced. Asking an individual echo device to state its volume after the announcement gets the response 'This device is at volume 4'
      So far so good.

      Using the:

      x_vera_svc_bochicchio_com_VeraAlexa1.SetVolume

      In an MSR reaction appears to have no impact when either applied to the group 'Everywhere' or a specific device.

      So executing this reaction:
      Screenshot 2023-01-31 at 09.17.40.png

      Is acknowledged by the device (with a 'beep') and shows the Lua Log below:

      2023-01-31 09:21:45.778 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x5572399831f8 2023-01-31 09:21:45.779 openLuup.server:: GET /data_request?GroupZones=Office&DesiredVolume=10&DeviceNum=22&id=action&serviceId=urn%3Abochicchio-com%3AserviceId%3AVeraAlexa1&action=SetVolume&output_format=json&_r=1675156905777 HTTP/1.1 tcp{client}: 0x5572399831f8 2023-01-31 09:21:45.780 luup.call_action:: 22.urn:bochicchio-com:serviceId:VeraAlexa1.SetVolume 2023-01-31 09:21:51.670 luup.variable_set:: 22.urn:bochicchio-com:serviceId:VeraAlexa1.LatestResponse was: sending cmd:speak:<s>Volume Set</s><break time="0s" /> to dev:Office type:A32DOYMUN6DTXA serial:G090U50991550NLS cu... now: sending cmd:vol:10 to dev:Office type:A32DOYMUN6DTXA serial:G090U50991550NLS customerid:A1CVTZEBJIUFJI #hooks:0 2023-01-31 09:21:51.671 openLuup.server:: request completed (35 bytes, 1 chunks, 5891 ms) tcp{client}: 0x5572399831f8 2023-01-31 09:21:51.683 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x5572399831f8 2023-01-31 09:21:51.685 openLuup.server:: request completed (930 bytes, 1 chunks, 42818 ms) tcp{client}: 0x557239726708 2023-01-31 09:21:51.687 openLuup.server:: request completed (930 bytes, 1 chunks, 42548 ms) tcp{client}: 0x5572392c0fd8 2023-01-31 09:21:51.688 openLuup.server:: request completed (930 bytes, 1 chunks, 12501 ms) tcp{client}: 0x5572392c7f88 2023-01-31 09:21:51.692 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x5572392c7f88 2023-01-31 09:21:51.704 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x557239be10b8 2023-01-31 09:21:51.704 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=66666322&MinimumDelay=50&output_format=json&_r=1675156911703 HTTP/1.1 tcp{client}: 0x557239be10b8 2023-01-31 09:21:51.905 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=66666322&Timeout=60&MinimumDelay=1500&_=1675022474387 HTTP/1.1 tcp{client}: 0x5572392c0fd8 2023-01-31 09:21:53.042 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=66666322&Timeout=60&MinimumDelay=1500&_=1675079237873 HTTP/1.1 tcp{client}: 0x557239726708

      However direct interrogation of the device reveals the volume has not changed.

      I assume I'm doing something wrong or not understanding how this is meant to work?

      One other observation is that messages announce to the 'Everywhere' group appear to make the volume 'stick' where as messages to an individual device appear to revert to the previous volume setting.
      My expectation would be analagous to a radio i.e. the volume stays as it was last set, but happy to be corrected.

      TIA!

      C

      Vera/openLuup plugins
    • Include Entity by Name in Dynamic Group Controller

      Pabla

      Trying to figure out how I can include a list of entities that have "battery_level" in their ID without having to manually include them in a list. I have a group which selects all entities with the battery_power capability and filters them if they are dead. In HA there are quite a few entities that have the battery_power capability but don't actually report a battery percent (see screenshot below for an example), the entities I am interested in are the ones that contain battery_level in their ID.

      I tried the following in the config file but it hasn't worked:

      "dead_battery": select: - include_capability: battery_power - include_entity: "/^hass>battery_level/"

      What I think I am doing wrong here is that I am including entities with the batter_level capability which doesn't actually exist.

      b50a2bfe-1779-4467-8b91-c078ff9404ef-image.png

      Multi-System Reactor
    • Need help in finding the right smart switch for my kitchen lights

      M

      Hello,
      I have a kitchen light that can be controlled by two switches, using either to turn it off or on. I have been slowly changing things over to be a smart home but this is the first switch I am attempting to install.
      I am in a double wide modular home (mobile) that was built in 1994.
      At first I thought I would need a 3 way switch but when taking the normal switches apart I realized that was incorrect because the wiring on my switches are different than anything I could find online.
      For one a 3 way smart switch requires 5 wires and there are only 2 wires going into the primary switch with 3 wires going into the secondary switch from the primary switch (at least I think the 3 wires connect the two switches together). Images will be attached of the wiring.
      There are two wires (one black and one white) going into the first switch and 3 wires (black, white, and red) going out of that and into the second switch (I assume). The odd thing is the red wire going to the second switch is connected to the white wire going into the first switch and the white wire going into the second switch seems to be a bridge wire or a traveler wire. Not exactly sure. You will see what I mean in the images.
      I need to know what kind of smart switch I can use in this set up with one remaining a normal switch.
      Note that for some reason the images got switched around when uploading them. The image with 2 wires on one side and 3 on the other is what I think is the primary and the image with just 3 wires is the secondary.
      Primary.jpg Secondary.jpg

      General Discussion
    • [Solved] MSR actions aren't running anymore-- can't find what's broken

      E

      Suddenly my MSR actions aren't running anymore. I've had this before, but with an update to a new version it was fixed. see also

      https://smarthome.community/topic/987/msr-actions-aren-t-running-anymore-can-t-find-what-s-broken/3?_=1674661492589

      But an update from version 22240 to 22256 gave this time no result.

      The reactions aren't running correctly. Most of my MSR automations are use turn lights on/off, and time based automations nothing worked where MSR does his magic.

      I've also tested a bunch of things to see what's broken, here's what I've observed:
      -I can successfully flip lights on/off manually within Vera
      -I can successfully flip lights on/off manually within MSR's Entities section
      -the sensors are correctly reporting to Vera and MSR (I can see when they're switch on/off)
      -the rules within MSR are working correctly, I can see when they flip to 'true' of 'false' '
      '
      But I cannot successfully run the "Set Reaction" and "Reset Reaction" within MSR (by hitting the 'play' button)
      But the play buttons on the entitiy action in the "Set Reaction" and in "Reset Reaction" they work well.

      Can someone help me to get MSR working again

      MSR is running bare metal on Rpi4

      Multi-System Reactor
    • Reactor (Multi-System/Multi-Hub) Announcements

      toggledbits

      Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.

      Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
      Multi-System Reactor
    • My MQTTController templates contribution

      Crille

      I've made a few templates for MQTTController, mostly Zigbee2MQTT, and sharing them to the community if anyone else would find use for them.

      GitHub - calmen77/MSR-mqtt_templates: MQTT templates for Multi-hub Reactor GitHub - calmen77/MSR-mqtt_templates: MQTT templates for Multi-hub Reactor

      MQTT templates for Multi-hub Reactor. Contribute to calmen77/MSR-mqtt_templates development by creating an account on GitHub.

      These are the ones I'm using but I'm happy to add more Zigbee2MQTT templates if needed.

      Happy Holidays!

      Multi-System Reactor
    • Sonoff zbmini-l and philips hue

      L

      Hello!

      I have recently begun making my home smarter, and I've run into some trouble while trying to get my Sonoff zbmini-l, which is connected to my Philips Hue bridge, to work properly. I am able to control it individually, but not through scenes or with the Google Home app. Has anyone else encountered this problem and know of a fix? Additionally, I have another Zigbee bridge, but I am unable to find the Sonoff device on it.

      Thank you in advance for your help!

      PS: I am very new to this.

      Zigbee
    • Ezlo Controller - Error Incompatible serialization data - api cloud Timeout

      N

      Hi,
      Connection to Ezlo is going in timeout with api-cloud.ezlo. This happens in anonymous_access set to false or in true.
      A lot of Error Incompatible serialization data (in the log I cut many more).
      In MSR controller status, Ezlo is in green icon but after sometime devices start to not respond.
      Can I have some help?

      Synology Nas - INTEL - DSM 7.1.1-42962 Update 3
      Ezlo Hub Model: h2.1 - v.2.0.35.2156.5
      Docker Container
      Reactor latest-23010-7dd2c9e9

      Thanks in advance

      [latest-23010]2023-01-20T18:11:08.069Z <app:null> Reactor build latest-23010-7dd2c9e9 starting on v16.15.1 [latest-23010]2023-01-20T18:11:08.071Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #42962 SMP Tue Oct 18 15:07:03 CST 2022; locale (undefined) [latest-23010]2023-01-20T18:11:08.071Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-23010]2023-01-20T18:11:08.071Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-23010]2023-01-20T18:11:08.085Z <app:INFO> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-23010]2023-01-20T18:11:08.122Z <app:INFO> Loaded locale en-US [latest-23010]2023-01-20T18:11:08.128Z <Structure:null> Module Structure v22323 [latest-23010]2023-01-20T18:11:08.131Z <Capabilities:null> Module Capabilities v22356 [latest-23010]2023-01-20T18:11:08.166Z <Capabilities:NOTICE> System capabilities loaded from core distribution, data version 22356 revision 1 [latest-23010]2023-01-20T18:11:08.211Z <Plugin:null> Module Plugin v22300 [latest-23010]2023-01-20T18:11:08.238Z <TimerBroker:null> Module TimerBroker v22283 [latest-23010]2023-01-20T18:11:08.241Z <Entity:null> Module Entity v22353 [latest-23010]2023-01-20T18:11:08.247Z <Controller:null> Module Controller v22323 [latest-23010]2023-01-20T18:11:08.261Z <default:null> Module Ruleset v22293 [latest-23010]2023-01-20T18:11:08.262Z <default:null> Module Rulesets v22146 [latest-23010]2023-01-20T18:11:08.271Z <GlobalExpression:null> Module GlobalExpression v22146 [latest-23010]2023-01-20T18:11:08.296Z <Predicate:null> Module Predicate v22345 [latest-23010]2023-01-20T18:11:08.317Z <AlertManager:null> Module AlertManager v22283 [latest-23010]2023-01-20T18:11:08.322Z <Rule:null> Module Rule v22345 [latest-23010]2023-01-20T18:11:08.327Z <GlobalReaction:null> Module GlobalReaction v22324 [latest-23010]2023-01-20T18:11:08.329Z <Engine:null> Module Engine v23001 [latest-23010]2023-01-20T18:11:08.335Z <httpapi:null> Module httpapi v22347 [latest-23010]2023-01-20T18:11:08.400Z <wsapi:null> Module wsapi v22320 [latest-23010]2023-01-20T18:11:08.400Z <app:NOTICE> Starting Structure... [latest-23010]2023-01-20T18:11:08.460Z <InfluxFeed:null> Module InfluxFeed v22286 [latest-23010]2023-01-20T18:11:08.462Z <Structure:INFO> Structure#1 starting plugin influx (InfluxFeed) [latest-23010]2023-01-20T18:11:08.463Z <Structure:INFO> Structure#1 loading controller interface vera (VeraController) [latest-23010]2023-01-20T18:11:08.517Z <TaskQueue:null> Module TaskQueue 21351 [latest-23010]2023-01-20T18:11:08.518Z <VeraController:null> Module VeraController v22325 [latest-23010]2023-01-20T18:11:08.548Z <Structure:INFO> Structure#1 loading controller interface ezlo (EzloController) [latest-23010]2023-01-20T18:11:08.635Z <EzloController:null> Module EzloController v22344 [latest-23010]2023-01-20T18:11:08.867Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_613c8f94129e291209006add: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:08.868Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:08.869Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_613c9094129e291209006ae4: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:08.869Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:08.902Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_61437a57129e29124dfcd791: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:08.902Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:08.925Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_61437a58129e29124dfcd7a0: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:08.925Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:08.942Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_6198168b129e2918c5ce97bc: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:08.943Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:08.945Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_61981760129e2918c5ce97cb: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:08.945Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:08.945Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_61981770129e2918c5ce97d0: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:08.945Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:08.946Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_6198177e129e2918c5ce97d5: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:08.946Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:08.947Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_6198178b129e2918c5ce97da: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:08.947Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:08.947Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_6198179b129e2918c5ce97df: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:08.947Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:08.948Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_619817a6129e2918c5ce97e4: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:08.948Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:08.948Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_619817b2129e2918c5ce97e9: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:08.949Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:09.012Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_626d5d16129e291244463492: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:09.012Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:09.013Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_626d5d16129e291244463494: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:09.013Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:09.013Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_626d64d4129e2912444634a8: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:09.014Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:09.014Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_626d64d5129e2912444634af: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:09.014Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:09.015Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_626d64d5129e2912444634b2: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:09.015Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:09.039Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_629e6ec1129e2912b034351f: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:09.040Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:09.040Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_629e6ec2129e2912b0343529: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:09.040Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:09.041Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_629e6ec3129e2912b034352b: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:09.041Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:09.042Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_629e6ec3129e2912b034352d: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:09.042Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:09.043Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_629e6ec3129e2912b034352f: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:09.043Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:09.043Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_62a6d99a129e29123e7b0a8f: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:09.043Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:09.044Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_62a6d99b129e29123e7b0a9d: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:09.044Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:09.060Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity room_629687b6129e2912430f2de2: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:09.060Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Group.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:09.061Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity room_62a66189129e29124345f791: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:09.061Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Group.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:09.128Z <Structure:INFO> Structure#1 loading controller interface groups (DynamicGroupController) [latest-23010]2023-01-20T18:11:09.146Z <DynamicGroupController:null> Module DynamicGroupController v22313 [latest-23010]2023-01-20T18:11:09.178Z <Controller:WARN> DynamicGroupController#groups failed (1) to restore entity earthquake_entities: [Error] Incompatible serialization data; can't unserialize [-] [latest-23010]2023-01-20T18:11:09.178Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Group.unserialize (/opt/reactor/server/lib/Entity.js:452:19) at /opt/reactor/server/lib/Controller.js:794:70 at Array.forEach (<anonymous>) at DynamicGroupController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36) at new Controller (/opt/reactor/server/lib/Controller.js:395:43) at new DynamicGroupController (/opt/reactor/server/lib/DynamicGroupController.js:207:9) at /opt/reactor/server/lib/Controller.js:451:37 [latest-23010]2023-01-20T18:11:09.186Z <Structure:INFO> Structure#1 loading controller interface weather (OWMWeatherController) [latest-23010]2023-01-20T18:11:09.219Z <OWMWeatherController:null> Module OWMWeatherController v22294 [latest-23010]2023-01-20T18:11:09.222Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [latest-23010]2023-01-20T18:11:09.227Z <SystemController:null> Module SystemController v22306 [latest-23010]2023-01-20T18:11:09.231Z <Structure:INFO> Structure#1 loading controller interface virtual (VirtualEntityController) [latest-23010]2023-01-20T18:11:09.238Z <VirtualEntityController:null> Module VirtualEntityController v22325 [latest-23010]2023-01-20T18:11:09.348Z <Structure:INFO> Starting controller VeraController#vera [latest-23010]2023-01-20T18:11:09.348Z <VeraController:NOTICE> VeraController#vera starting... [latest-23010]2023-01-20T18:11:09.357Z <Controller:INFO> VeraController#vera loaded vera capabilities ver 22253 rev 1 format 1 [latest-23010]2023-01-20T18:11:09.394Z <Controller:INFO> VeraController#vera loaded implementation data ver 22345 rev 1 format 1 [latest-23010]2023-01-20T18:11:09.394Z <Structure:INFO> Starting controller EzloController#ezlo [latest-23010]2023-01-20T18:11:09.397Z <Controller:INFO> EzloController#ezlo loaded ezlo capabilities ver 22266 rev 1 format 1 [latest-23010]2023-01-20T18:11:09.408Z <Controller:INFO> EzloController#ezlo loaded implementation data ver 22344 rev 1 format 1 [latest-23010]2023-01-20T18:11:09.408Z <Structure:INFO> Starting controller DynamicGroupController#groups [latest-23010]2023-01-20T18:11:09.413Z <Controller:NOTICE> Controller DynamicGroupController#groups is now online. [latest-23010]2023-01-20T18:11:09.413Z <Structure:INFO> Starting controller OWMWeatherController#weather [latest-23010]2023-01-20T18:11:09.503Z <Structure:INFO> Starting controller SystemController#reactor_system [latest-23010]2023-01-20T18:11:09.506Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. [latest-23010]2023-01-20T18:11:09.537Z <Structure:INFO> Starting controller VirtualEntityController#virtual [latest-23010]2023-01-20T18:11:09.549Z <Controller:INFO> VirtualEntityController#virtual loaded virtualentity capabilities ver 22263 rev 2 format 1 [latest-23010]2023-01-20T18:11:09.550Z <Controller:INFO> VirtualEntityController#virtual loaded implementation data ver 22280 rev 1 format 1 [latest-23010]2023-01-20T18:11:09.556Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute members [latest-23010]2023-01-20T18:11:09.556Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute empty [latest-23010]2023-01-20T18:11:09.557Z <EzloController:INFO> EzloController#ezlo device mapping data loaded; checking... [latest-23010]2023-01-20T18:11:09.566Z <EzloController:INFO> EzloController#ezlo: connecting to hub "90000464" [latest-23010]2023-01-20T18:11:09.570Z <VirtualEntityController:INFO> VirtualEntityController#virtual configuring virtual .DefaultMode (vec01) [latest-23010]2023-01-20T18:11:09.571Z <VirtualEntityController:INFO> VirtualEntityController#virtual configuring virtual .GuestMode (vec02) [latest-23010]2023-01-20T18:11:09.571Z <VirtualEntityController:INFO> VirtualEntityController#virtual configuring virtual .PartyMode (vec03)
      Multi-System Reactor
    • MQTT log levels & log rotation

      tunnus

      Trying to set log level for MQTT to the lowest possible, is it in practise level 4? Also, would like to set maximum size and log rotation, but the following setup in logging.yaml did not work:

      MQTTController: level: 4 streams: - type: file maxsize: 2 keep: 2

      Using the latest build (23010).

      Multi-System Reactor
    • Help. Installing Reactor on Home Assistant.

      A

      Good afternoon. I want to connect Reactor to HA. HA is installed on Proxmox. Proxmox is installed on a Beelink U59 PRO mini PC. Studied the installation instructions ( https://reactor.toggledbits.com/docs/Installation / ) but I didn't understand how to do it (I'm a weak linux user). Help, give detailed instructions on how to install MSR.
      Reactor is a cool plugin, I use it on VeraPlus, but gradually I want to switch to HA.
      Thanks.

      Multi-System Reactor
    • Neural TTS with Sonos & Hubitat

      tunnus

      My migration from Vera to Hubitat is almost ready, only Sonos & Visonic (alarm system) remain on Vera. Hubitat has a Sonos integration, but it lacks neural voices for TTS so I've been looking for an alternative solution.

      @a-lurker hinted that there's a mqtt version for Sonos so I went that route and installed Docker containers for both sonos2mqtt and sonos-tts-polly. It turned out that I won't need mqtt for this at all, and I can utilize Hubitat's integration and just use the latter container for Polly.

      Did create a separate user on AWS only for TTS usage (there's an access right called "AmazonPollyReadOnlyAccess") and configured key, secret & cache in the container. Then I made the following test rule / reaction in MSR:

      Screenshot 2023-01-20 at 15.32.23.png Screenshot 2023-01-20 at 15.32.38.png

      So if anyone else has the same (or similar) setup, here's one way to achieve neural TTS with Sonos.

      Multi-System Reactor
    • Cheapest platform on which to run MSR

      T

      Please can anyone give me advice on a cheap way to run MSR (both initial cost and ongoing electricity cost). I currently run it on my QNAP network drive (which works very well incidentally). However, this draws a constant 35Watts (£90/yr @ 30p/kWh) and given the recent rise in fuel costs I am evaluating the best way forwards. Note, I only really need to turn my QNAP on for an hour a week to back-up my computer data. I understand that MSR can run on a Raspberry PI, but I am not competent with Linux! Thanks.

      Multi-System Reactor
    For those who registered but didn't received the confirmation email, please send an email to support@smarthome.community with the email you used
    A
    • Profile
    • Following 0
    • Followers 0
    • Topics 10
    • Posts 258
    • Best 66
    • Controversial 0
    • Groups 0

    ArcherS

    @ArcherS

    84
    Reputation
    34
    Profile views
    258
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    ArcherS Unfollow Follow

    Best posts made by ArcherS

    • RE: openLuup: Tasmota MQTT Bridge

      Thought it could be good for future users to give a short write up on how to set up Tasmota devices reporting sensors into OpenLuup with the new Tasmota bridge.

      First setup the Tasmota device:
      Browse to the Tasmota device IP and then select "Configuration"
      5037d753-42b7-4014-a4d9-1fd120adfcbb-image.png Go into Configuration Other
      Make sure "Mqtt enable" is set and give a Device Name
      61776069-bf6e-4d2d-b9a5-95451c08b62c-image.png Then into Configuration MQTT
      Give IP adress and port of OpenLuup Mqtt server
      Give a Client name
      Set user and password
      Set topic name
      701d2925-8897-4a7b-8bac-55f13654213b-image.png

      If you want to change how often the Tasmota device pushes data over Mqtt you can do that in the Console for the Tasmota by using the "TelePeriod" command. By default TelePeriod is set to 300 seconds, e.g. "TelePeriod 60" sets it to once every minute. (Just typing "TelePeriod" shows the current value.)

      Second set up OpenLuup:
      Paste the following into Lua Startup:

      luup.attr_set ("openLuup.MQTT.Port", 1883)
      luup.attr_set ("openLuup.MQTT.Username", "luup")
      luup.attr_set ("openLuup.MQTT.Password", "password")
      luup.attr_set ("openLuup.MQTT.PublishVariableUpdates", true) -- Not requred for Tasmota, publish every variable update if wanted
      

      Save and reload Luup engine, you should now get the Tasmota bridge in OpenLuup
      218be9a6-ec10-471a-8e96-65e2462e2d5c-image.png

      You should also get the Tasmota device you setup above
      9eb70057-37e2-4f77-a4c1-2dc5462d5840-image.png On my OpenLuup it got placed in the room "Tasmota".

      Next step is to set up devices for the sensor data you want to get from the Tasmota device. This data is pushed into variables for the Tasmota device (if you hover above a variable name you see the sensor, e.g. "BME280"):
      47c8cd4f-bd2d-499c-86db-0903c792c753-image.png

      Download the plugin "Virtual Sensor" if you do not have it.
      099ba5c9-a5f5-4200-ba6e-5f8d32021544-image.png Go into Virtual Sensors, tab "Virtual Sensors" and create the new virtual sensors you need for the data you want to display from the Tasmota device, you want one virtual sensor per value.
      4deddfff-45bf-4af5-9379-1f45a1ab6644-image.png

      Next step is to set the data from the Tasmota variables to the corresponding virtual sensors.
      Go into the Virtual Sensor plugin, into the tab "Virtual Sensors"
      Select the Tasmota device in the first drop down and then the variable in the second:

      6ba15680-9d35-41bb-a2e2-df5d85115094-image.png

      Job done! Now repeat for all the variables you wish to add into OpenLuup. 🙂

      posted in Plugins
      A
      ArcherS
    • RE: Tinkering with Tasmota sensors

      @therealdb I built my outdoor sensor from what I had in the garage, very much DIY in other words. 🙂
      I used an outdoor junction box, to this I hot glued a plastic dome from an old motion sensor for the light sensor. I also added a short piece of plastic pipe for the BME280 so that it is outside of the box to get better readings. To keep spiders etc out of the pipe I added an old stainless mesh dome to the end of it.
      In the box is also a 240V/5V transformer.

      The intention is to mount it on the north wall of the house outside of the sun. At the moment it is laying on the window sill.
      utesensor.jpg

      Some more small tips on rules:
      It is possible to create up to three rules for each sensor.
      It is possible to have several "Do" stamements in each rule.
      Rule<x> ON <trigger1> DO <command> ENDON ON <trigger2> DO <command> ENDON ...

      It is very easy to find out the name of each sensor for using in the rules by looking at: http://IP_address/cm?cmnd=Status%2010

      A rule is defined by pasting the rule from e.g. notepad to the Console window of the sensor.
      After that the rule needs to be enabled by Rule1 1, Rule2 1 etc.
      After enabling a rule check in the console that the rule is sending values.
      A rule is deactivated by Rule1 0 etc.
      To see the contents of a rule just type Rule1 etc.
      To delete a rule type Rule1 " etc.

      My recommendation is for people to look at the Tasmota rules documentation, it is very good.
      .
      //ArcherS

      posted in Hardware
      A
      ArcherS
    • RE: Help with Z-Way plugin

      Thank's for a really quick reply! That indeed did the trick, I knew it was something easy I missed.
      Now I just need to go through my Reactors and re-map my z-way devices. Not too much work.

      //ArcherS

      posted in Zway Bridge
      A
      ArcherS
    • RE: Remotec ZRC90

      Checked with v20.7.14 and the "sl_CentralScene" variable is updated with the key pressed.

      Thanks again for the update! 🙂

      posted in openLuup
      A
      ArcherS
    • RE: Tinkering with Tasmota sensors

      Some time ago I stumbled on some rather nice looking temperature and humidity sensors from Xiaomi and how to get them to communicate with a Tasmota ESP32 with BLE.

      Xiaomi temp sensor.jpg

      I ordered an ESP32 on Ebay and a three-pack of the sensors from Bangood. The sensors are quite cheap, you can find them for €4-5 in the usual sites.

      The sensors are quite small, approx 4.5cm and run on a CR2032 battery. Time will tell how long the batteries will last. With the custom firmware you can change the reporting interval.

      I have now been running this for little over two months and it works surprisingly well, bringing the temperature and humidity data into OpenLuup.

      In short what you do is the following:

      • Download the beta Tasmota for ESP32, flashing is a bit different from the regular Tasmota but pretty straight forward

      • Enable bluetooth with setoption115 1

      • The Xiaomi sensors can used both with stock firmware and flashed with a custom firmware that removes the encryption from the transmit of data, I flashed them with a Win10 laptop and it was super easy. You can even roll back the original firmware if you want.

      The Xiaomi sensors will then be included by the ESP32 Tasmota device and can be sent to OpenLuup with rules, brought in with Sitesensor or now via MQTT.

      73f83e12-af75-458a-b021-cd9d413260fc-image.png

      posted in Hardware
      A
      ArcherS
    • RE: External antenna on razberry board

      It seems as if it is possible to modify it with an external antenna.
      Here is an article on how to modify the Razberry2 EU:
      Modify Razberry2 (translated)

      Is is in Swedish, hopefully the translated text is understandable. 🙂
      In short you cut away the built-in antenna and solder on an antenna connector for the external antenna. You of course need an antenna for the frequency in your country, the article is for 868 MHz (EU).

      //ArcherS

      posted in Z-Wave.me
      A
      ArcherS
    • RE: Easy way to convert to SSD from SD card on Pi with MSR

      @matteburk if you have a Pi 3B+ then you are in luck since it will boot from USB without doing anything.
      If it is a Pi 3B then you have to change a "USB boot bit", see e.g. this instruction.

      I took the easy route and bought a new Pi 3B+ when I moved my Z-way server to SSD from SD. They are quite cheap anyway and I guess I can get use of the Pi 3B for something else later on.

      As @toggledbits says the Pi's are a bit picky on SSD adapters. I had two old 2.5" cases laying around, one worked and the other did not. The SSD migration cable that came with a Samsung SSD that I used for another PC also works.

      Edit: And if you buy a new Pi 4 they should now also have USB boot out of the box. Assuming the box has not been sitting on the shelf in the store for too long of course. 🙂

      posted in General Discussion
      A
      ArcherS
    • RE: openLuup: MQTT server

      @akbooer thanks for the assistance and patience, now it works! 🙂

      Edit: Added the humidity to the code:

      local json = require "openLuup.json"
      
      function MyMQTThandler (topic, message)
        local info = json.decode (message)
        local t = info.AM2301.Temperature
        local h = info.AM2301.Humidity
        luup.variable_set ("urn:upnp-org:serviceId:TemperatureSensor1", "CurrentTemperature",  t, 216)
        luup.variable_set ("urn:micasaverde-com:serviceId:HumiditySensor1", "CurrentLevel",  h, 228)
      end
      
      luup.register_handler ("MyMQTThandler", "mqtt:tele/tasmota_test/SENSOR")
      
      posted in openLuup
      A
      ArcherS
    • RE: Tinkering with Tasmota sensors

      @buxton yes it opens up new possibilities. On the Tasmota bluetooth webpage some other devices are listed, e.g. a soil humidity meter.

      So far it has been quite stable for more than two months.
      The Tasmota ESP32 is still beta, I assume it will get better over time.

      I will also make the ESP32 to report over Mqtt now that OpenLuup has support for it, hopefully that will make the setup even more stable.

      posted in Hardware
      A
      ArcherS
    • RE: Luup reload required after server reboot

      @rafale77 I tried this way of delaying at startup and it works fine. It does not cause delays when reloading luup which is a clear benefit.

      posted in openLuup
      A
      ArcherS

    Latest posts made by ArcherS

    • RE: Power monitoring options

      Like @Crille I have an electrical meter with a P1 data port. I use a DIY ESP8266 reader that I described some time ago in this thread. Since writing my post I have changed the software on the ESP, the version I am using now publishes the meter data approx every 10s as a json.

      A good wifi solution for the whole house if lacking a dataport is to use a Shelly 3EM. It is a three clamp meter that can measure all three incoming phases, assuming you have that. I have a few of these for measuring both single and multiple phase consumers, e.g. a two-phase water heater. It reports both energy, power, voltage and current per phase.
      The only downside I can see is that the clamps are a bit big, so some space is required to get them in place around the incoming power lines.

      posted in Vera
      A
      ArcherS
    • RE: OpenLuup installation

      So I thought I would report back on the restore of openLuup onto my new server.

      What I did was roughly:

      • set up a fresh install of openLuup on my new server
      • stop the old and new server with
        http://192.168.1.xxx:3480/data_request?id=exit
      • copy all the content from the folders "files" and "icons" from the old server to the new server (this I had to do with sudo rights in the Terminal)
      • copy the latest backup file to the backup foder on the new server
      • run the reload openLuup script from the cmh-ludl folder
        ./openLuup_reload backup/backup.openLuup-nnnn.lzap
      • restart the server

      After this the new server contained all the items from the old installation. Most things has worked, but some things did not.

      I had to reinstall the Z-way plugin (plugins->update now button) to get it working, the login fields did not exist (see above) until I did that. After the reinstall I could log in and get it to work.
      I also had to reinstall Reactor and the Telegram plugins (plugins->update now button).
      Reactor said the database was old and the update button was not there so it could not be updated.
      Telegram did not work but everything looked as it should. After the update it worked.
      The only remaining oddity from this error is that I now have a Reactor sensor that I cannot remove. It crashed during editing it before I realised that the plugin did not fully work (it is now empty when I open it, so no delete button).
      I recreated the logic in a new sensor and disabled the old one.
      Any advice on how I can remove the failed sensor would be appreciated. 🙂

      Yesterday I discovered that my Remotec ZRC90 remotes did not work. The sl_CentralScene did not update when pressing the buttons on the remote. Based on the advice in this thread I reinstalled the development version of the Z-way plugin from the App Store and then it worked. Strange problem, unclear what could be the reason for it.

      So a few quirks here and there, it seems as if some data does not survive the restore, unclear why.

      @akbooer is it better to do a reinstall from App Store when restoring a backup of from of from Plugins->update now button? Or should it not matter? 🙂

      As a small side note I also reinstaller Grafana onto the new server. I found a useful tip that it is possible to copy the grafana.db file from the old server to move all of the configuration. This worked perfectly at least on my 8.1.1 installation. The only issue is to make sure to have the same version Grafana on the new server as on the old. This is is easy to do with the help of their webpage.

      posted in openLuup
      A
      ArcherS
    • RE: OpenLuup installation

      @catmanv2 MSR is definitely on the list of things to setup and try. It seems really nice and a natural step forward from Reactor. 🙂

      posted in openLuup
      A
      ArcherS
    • RE: OpenLuup installation

      @catmanv2 yes it can quickly become tricky to have back-ups of everything. I have no clear strategy but some bits-and-pieces that I use.

      For the Zway server that is running on a separate Pi I make a complete image with Win32 Disk Imager when I update the server. I run it on a 2.5" ssd, so I have two. That way I can revert back if it crashes hopefully.

      For openLuup I do manual backups (Table Controllers->Backup Controller) before changing things. I keep them on another PC for safe keeping. A fresh install and copying the files and icon folders before running the reload script seems to work ok.

      Now that I look at migrating to Proxmox I will test another strategy. In Proxmox it is super easy to make a complete copy of the VM. This can then be deployed in a few minutes, no need to set everything up from scratch again. My idea is to use this as a fall back also in combination with openLuup backups. Also to use it when testing things on a temporary VM before updating the live VM.

      I have not moved over to MSR yet so thte Reactor logic is part of the openLuup backups.

      The plan is also to run my Home Assistant on the Proxmox server to be able to have a live server and a test server in parallel.

      posted in openLuup
      A
      ArcherS
    • RE: OpenLuup installation

      @akbooer that seems to have worked quite nicely when checking quickly on all the devices, thank once more for the quick response. 🙂

      One thing that does not work is the connection to the Z-Way server. The devices do not update when changing them either in the new openLuup or in the Zway UI.
      I suspect I need to login again to connect the bridge with the server.
      If I remember it correctly I should do that in the Console under "actions" for the Z-Way bridge. However it is empty there:

      8253efd8-3e8f-4461-9a26-1ff3bd1be79f-image.png

      Any ideas on that one?

      Edit: I have version 21.1.19 of the Z-Way bridge. On my old installation the login fields are there under "actions".
      fd1c629f-ffc9-4517-9324-43b6160d03a8-image.png

      Edit 2: I updated the Z-way plugin. This gave me a second plugin, also the username/passwd dialogues reappeared on the old bridge.
      After having deleted the new bridge, logged in into the old one and restarted openLuup it seems to work. I will see if anything looks strange.

      posted in openLuup
      A
      ArcherS
    • RE: OpenLuup installation

      Next question. 🙂

      When restoring from a backup file from another OpenLuup what is the best approach to get everything up and running on the new openLuup installation with icons, plugins etc?

      Should I manually copy e.g. icons and something else before restoring. Also do I have to install the plugins again?

      //ArcherS

      posted in openLuup
      A
      ArcherS
    • RE: OpenLuup installation

      That did the trick! 🙂

      Alpine and Docker, need to look at that also later on. 🙂

      Thank's @CatmanV2 and @akbooer for your swift help!

      posted in openLuup
      A
      ArcherS
    • RE: OpenLuup installation

      Hi,

      I am trying to install openLuup on a new Debian 11 server. It is a clean install Debian 11 running as a VM on Proxmox.

      I have installed lua 5.1, lua-socket, lua-filesystem and lua-sec.

      When installing openLuup with "# lua5.1 openLuup_install.lua" I get the following response:

      debian-pve:~/cmh-ludl$ lua5.1 openLuup_install.lua
      openLuup_install   2019.02.15   @akbooer
      getting openLuup version tar file from GitHub branch master...
      un-zipping download files...
      getting dkjson.lua...
      creating required files and folders
      initialising...
      downloading and installing AltUI...
      sh: 1: curl: not found
      lua5.1: ./openLuup/L_AltAppStore.lua:567: attempt to call upvalue 'next_file' (a nil value)
      stack traceback:
      	./openLuup/L_AltAppStore.lua:567: in function 'update_plugin_job'
      	openLuup/init.lua:254: in main chunk
      	[C]: ?
      openLuup downloaded, installed, and running...
      visit http://192.168.1.210:3480 to start using the system
      olsson@debian-pve:~/cmh-ludl$ Sat Aug 27 13:35:31 2022	device 2 '    openLuup' requesting reload
      

      When I try to go to the url "http://192.168.1.210:3480" I get the following response:

      No handler for data_request?id=lr_ALTUI_Handler
      

      In other words it seems as if there is a problem starting AltUI.

      If I instead go to the Console (http://192.168.1.210:3480/console) openLuup is up and running.

      The startup_log in the Console reads:

      2022-08-27 13:35:31.488   :: openLuup STARTUP :: /home/olsson/cmh-ludl
      2022-08-27 13:35:31.488   openLuup.init::        version 2021.06.14  @akbooer
      2022-08-27 13:35:31.489   openLuup.scheduler::   version 2021.03.19  @akbooer
      2022-08-27 13:35:31.510   openLuup.io::          version 2021.03.27  @akbooer
      2022-08-27 13:35:31.510   openLuup.mqtt::        version 2021.06.08  @akbooer
      2022-08-27 13:35:31.511   openLuup.wsapi::       version 2019.08.12  @akbooer
      2022-08-27 13:35:31.511   openLuup.servlet::     version 2021.04.30  @akbooer
      2022-08-27 13:35:31.511   openLuup.client::      version 2019.10.14  @akbooer
      2022-08-27 13:35:31.512   openLuup.server::      version 2020.03.26  @akbooer
      2022-08-27 13:35:31.518   openLuup.scenes::      version 2021.06.02  @akbooer
      2022-08-27 13:35:31.520   openLuup.chdev::       version 2021.05.04  @akbooer
      2022-08-27 13:35:31.521   openLuup.userdata::    version 2021.04.30  @akbooer
      2022-08-27 13:35:31.521   openLuup.requests::    version 2021.02.20  @akbooer
      2022-08-27 13:35:31.521   openLuup.gateway::     version 2021.05.08  @akbooer
      2022-08-27 13:35:31.522   openLuup.smtp::        version 2018.04.12  @akbooer
      2022-08-27 13:35:31.523   openLuup.historian::   version 2021.06.12  @akbooer
      2022-08-27 13:35:31.523   openLuup.luup::        version 2021.05.14  @akbooer
      2022-08-27 13:35:31.524   openLuup.pop3::        version 2018.04.23  @akbooer
      2022-08-27 13:35:31.524   openLuup.compression:: version 2016.06.30  @akbooer
      2022-08-27 13:35:31.524   openLuup.timers::      version 2021.05.23  @akbooer
      2022-08-27 13:35:31.524   openLuup.logs::        version 2018.03.25  @akbooer
      2022-08-27 13:35:31.524   openLuup.json::        version 2021.05.01  @akbooer
      2022-08-27 13:35:31.524   luup.create_device:: [1] D_ZWaveNetwork.xml /  /    ()
      
      2022-08-27 13:35:31.525   openLuup.chdev:: ERROR: unable to read XML file I_ZWave.xml
      
      2022-08-27 13:35:31.530   luup.create_device:: [2] D_openLuup.xml / I_openLuup.xml / D_openLuup.json   (openLuup)
      2022-08-27 13:35:31.530   openLuup.init:: loading configuration user_data.json
      2022-08-27 13:35:31.530   openLuup.userdata:: loading user_data json...
      2022-08-27 13:35:31.532   luup.variable_set:: 2.openLuup.HouseMode was: EMPTY now: 1 #hooks:0
      2022-08-27 13:35:31.532   openLuup.userdata:: loading rooms...
      2022-08-27 13:35:31.532   openLuup.userdata:: ...room loading completed
      2022-08-27 13:35:31.532   openLuup.userdata:: loading devices...
      2022-08-27 13:35:31.532   luup.create_device:: [1] D_ZWaveNetwork.xml /  /    ()
      
      2022-08-27 13:35:31.532   openLuup.chdev:: ERROR: unable to read XML file I_ZWave.xml
      
      2022-08-27 13:35:31.534   luup.create_device:: [3] D_AltAppStore.xml / I_AltAppStore.xml / D_AltAppStore.json   (urn:schemas-upnp-org:device:AltAppStore:1)
      2022-08-27 13:35:31.534   openLuup.userdata:: loading scenes...
      2022-08-27 13:35:31.534   openLuup.userdata:: number of scenes = 0
      2022-08-27 13:35:31.534   openLuup.userdata:: ...scene loading completed
      2022-08-27 13:35:31.534   openLuup.userdata:: loading installed plugin info...
      2022-08-27 13:35:31.534   openLuup.userdata:: [openLuup] openLuup (21.7.25)
      2022-08-27 13:35:31.534   openLuup.userdata:: [AltAppStore] Alternate App Store (20.3.30)
      2022-08-27 13:35:31.534   openLuup.userdata:: [VeraBridge] VeraBridge (not.installed)
      2022-08-27 13:35:31.534   openLuup.userdata:: [8246] Alternate UI (not.installed)
      2022-08-27 13:35:31.534   openLuup.userdata:: [Z-Way] Z-Way (not.installed)
      2022-08-27 13:35:31.534   openLuup.userdata:: [Arduino] MySensors (not.installed)
      2022-08-27 13:35:31.534   openLuup.userdata:: ...user_data loading completed
      2022-08-27 13:35:31.534   openLuup.init:: running _openLuup_STARTUP_
      2022-08-27 13:35:31.534   luup_log:0: startup code completed
      2022-08-27 13:35:31.534   openLuup.init:: init phase completed
      2022-08-27 13:35:31.534   :: openLuup LOG ROTATION :: (runtime 0.0 days) 
      

      Any ideas on what could be wrong and why AltUI does not work?

      posted in openLuup
      A
      ArcherS
    • RE: Considering changing to HA - but what installation method?

      Just for fun I decided to test and setup Home Assistant OS on two virtual machines.

      The first is a HA OS VM on a Windows 10 i5 NUC with VirtualBox. Quite easy to setup, some information can be found on the HA website, I also looked at this guide.

      The second VM I installed on an old Core2 PC. I installed Proxmox and then HA OS in a VM. A bit more complicated to setup but there is a good guide here. The Core2 seems ok for this setup, in comparison with the old Athom PC that did not do the job.

      Both installations seem to work ok. I will test them later on with a backup of my production setup to see if that changes anything.
      The Windows installation got corrupted when I had to hard reset the PC. As expected HA OS did not like that, however quite easy just to delete the VM and set it up again. I only had a test installation of HA on the VM, but as always a backup of HA is a good idea.

      I have not tested any USB devices (e.g. Zwave stick) since I do not use it. As far as I have understood it both should work with USB devices.

      What to use? The plan is to stay with my current Debian/Docker setup since it has so far been very stable. If the HA devs continues to move away from the Docker installation I may need to reconsider this.

      The other VM's could be an option for test rigs I think.
      I like the Proxmox setup, it feels quite solid and is built for VM. The Windows setup feels a bit more uncertain with the MS Windows 10 automatic updates etc.

      posted in Home Assistant
      A
      ArcherS
    • RE: An electricians or wiring experts here?

      @cw-kid it is really difficult to say. I think your drawing looks quite similar to the one I posted, but not quite sure, it could be different. The earthing in the pattress box is unfamiliar with me, the boxes here are in plastic. But I assume it is simply an earth to the box since it is made of metal.

      The colours are always tricky in old houses. They can have changed, different standards over time etc. Not to be trusted in other words. The only way to know is really to try understand what they all are and where they all go.
      You may need to disconnect the cables on the two switches to fully map things out. Marking the original position of all cables, cutting the power while working etc. 🙂

      I do not have any Dimmer 2, but will it not need neutral to operate? This means that you would need to get neutral to behind one of the light switches.

      Another solution could be to put the Fibaro at the light instead, if it fits safely there and is allowed in your location. That could perhaps be a solution not having to get new cables drawn into the boxes.

      Regarding your switches momentary should work or are even needed for being able to dim the light.

      I found a sketch showing one way to connect two momentary switches to a Fibaro Dimmer (the older version I think since it says "O" for the connnection that goes to the light). Maybe it could be of use.
      As always continue with care and cross-check with the Fibaro diagram, they could have changed something in the new version.

      f4e3f986-2d6b-42b7-a054-e68d60607563-bild.png

      Basically if I understand the sketch correctly the two switches need to be connected in parallel over S1 and SX.

      Not sure I can help more, good luck! 🙂

      posted in General Discussion
      A
      ArcherS