All Activity

I updated to the newest version (0.2.10) and it is still not working, again. I tried re-authenticating it and that hasn't helped either. any suggestions?

Should be in the non-production store.

Is there anything further on this? Every time there is any hiccup in my network Blue Iris disconnects (despite saying "connected"). It seems that people are saying using the "re-discover" button will fix it. Do I need to just have a program that runs every hour triggering a "re-discover"?

The heat sink on these things is the chassis. So I think it is a little deceiving compared to other devices with internal heat sinks. With these devices you actually touch the heat sink with normal handling of the unit. With internal devices, you are touching plastic that is well removed from the source of heat. I think if you opened your PC (or similar) and touched the heat sink, you might get the impression that it is also too hot even though it is working as expected.

@sjenkins is 1.13.0 in the plugin store? Just wondering how to get at it Gary

I don't have an eISY (MeLE Quieter3Q), but do have a MeLE Quieter3C running Ubuntu with Homebridge. The cooling fins on the top of the unit are plastic, not aluminum. I simply mounted it to the back of a monitor with a VESA mount. Hasn't been a problem after 2.56 years. root@mele-ud22:~# sensors coretemp-isa-0000 Adapter: ISA adapter Package id 0: +49.0°C (high = +105.0°C, crit = +105.0°C) Core 0: +41.0°C (high = +105.0°C, crit = +105.0°C) Core 1: +41.0°C (high = +105.0°C, crit = +105.0°C) Core 2: +41.0°C (high = +105.0°C, crit = +105.0°C) Core 3: +41.0°C (high = +105.0°C, crit = +105.0°C) acpitz-acpi-0 Adapter: ACPI interface temp1: +27.8°C (crit = +119.0°C) nvme-pci-0200 Adapter: PCI adapter Composite: +41.9°C (low = -0.1°C, high = +84.8°C) (crit = +94.8°C) Sensor 1: +41.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +46.9°C (low = -273.1°C, high = +65261.8°C) Sensor 8: +41.9°C (low = -273.1°C, high = +65261.8°C) root@mele-ud22:~# nvme smart-log /dev/nvme0 Smart Log for NVME device:nvme0 namespace-id:ffffffff critical_warning : 0 temperature : 42 C (315 Kelvin) available_spare : 100% available_spare_threshold : 5% percentage_used : 11% endurance group critical warning summary: 0 data_units_read : 1,495,531 data_units_written : 41,693,437 host_read_commands : 21,305,919 host_write_commands : 1,899,017,040 controller_busy_time : 1,898 power_cycles : 36 power_on_hours : 22,418 unsafe_shutdowns : 12 media_errors : 0 num_err_log_entries : 1,098 Warning Temperature Time : 0 Critical Composite Temperature Time : 0 Temperature Sensor 1 : 42 C (315 Kelvin) Temperature Sensor 2 : 46 C (319 Kelvin) Temperature Sensor 8 : 42 C (315 Kelvin) Thermal Management T1 Trans Count : 0 Thermal Management T2 Trans Count : 0 Thermal Management T1 Total Time : 0 Thermal Management T2 Total Time : 0 Not sure if the eISY comes with the original warning label on it, but here is a pic from a 3Q review.

I placed a cheap ($11) usb fan from Amazon on top on the unit have had zero problems With the ambient temperature on my desk is around 71° [admin@eisy ~]$ ./get-temp.sh CPU0 26 C / 78 F CPU1 27 C / 80 F CPU2 26 C / 78 F CPU3 27 C / 80 F TZ0 27 C / 80 F Quiet 90mm Router Fan Cooler $11.99 2Pack Quiet 80mm USB Fan Dual-Ball Bearings $19.99

Is there a way to copy the advanced configuration settings in favorites one object node to another, for example, value based color settings on multiple temperature sensors.

Turns out, not VirtualSmartHome. I just had the same problem when I tried to code this into a plugin. The issue was the headers not whether it was HTTP/1.1 or HTTP/2. With the proper headers it works with either one. POST or GET also work.

I'm an INSTEON installer and am at a customer who has the same scenario described above. I assumed the PLM dead. Replaced it, no change. Found this thread. INSTEON support was unchecked. Checked it, saved, restarted IOX. PLM working. I'm going the check my other eisy customers. Thanks for this thread!

I guess two ways to countermeasure the confusion for users 1. Make the local plugin handle both, the regular plugin handle remote only. Will likely have your more advanced users in the local plugin. Could use this as your slow merge plan. Cons: managing two plugins & as you state the testing involved. 2. Lots of warnings in the instructions and the labels on the configuration items to steer the remote users from entering anything in the fields. Again assumption is your local hub users are your more advanced. May, or not, be a good assumption. Pick your poison.

Fixed version - thanks I agree and could likely merge the two - I just fear confusion with non-local users (having option to enter credentials that they cannot get etc.) if it was to become 1 combined node Making the local a super node is not too big an issue - but it still requires double testing (and even more so when supporting both connection types) - but as you say long term it could take over the existing one. I guess I'll aim for the combo node from the start

Pretty quiet group out there ; I am specifically looking for at least ONE Gen2 user to tell me the commands and updates still work before I go into production.

The one installed is 0.0.7, the one I got a message on and is in the store is 0.0.6. Assumed there was no difference, just wanted to let you know as it has happened to me before ; just causes noise with the users. I am good either way on do the non-local devices sit on the local plugin. Con is it means another plugin, Pro as you say is keeping it clean ( keeps it very obvious which ones you added to the local hub). Saying that, my additional speaker hub is sitting on the local plugin right now & seems happy enough. Do'ing it this way would allow me to utilise it with one plugin. I don't know what the plumbing is, but doesn't it give you a path to "one plugin to rule them all" if the local eventually swallows the functionality of the non-local hub? or does the communications go the other way? Good to support either way. I have debated this question with my Hunter-Douglas plugin, there are Generation 2 & 3 with very different update paths. I kept them as one, but nearly split them in my last rewrite. There are almost no blended 2/3 environments. In this case you will have many with at least a speaker hub which has some use but won't be on the local. More rambling than help, but maybe some things to discuss.

