Multi-System Reactor

696 Topics 6.8k Posts
  • 0 Votes
    22 Posts
    784 Views

    Hi, it seems working ok. Thanks! If you need more infos to test, just tell me how I can produce them.

    L Bulb FibaroDimmer2 ezlo>device_61425874129e29124dfcd75e 0.65 7:30:07 PM dimming.level=0.65 dimming.step=0.1 energy_sensor.units="KWh" energy_sensor.value=11.3400001525879 power_sensor.units="W" power_sensor.value=6.90000009536743 power_switch.state=true x_ezlo_device.battery_powered=false x_ezlo_device.category="dimmable_light" x_ezlo_device.manufacturer="Fibaro" x_ezlo_device.model="FGD-212" x_ezlo_device.parent="" x_ezlo_device.reachable=true x_ezlo_device.ready=true x_ezlo_device.room="613e2024129e2912114c093b" x_ezlo_device.status="idle" x_ezlo_device.subcategory="dimmable_in_wall" x_ezlo_device.type_id="271_258_4096" x_ezlo_item.dimmer=65 x_ezlo_item.dimmer_down=0 x_ezlo_item.dimmer_stop=0 x_ezlo_item.dimmer_up=0 x_ezlo_item.electric_meter_kwh=11.3400001525879 x_ezlo_item.electric_meter_watt=6.90000009536743 x_ezlo_item.hw_state="hardware_failure" x_ezlo_item.load_error_state="unknown" x_ezlo_item.meter_reset=0 x_ezlo_item.over_current_state="unknown" x_ezlo_item.over_load_state="unknown" x_ezlo_item.power_surge_state="no_surge" x_ezlo_item.switch=true x_ezlo_item.voltage_drop_drift_state="unknown" x_ezlo_object.id="61425874129e29124dfcd75e" zwave_device.capabilities=null zwave_device.failed=false zwave_device.manufacturer_info=["Fibaro","FGD-212",null] zwave_device.node_id=27 zwave_device.version_info=null Capabilities: dimming, energy_sensor, power_sensor, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighbors

    another

    K Bulb Domitech ezlo>device_61423589129e29124dfcd756 0.65 7:35:42 PM dimming.level=0.65 dimming.step=0.1 power_switch.state=true x_ezlo_device.battery_powered=false x_ezlo_device.category="dimmable_light" x_ezlo_device.manufacturer="Domitech" x_ezlo_device.model="ZE27EU" x_ezlo_device.parent="" x_ezlo_device.reachable=true x_ezlo_device.ready=true x_ezlo_device.room="613e2020129e2912114c093a" x_ezlo_device.status="idle" x_ezlo_device.subcategory="dimmable_bulb" x_ezlo_device.type_id="526_19522_12596" x_ezlo_item.dimmer=65 x_ezlo_item.dimmer_down=0 x_ezlo_item.dimmer_stop=0 x_ezlo_item.dimmer_up=0 x_ezlo_item.switch=true x_ezlo_object.id="61423589129e29124dfcd756" zwave_device.capabilities=null zwave_device.failed=false zwave_device.manufacturer_info=["Domitech","ZE27EU",null] zwave_device.node_id=26 zwave_device.version_info=null Capabilities: dimming, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighbors

    another

    H Bulb Widom dimmer ezlo>device_6147578c129e29124dfcd814 1 7:36:56 PM dimming.level=1 dimming.step=0.1 energy_sensor.units="KWh" energy_sensor.value=0.651000022888184 power_sensor.units="W" power_sensor.value=2.47000002861023 power_switch.state=true x_ezlo_device.battery_powered=false x_ezlo_device.category="dimmable_light" x_ezlo_device.manufacturer="Unknown" x_ezlo_device.model="Unknown" x_ezlo_device.parent="" x_ezlo_device.reachable=true x_ezlo_device.ready=true x_ezlo_device.room="613e2012129e2912114c0938" x_ezlo_device.status="idle" x_ezlo_device.subcategory="dimmable_in_wall" x_ezlo_device.type_id="329_4628_2560" x_ezlo_item.dimmer=100 x_ezlo_item.dimmer_down=0 x_ezlo_item.dimmer_stop=0 x_ezlo_item.dimmer_up=0 x_ezlo_item.electric_meter_kwh=0.651000022888184 x_ezlo_item.electric_meter_watt=2.47000002861023 x_ezlo_item.meter_reset=0 x_ezlo_item.switch=true x_ezlo_object.id="6147578c129e29124dfcd814" zwave_device.capabilities=null zwave_device.failed=false zwave_device.manufacturer_info=["Unknown","Unknown",null] zwave_device.node_id=41 zwave_device.version_info=null Capabilities: dimming, energy_sensor, power_sensor, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighbors
  • This topic is deleted!

    Locked
    1
    0 Votes
    1 Posts
    11 Views
    No one has replied
  • 0 Votes
    9 Posts
    303 Views

    Master @toggledbits 🙂

    Following the line "I show you the way, I don't give you the transport":), the MSR indicates in Entities the time of the last device status change. Where is this information stored?

    e9bcef0d-fd5c-4e4a-b2fa-0ade8eeb52e7-image.png

    Use case: I want to monitor all devices, and the ones that are not communicating for more than 48 hours should know and take action.

    For sure there are some that can not even, because it would be a problem, then I create an exception list. But initially, I want to see everything that has not been communicated in 48 hours.

    The principle is almost the same as Hubitat's WatchDog APP, but I want to have my own, and not be dependent on Hubitat's communication or action. I also understand that it has more validity, because it is a way to ensure that the MSR is talking to all devices, and not only to Hubitat.

    Thanks.

  • 0 Votes
    5 Posts
    188 Views

    He's got a case-insensitive test going; it'll be fine. The problem arises mostly when you send a new mode to Hubitat... that's where you need to be careful and get the case correct.

  • 0 Votes
    19 Posts
    318 Views

    @toggledbits ok, thanks!

  • 0 Votes
    5 Posts
    184 Views

    Sure enough, it is working just as you (toggledbits) described it. Not sure I could have figured this one out. I have made many attempt using the conditions but since I was having only one, using a group never occured to me. The condition and group have similar output control and restriction but not quite the same. Lesson learned.

    Thanks again

  • Difference between two dates.

    Locked
    4
    0 Votes
    4 Posts
    161 Views

    @alan_f very good! Nothing like consulting those who know how to use the available functions! Thank you very much, I am already removing what I had done and changing it to your instruction, and putting one more command in my knowledge notebook. Thank you very much!

  • Saving previous house mode with MSR

    Locked
    5
    0 Votes
    5 Posts
    141 Views

    Thanks! I’m happy to have the right approach. This means I’m into the tool and ready to helps others.

  • MSR under reverse proxy?

    Locked
    11
    0 Votes
    11 Posts
    768 Views

    I'll look into that.

  • 0 Votes
    13 Posts
    306 Views

    So I think in my case it really was just quiet on the entity updates, resulting in a lot of warnings and restarts. I added the Hubitat Ping app to my hub and set it to ping it's gateway every 60 seconds. I know from running several ping jobs on my own hub that they show up as recently updated entities on MSR every time they fire. Sure enough, since starting the polling on their hub there have been no more websocket restarts or warnings.I also haven't had any out-of-sync devices yet, so I'll continue to wait until I see that again and try the MSR restart instead of the Hubitat refresh to see what the result is.

  • This topic is deleted!

    1
    0 Votes
    1 Posts
    19 Views
    No one has replied
  • Format a value from date to epoch in MSR

    Locked
    4
    0 Votes
    4 Posts
    121 Views

    Already done!

  • Execute HAAS command via MQTT

    Locked
    7
    0 Votes
    7 Posts
    163 Views

    Yeah, I know that feeling.

    So, right now I'm on week 2 and I've completely removed every plug-in from my Vera and moved most of them to HomeAssistant (or my own code). MQTT is doing great, and now I'm sending my TV commands via HA bridge, then to a wrapper aggregating them for MQTT and pushed via MSR to HA. It seems complicated, but it's pretty fast. Bonus point, I have a nicely formatted MQTT message from MSR when Harmony Activities are changed.

    Next week I'll work on my solar integrations (my installer was slow due to bad weather, so we will switch the system on next week), but I've already pushed a couple of things via MQTT.

    I will eventually move other things to HA and use the MQTT trick to execute services from other part of my logic. Thanks for the work!

  • 0 Votes
    26 Posts
    616 Views

    @toggledbits I'm marking this as solved because I watched a couple of the rulesets WIA this morning as the day's temps ramped up.

    Thanks for your incite and guidance as always, sir!

  • A couple of suggestions for MSR

    Locked
    10
    4 Votes
    10 Posts
    260 Views

    @toggledbits

    Surely in an election between all users, this is the most important "a tool to see where I'm using an entity, as trigger or condition". You have already explained before the difficulty, and that the effective use of a DB would help this crossing of information, but the cost of the DB is still high and can sacrifice a lot of the system.

    One day you will find a way to #1 MSR request.

    I would add one more request, that I have commented on before and I am sure you have in your notebook of improvements for the future. In the home screen, the same way you have the Recently Changed Entities board, a board that can show the history of what happens in the Set Rules, so it would be possible to follow the last actions.

    And again and repeat "Thanks for the hard work @toggledbits" !

  • 0 Votes
    11 Posts
    282 Views

    Thanks to you!
    The fix is working.
    Now I can truck energy consuption on Influxdb. The idea is to try to make in MSR what in HA is doing with utility_meter, Trend and Lovelace UI togheter. Maybe in future we will see a standard MSR energy plugin too.

    Home Assistant Utility Meter Utility Meter

    Instructions on how to integrate the Utility Meter into Home Assistant.

    Home Assistant Trend Trend

    Instructions on how to integrate Trend binary sensors into Home Assistant.

  • Run MSR on Hubitat C7?

    Locked
    3
    0 Votes
    3 Posts
    165 Views

    Kinda where I figured things stood, and by all means, stay the course! About to sell my unused Ezlo Plus now, btw.

  • 0 Votes
    12 Posts
    244 Views

    OK. In playing with this a bit more, I'm going to make suninfo.sun_angle go away (eventually; after a deprecation period), and it's replacement will be a soon-to-come suninfo.elevation. The elevation is the true angle of the sun above the horizon. Unless you live on the equator, the sun is not really at 0 degrees at solar noon, as sun_angle indicates. For example, right now for me in the Atlanta area at this time, solar noon gives me an elevation of just 33.5 degrees (summer solstice about 80 degrees). I think the true elevation will be a better metric for solar energy calculations, and in combination with azimuth, you should easily be able to compute ray angles/exposure to solar panels and good things like that.

    The other things I'm fixing is that our friends in Prudhoe Bay and Tromsø are getting incorrect day lengths, etc., right now because the sun never rises at this time of year. The sunrise/sunset times are null as expected, but the day length is 24 when, IMO, it should be zero, and the sun_angle is null which is again not as useful as having a real elevation.

  • Is Telegram working?

    Locked
    27
    0 Votes
    27 Posts
    899 Views

    @toggledbits No, I guess we shouldn't spend any more time trying to understand. It works and I'm delighted. I do appreciate that you try to teach us fishing instead of handing the fish. I always try for hours before I ask for assistence. That's the way to learn and grow. Take care!

  • 0 Votes
    4 Posts
    102 Views

    I'll get after those docs... you're not the first to be bitten.

Recent Topics