There is a major update coming, which includes an update to the OS. It was to be announced at the same time, but it got delayed.

Apologies. I'm using a rest command from Home Assistant to run a program on the ISY. That ISY program is what actually does the adjusting of the screen. I'd like to adjust the scene directly from Home Assistant and therefore not require a program on the ISY. So yes, I will still need the ISY but I don't want the ISY to be running/needing any programs.

it is the version shown or the one installed? There is no difference between to two besides the version number I have started to work on the local version - I am wondering if it is better to make the local node only handle devices attached locally to the hub (the non-local can be handled by the existing node) It seems like a cleaner cut in my mind vs the current node Let me know what you think

I'm confused. Your last statement indicates that you are making the adjustments using an API Rest command (by calling an ISY program). That is only one level of abstraction away from what you're apparently trying to accomplish. In both cases, you'd still need the ISY, right? Or am I missing something?

@Panda88, fyi the version in beta store has reverted from 0.0.7 to 0.0.6

Decided to start the rewrite ; mostly this is modernising the coding of the plugin, but a few features come along for the ride. Controller: re-written to be more pythonic Status which is meant to indicate if connected was never working right, on at start, off with stop / delete. If you monitor, it can be useful. I use it on folders to switch between my beta, local, and production versions of programs. Monitor the control version of ST for heartbeat. added NumberofNodes which may be useful to some Garage In the continuing roll out of control the garage device added it for motor, motion, obstruction. will get its rewrite next version, lots to do here Switch added TOGGLE, as a receive command, the send will be DON or DOF, let me know how useful re-written to be more pythonic, logging should be much less noisy persistence is now using the polyglot management instead of individual files for those watching, the first run will use the file data then store it with polyglot, then delete the file Generic / dimmer didn't add a TOGGLE but could; thoughts? same as switch for re-write, logging, persistence much improved behaviour from 3.1.15 for remembering on level, won't get messed up by double off or fast off/on Temp / TempC poly persistence next version they get their re-write, logging need to be consolidated into a single file, still will be configured as separate, for backward compatibility TEST IT OUT & Give me some feedback people!!! VERSION = '3.1.16' """ 3.1.16 DONE fix controller ST "status" on at start, off at stop / delete, "control" still heartbeat DONE garage send CMDs, motor, motion, obstruction ; get naming consistent DONE standardize startup sequence DONE rewrite checkParams, Discovery DONE add NumberOfNodes DONE switch/generic/dimmer node: use polyglot persistence, delete old db files 3.1.15 DONE generic, dimmer, change ST to OL, memory of level for DON, DFON/DFOF, command 3.1.14 DONE commands for switches, generic, dimmer, garage

Who would write an http: driver that isn't backward compatible with the accepted protocol for what 20 years? Very weird for such a new protocol standard.

I've been using my ISY for over 10 years now and it has been my main automation system for that entire time. I'm transitioning over to Home Assistant (HA) Yellow. Most of my devices are still Insteon so I'm keeping my ISY but all the automation will be done through HA. One thing I'm having trouble with doing solely in HA and am looking for some help. Any ideas if what I'm trying to do is possible? I have a bathroom light switch called MasBathLight and an 8-button keypad called BedsideKeypad. I have a scene called MasterBathroomLights. In the scene I have both MasBathLight and BedsideKeypad as controllers. This enables me to turn on/off the bathroom light using MasBathLight which is a switch right as you walk into the bathroom, or using BedsideKeypad which is located right next to the bed. What I would like to do is when someone goes to sleep, adjust it so that whenever someone uses either switch (MasBathLight or BedsideKeypad) to turn on the lights, I'd like the lights to turn on to 15% only. To do this I need to adjust the following: In the scene MasterBathroomLights, adjust controller device MasBathLight for MasBathLight on-level of 15% and also in the same scene adjust controller device BedsideKeypad for MasBathLight on-level to 15% (MasBathLight is the load). The actual on-level of the scene MasterBathroomLights does not need to be adjusted as I never call that scene from anything. Here's what my program currently in the ISY looks like to do this. In 'MasBathLight' Set 'MasBathLight' to 15% in 0.1 seconds, 1 retry In 'BedsideKeypad' Set 'MasBathLight' to 15% in 0.1 seconds, 1 retry Any ideas how I can make these adjustments using an API rest command? I've found several examples online but none of them have worked. Some include using the node of the scene and the node of the controller such as rest/links/groups/<scene_node_id>/controllers/<controller_node_id>/responders/<responder_node_id>/update/cmd/DON/<on-level> or /rest/scenes/adjust/[controller_node_address]/[responder_node_address]/[level] My current work-around is that I have a program in my ISY to do the adjustment that I need and I use HA to call that program using an API Rest command.

Yes - there is a localHub that is not widely promoted (yet?), but you can buy it if you contact them I would start with the simple Hub (much lower cost) initially if you are just testing - service is reliable if you internet is reliable. Once you have something critical that must work without internet access you can look at localHub - my guess is price for the localHub will also be lower by then. It is fairly easy to move devices to local later

I’m looking into using yolink. If I want to use it with local API, what do I need to do? Is there a certain hub I should buy? Thank you.

Interestingly our robot overlords do not agree: Now mind you, I trust Michel more than any AI, but maybe he meant HTTPS vs HTTP as opposed to HTTP2 versus HTTP1.1?